Help with Xen Orchestra

jrc

So last night I compiles XO from source as I plan to use it at home for my 2 XCP-ng 8.2 servers, but also as an eval for work, since I am thinking about moving to it there from XCP-center.

Everything went well, got it up and running and playing with it, but I have run into an issue that, in my opinion, make XO somewhat suspect as a management platform for XCP.

I installed the patches is suggested, and then a triangle appeared in the hosts list saying I need to restart in order for the patches to be applied, I did this three times, but the alert has not gone away.

Related to this, one host also has a red triangle saying that the time on the host does not match that of the XO system. Which was true, the RTC was set to local time, but XCP thought that was UTC, so it adjusted the system time. I fixed that, now the time is correct. Yet the triangle has not gone away, it's been over twelve hours and a reboot of that host, the red triangle persists.

Did I miss something here? Is there a way to force XO to check again and update? How do I know if the patches have been applied (XCP-center used to be nice and easy for this)?

I also note that none of these warnings/errors are listed under the Healthy dashboard in the alerts section, or in the Overview dashboard.

olivierlambert

Just refresh the UI (Ctrl+R)
If nothing changed, Disable/Enable the pool in Settings/server (be sure to have only one host per pool connected, not all)

jrc

@olivierlambert

Thanks, I actually tried all of that, it did not help. I then rebooted the pool master (which also had updates pending) and once it came back up that alert from the host in question went away. I guess "reboot the host to apply updates" really means restart all the hosts in the pool to apply updates.

Maybe I could suggest a bit clearer description of that flag?

Also, there is a place in XO that I can go to see exactly what patches are installed and applied to any given host and/or the pool?

olivierlambert

Indeed, you must reboot all hosts of the pool because you must have same update level inside the same pool.

Having various patch level on the pool is a bad practice, so that why you should always have all your hosts up to date and rebooted as closely as possible (in time).

You can't know the "patch" level for an updated host, because we are using yum and therefore, one must being always up to date. If not, at least at the same unpatched level.

That's also why we strongly encourage people to patch at pool level, that will download updates for the whole pool.

jrc

@olivierlambert

That makes sense. So the way to do it would be to install all the updates, then restart the Master, followed by the rest of the hosts?

If, it might be good if the tooltip for the exclamation triangle was a bit different on the non-master hosts, could say "Reboot the master, then this host to apply updates" vs "Reboot this host to apply updates"

Is there an official way to make suggestions like this? Not necessarily a feature request, more a UI improvement suggestion.

olivierlambert

Sure, you can create a GH issue on XO repository