@flakpyro yes. thanks for your test and to reporting the problem anyway. it is helping us to see what kind of problems users could have.
Team - XAPI Network
Private
Posts
-
RE: XCP-ng 8.3 updates announcements and testing
-
RE: XCP-ng 8.3 updates announcements and testing
@flakpyro it seems to me the proper upgrade path is:
- put the master in maintenance mode (
xe host-disable host=$MASTER) - evacuate the master (
xe host-evacuate host=$MASTER) - yum update the master
- reboot the master (
xe host-reboot host=$MASTER) - once done, do the same of the others hosts
the VM would have been updated with the new
trunksattribute when migrating to some updated host (in your case, when migrating to the master). - put the master in maintenance mode (
-
RE: XCP-ng 8.3 updates announcements and testing
"xenopsd internal error: Hotplug.Hotplug_error(\"Failed to read /xapi/450015b0-e878-5067-e8b6-000000000001/private/vif/1/trunks\")"This is related to new code in the upgrade. the trunks attribute is used for VLAN filtering (new feature).
it seems that the running code is the new one (it is knowning about trunks) but the VM doesn't have the trunks attribute.
I would be interested to have a clean picture of the situation:
- on which host this VM is resident on
- version of the master
- version of the host where the VM is resident
-
RE: XCP-ng 8.3 updates announcements and testing
@andersonalipio Let's continue the discussion with @semarie in a separate thread
-
RE: Bad Performance CPU? get-cpufreq-para failed
@flakpyro oh, good to know, thanks for sharing this!
@poddingue this might be worth some investigation to document, but likely would need to gather similar settings for a set of vendors to make it relevant.
-
RE: XCP-ng 8.3 updates announcements and testing
@andersonalipio can you also share the XOA version you're running? @semarie did a bunch of improvement on lifecycle of hosts and VM at some point XO side.
-
RE: XCP-ng 8.3 updates announcements and testing
@andersonalipio I would be interested to get some elements from your installation.
- your
/var/log/sdn-controller-plugin.logfile (on the host) in order to check the parameter passed by XO. - output of
xe network-param-list uuid=$UUID(for the network concerned) orxe network-list params=all(if uuid is unknown) - output of
xe pool-list params=other-config(forxo:sdn-controller:*elements) - output of
xe vif-list params=uuid,network-uuid,other-config(forxo:sdn-controller:*elements)
Feel free to share it privately via PM if you prefer, possibly using https://paste.vates.tech/ .
Cc @Team-XO-Backend too (as it could be from XO side)
- your
