@olivierlambert I've made the needed adjustment in the build script to override the default. Now I wait for another set of patches to test it.
Thanks all.
Best posts made by dsiminiuk
-
RE: Rolling Pool Update - host took too long to restart
-
RE: How to add a static IP address to a PIF
@olivierlambert Wow too easy. Thank you!
Latest posts made by dsiminiuk
-
RE: Rolling Pool Update - host took too long to restart
@olivierlambert I've made the needed adjustment in the build script to override the default. Now I wait for another set of patches to test it.
Thanks all. -
RE: Rolling Pool Update - host took too long to restart
@DustinB Not a faulty disk. It appears to be memory testing at boot time and at other times after init doing the same thing,
The cluster is a pair of HPE ProLiant DL580 Gen9 servers, each with 2TB of RAM.
Yes, I could turn off memory checking during startup, but I'd rather not.
Danny
-
Rolling Pool Update - host took too long to restart
Rolling pool updates fail because the master is taking too long to restart.
What is considered too long?
Perhaps this should be a setting in the server config to override a default.
In this case, my servers take about 20 minutes to reboot.
Is there a CI I can adjust?pool.rollingUpdate { "pool": "3cfffa75-69ea-7792-a320-92a7cb33f6f8" } { "message": "Host b725c95c-17af-41ae-a9c5-deeb1b7bfc50 took too long to restart", "name": "Error", "stack": "Error: Host b725c95c-17af-41ae-a9c5-deeb1b7bfc50 took too long to restart at Xapi.rollingPoolReboot (file:///opt/xo/xo-builds/xen-orchestra-202404111938/packages/xo-server/src/xapi/mixins/pool.mjs:127:9) at Xapi.rollingPoolUpdate (file:///opt/xo/xo-builds/xen-orchestra-202404111938/packages/xo-server/src/xapi/mixins/patching.mjs:506:5) at XenServers.rollingPoolUpdate (file:///opt/xo/xo-builds/xen-orchestra-202404111938/packages/xo-server/src/xo-mixins/xen-servers.mjs:689:5) at Xo.rollingUpdate (file:///opt/xo/xo-builds/xen-orchestra-202404111938/packages/xo-server/src/api/pool.mjs:231:3) at Api.#callApiMethod (file:///opt/xo/xo-builds/xen-orchestra-202404111938/packages/xo-server/src/xo-mixins/api.mjs:366:20)" }
-
RE: Restoring from backup error: self-signed certificate
@Danp Is it safe to say this is being worked on? I don't want to assume anything.
-
RE: Patching behind a corporate proxy server
@Gheppy A follow up... Patches appeared in XO right after updating the files (prior to an XCP-ng reboot). Just FYI.
-
RE: Patching behind a corporate proxy server
@olivierlambert Not production yet. I'm setting up a proof of concept so that management can see there are alternatives to
VMwareBroadcom. -
Patching behind a corporate proxy server
I have 2 HPE servers and a separate VM with XO built from sources using ronivay's script.
I have the web proxy setup in the XO VM for yarn, apt, and global use and everything works there. I can do apt updates and XO updates.
I am trying to understand what I need to set elsewhere in XCP-ng for patching to work, i.e. detection, download, and deployment. I have set the same proxy used elsewhere for the proxy setting in the master host but I have no idea if that is the correct thing to do or do I need to setup something else on the XO instance?
I think this is the last issue before I can say the environment is ready for prime time.
Thanks
Danny -
RE: How to add a static IP address to a PIF
@olivierlambert Wow too easy. Thank you!
-
How to add a static IP address to a PIF
XCP-ng 8.2.1 release/yangtze/master/58
Xen Orchestra, commit 9cb94
Master, commit 7cb2fI have setup anew on a pair of DL580s (72 CPUs, 2TB RAM). I have SAN HBAs, a 1TB LUN attached with multipath. I have a VLAN for VM network access, all works fine.
I have an additional 10GbE NIC on these machines connected through a switch on a private VLAN and I would like to use this network as a migration network. The PIFs are up but I don't see a way to add IP addresses so that I can use it.
How do you add a static IP to a PIF in XO?
Thanks
Danny