🛰️ XO 6: dedicated thread for all your feedback!

[rcolzen]

Hello, I hope this is the correct place to report this issue.

Short version:

When an XO-managed NFS remote became unreachable, XOA Web UI would not become operational. Once the NFS server became reachable again, the UI immediately recovered.

Investigation and Findings

We just updated our XOA to ver. 6.8.2, and discovered that if an NFS remote becomes unavailable, XOA Web UI does not load correctly and appears unavailable to users. This has not been an issue with previous versions.

We had some network changes in our environment, and because of that the network to one of our NFS remotes broke for some time. The XOA UI would not load at all, despite being up before our network broke the connection to the NFS.

Checking logs, we observed repeated warnings such as:

TimeoutError: operation timed out

for the remote.

Additionally, XOA reported:

Setting up /v5
Setting up /v6
Setting up /

and:

Web server listening on http://[::]:80
Web server listening on https://[::]:443

which suggests the web service itself started.

Also, xoa check reported all fine.

However, as long as our NFS was unreachable, no user could not access a functional Web UI, either v6 or v5.

Root Cause

One of the configured NFS remotes was unavailable:

172.24.44.140:/mnt/Storage01/vm-iso-store

After connectivity to the NFS server (172.24.44.140) was restored, the Web UI immediately became operational again.

Before connectivity was restored:

• df -h was hanging for an extended period.
• XOA Web UI was unavailable.
• xoa check did not identify the problem.
• Multiple remote timeout errors appeared in the logs.

After NFS connectivity returned:

• df -h completed immediately.
• XOA Web UI became available again.
• No manual XO intervention was required.

We expect an unavailable NFS remote (an ISO repository) should mark the remote as unavailable, and allow XO/XOA Web UI to load normally.

If this is not the correct place for this type of bug report, please feel free to move it or point me to the appropriate location. I wanted to make sure the issue was reported and documented.

Thanks.