Team - XAPI & Network

Private

Posts

  • RE: When the XCPNG host restart, it restarts running directly, instead of being in maintenance mode

    @olivierlambert XCP-ng will include an option to keep hosts disabled after reboot. This will be part of the next update for xapi. (25.33.1) This was contributed upstream by Andriy and is used by adding an extra parameter to disable: xe host-disable uuid=$HOST auto-enable=false.

  • RE: Potential bug with Windows VM backup: "Body Timeout Error"

    I've got a fix for this issue in the pipeline and would really appreciate if anyone here could test to confirm if it resolves the problem for you.

    You'd need to install a custom build (not production-ready, be careful, all the usual warnings apply here) according to these steps:

    1. Before updating, preferably check that exporting a particular VM with compression on results in the timeout error consistently.

    2. Write the following file to /etc/yum.repos.d/xvatest.repo:

    [xva-test-repo]
    name=xva-test-repo
    baseurl=https://koji.xcp-ng.org/repos/user/8/8.3/asultanov1/x86_64/
    enabled=0
    metadata_expire=1m
    gpgcheck=1
    repo_gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-xcpng
    
    1. Make sure you're up to date on the rest of your packages with yum upgrade --enablerepo=testing (reboot if necessary)
    2. Install the fix (this should install *.xvafix.1 packages):
    yum upgrade xapi-core qcow-stream-tool vhd-tool --enablerepo=xva-test-repo
    
    1. Restart the toolstack:
    xe-toolstack-restart
    
  • RE: XOCE - ISO upload is renamed after upload to ISO SR

    @olivierlambert said in XOCE - ISO upload is renamed after upload to ISO SR:

    I think we discussed it internally, IIRC it's not XO doing any renaming, but the toolstack. Adding @andriy.sultanov or @psafont in the loop

    I'm not sure about that, xapi is quite conscious it cannot rename these ISOs, in the few places I've seen it mentioned. I did not see any place in xapi that could have renamed these, nor reproduce it in my system.

  • RE: Attempting to add new host fail on xoa and on server, worked on xcp-ng center

    I see at least on a couple of instances that the pool join is being forced. Please don't do this unless you understand the checks being ignored.

    What's the result of a pool join without the force option?

    Do both hosts have tls verification enabled?
    If not, run xe pool-enable-tls-verification. This will set up the certificates for pool communication correctly for the hosts in that pool and turn on TLS verification for pool communication.
    If yes, run xe host-list --minimal | xargs -I _ xe host-param-get uuid=_ param-name=name-label | xargs -I _ xe host-refresh-server-certificate host=_. This will reset the certificates for all the hosts in the pool.

    Try running the normal join command after doing these steps, and report whether it went well, or report the error.