@julien-f is aware of this problem and we'll find a way to make it more obvious

@Danp I tried some of the xe commands listed in that post like xe vm-param-clear and xe vm-param-remove and wasn't successful.

@tuxpowered said in Rolling Pool Update - host took too long to restart: When the first note reboots (the master), I can see that the system is back up in 5-8 min. If I go in to XO > Settings > Servers and click the Enable/Disable status button to reconnect it pops right up. Again, does not resume migrating the other nodes. That is what I am seeing also, logged here https://xcp-ng.org/forum/topic/9683/rolling-pool-update-incomplete

I had a similar issue, and what helped me was routing update traffic through Static Residential Proxies to avoid deep packet inspection that was blocking some repositories. They worked better than regular proxies in our setup since they look like normal home users, so the network didn’t treat the traffic as suspicious. You might need to whitelist some domains manually though, depending on how strict your proxy rules are.

@olivierlambert Ah, ok...thanks, but I'm not using the appliance; I installed XO via source.

@julien-f @julien-f All I have done is let ronivay's script do the builds daily on schedule if there is a new commit on the master branch. His script has not changed. There have been no new patches to the hosts. I don't have an explanation.

Trying something new... Remove all servers from XO and log out. Host 1 is powered off. On host 2. xe task-list uuid ( RO) : 727ecb6b-6f2e-15eb-601b-110b2478996b name-label ( RO): Async.host.power_on name-description ( RO): status ( RO): pending progress ( RO): 0.000 xe task-cancel uuid=727ecb6b-6f2e-15eb-601b-110b2478996b Task is still there. From XCP-NG Center. Shutdown all VMs and host2 (All powered off). Powered up both servers. Wait 15 minutes to make sure no tasks are pending (xe task-list). Logging output to file via putty of; tail -f /var/log/audit.log Added host2 (master) to XO Settings/Servers. The Async.host.power_on task hasn't come back.