[ovirt-users] Re: 4.3 won't upgrade engine in standalone KVM VM: low_custom_compatibility_version 'agent03'
Ah - it found a oVirt VM called agent03 - that has nothing to do with the engine VM. I think I confused myself, and thought engine-setup did not like the engine VM. Actually it was complaining about an existing oVirt VM...Hmmm - this VM was indeed set to 3.6. Thank you!! On Fri, Jul 5, 2019 at 9:22 PM Simone Tiraboschi wrote: > > > On Fri, Jul 5, 2019 at 3:15 PM Simone Tiraboschi > wrote: > >> >> >> On Fri, Jul 5, 2019 at 3:06 PM Richard Chan >> wrote: >> >>> In libvirt/virsh the VM is called "ovirt7"; here is the domain >>> definition. This VM has been upgraded from >>> 3.6->4.0->4.1->4.2. This is the first time engine-setup has complained >>> about the "level" of the VM. >>> >>> libvirt domain definition: >>> >> >> oVirt VMs contains something like: >> >> http://ovirt.org/vm/tune/1.0; xmlns:ovirt-vm=" >> http://ovirt.org/vm/1.0;> >> >> http://ovirt.org/vm/1.0;> >> 4.2 >> >> in the XML for libvirt so you are checking the wrong VM. >> > > Please try executing this on your engine VM: > > sudo -u postgres scl enable rh-postgresql95 -- psql -d engine -c "select * > from vms where vm_name='agent03'" > > >> >> >>> >>> >>> ovirt7 >>> cdb0f3fd-42c7-4a16-bcd1-5d65f19aca19 >>> 8388608 >>> 8388608 >>> 2 >>> >>> /machine >>> >>> >>> hvm >>> >> type='pflash'>/usr/share/edk2.git/ovmf-x64/OVMF_CODE-pure-efi.fd >>> /var/lib/libvirt/qemu/nvram/ovirt7_VARS.fd >>> >>> >>> >>> >>> >>> >>> >>> >>> Haswell-noTSX >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> destroy >>> restart >>> destroy >>> >>> >>> >>> >>> >>> /usr/libexec/qemu-kvm >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >> file='/var/lib/libvirt/images/ovirt7/database_01.WAEqcow2'/> >>> >>> >>> >>> >>> >>> >>> >>> >>> >> function='0x7'/> >>> >>> >>> >>> >>> >> function='0x0' multifunction='on'/> >>> >>> >>> >>> >>> >> function='0x1'/> >>> >>> >>> >>> >>> >> function='0x2'/> >>> >>> >>> >>> >> function='0x0'/> >>> >>> >>> >>> >>> >>> >>> >> function='0x0'/> >>> >>> >>> >>> >>> >>> >>> >>> >> function='0x0'/> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >> path='/var/lib/libvirt/qemu/channel/target/domain-15-ovirt7/org.qemu.guest_agent.0'/> >>> >> state='connected'/> >>> >>> >>> >>> >>> >> state='disconnected'/> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >> function='0x0'/> >>> >>> >>> >> heads='1' primary='yes'/> >>> >>> >> function='0x0'/> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >> function='0x0'/> >>> >>> >>> >>> system_u:system_r:svirt_t:s0:c194,c775 >>> system_u:object_r:svirt_image_t:s0:c194,c775 >>> >>> >>> +107:+107 >>> +107:+107 >>> >>> >>> >>> On Fri, Jul 5, 2019 at 8:53 PM Simone Tiraboschi >>> wrote: >>> On Fri, Jul 5, 2019 at 2:48 PM Richard Chan < rich...@treeboxsolutions.com> wrote: > Hi, > > I am running 4.2 engine in a standalone libvirt KVM VM (running on a > hypervisor that is not part of the oVirt infrastructure); i.e., I am not > using hosted engine but still running engine in a VM. > > Now 4.3 won't upgrade inside this libvirt KVM VM: > > Failed to execute stage 'Setup validation': Cannot upgrade the Engine > due to low custom_compatibility_version for virtual > machines: ['agent03']. Please edit this virtual machines, in edit VM > dialog go to System->Advanced Parameters -> Custom Compatibility Version > and either reset to empty (cluster default) or set a value supported by > the > new installation: 4.1, 4.2, 4.3. > > engine-setup has probably detected that it is running inside a VM: > 1. Where did it get 'agent03' string from > 2. Any suggestions how to fool engine-setup to think this is 4.3 > The engine is not going to check anything on hosts that are unknown at engine eyes. I think that you simply have in the engine a VM called 'agent03'. Please check it. > > Here is the dmidecode of the standalone engine VM: > > # dmidecode 3.1 > Getting SMBIOS data from sysfs. > SMBIOS 2.8
[ovirt-users] Re: 4.3 won't upgrade engine in standalone KVM VM: low_custom_compatibility_version 'agent03'
This engine VM running as part of the oVirt cluster (not hosted engine/not running under oVirt). It is running on a separate libvirt/KVM server. This hypervisor is totally separate and standalone: it is not a oVirt host. This VM has been controlling the oVirt hosts since 3.6 days. Inside this VM I have installed ovirt-release43.rpm and now running engine-setup. On Fri, Jul 5, 2019 at 9:15 PM Simone Tiraboschi wrote: > > > On Fri, Jul 5, 2019 at 3:06 PM Richard Chan > wrote: > >> In libvirt/virsh the VM is called "ovirt7"; here is the domain >> definition. This VM has been upgraded from >> 3.6->4.0->4.1->4.2. This is the first time engine-setup has complained >> about the "level" of the VM. >> >> libvirt domain definition: >> > > oVirt VMs contains something like: > > http://ovirt.org/vm/tune/1.0; xmlns:ovirt-vm=" > http://ovirt.org/vm/1.0;> > > http://ovirt.org/vm/1.0;> > 4.2 > > in the XML for libvirt so you are checking the wrong VM. > > >> >> >> ovirt7 >> cdb0f3fd-42c7-4a16-bcd1-5d65f19aca19 >> 8388608 >> 8388608 >> 2 >> >> /machine >> >> >> hvm >> > type='pflash'>/usr/share/edk2.git/ovmf-x64/OVMF_CODE-pure-efi.fd >> /var/lib/libvirt/qemu/nvram/ovirt7_VARS.fd >> >> >> >> >> >> >> >> >> Haswell-noTSX >> >> >> >> >> >> >> >> >> >> >> >> >> >> destroy >> restart >> destroy >> >> >> >> >> >> /usr/libexec/qemu-kvm >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> > file='/var/lib/libvirt/images/ovirt7/database_01.WAEqcow2'/> >> >> >> >> >> >> >> >> >> > function='0x7'/> >> >> >> >> >> > function='0x0' multifunction='on'/> >> >> >> >> >> > function='0x1'/> >> >> >> >> >> > function='0x2'/> >> >> >> >> > function='0x0'/> >> >> >> >> >> >> >> > function='0x0'/> >> >> >> >> >> >> >> >> > function='0x0'/> >> >> >> >> >> >> >> >> >> >> >> >> >> > path='/var/lib/libvirt/qemu/channel/target/domain-15-ovirt7/org.qemu.guest_agent.0'/> >> > state='connected'/> >> >> >> >> >> > state='disconnected'/> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> > function='0x0'/> >> >> >> > primary='yes'/> >> >> > function='0x0'/> >> >> >> >> >> >> >> >> >> >> >> >> > function='0x0'/> >> >> >> >> system_u:system_r:svirt_t:s0:c194,c775 >> system_u:object_r:svirt_image_t:s0:c194,c775 >> >> >> +107:+107 >> +107:+107 >> >> >> >> On Fri, Jul 5, 2019 at 8:53 PM Simone Tiraboschi >> wrote: >> >>> >>> >>> On Fri, Jul 5, 2019 at 2:48 PM Richard Chan < >>> rich...@treeboxsolutions.com> wrote: >>> Hi, I am running 4.2 engine in a standalone libvirt KVM VM (running on a hypervisor that is not part of the oVirt infrastructure); i.e., I am not using hosted engine but still running engine in a VM. Now 4.3 won't upgrade inside this libvirt KVM VM: Failed to execute stage 'Setup validation': Cannot upgrade the Engine due to low custom_compatibility_version for virtual machines: ['agent03']. Please edit this virtual machines, in edit VM dialog go to System->Advanced Parameters -> Custom Compatibility Version and either reset to empty (cluster default) or set a value supported by the new installation: 4.1, 4.2, 4.3. engine-setup has probably detected that it is running inside a VM: 1. Where did it get 'agent03' string from 2. Any suggestions how to fool engine-setup to think this is 4.3 >>> >>> The engine is not going to check anything on hosts that are unknown at >>> engine eyes. >>> I think that you simply have in the engine a VM called 'agent03'. >>> Please check it. >>> >>> Here is the dmidecode of the standalone engine VM: # dmidecode 3.1 Getting SMBIOS data from sysfs. SMBIOS 2.8 present. 11 structures occupying 591 bytes. Table at 0xBFED7000. Handle 0x0100, DMI type 1, 27 bytes System Information Manufacturer: Red Hat Product Name: KVM Version: RHEL 7.3.0 PC (i440FX + PIIX, 1996) Serial Number: Not Specified UUID: cdb0f3fd-42c7-4a16-bcd1-5d65f19aca19 Wake-up Type: Power Switch SKU Number: Not Specified Family: Red Hat
[ovirt-users] Re: 4.3 won't upgrade engine in standalone KVM VM: low_custom_compatibility_version 'agent03'
On Fri, Jul 5, 2019 at 3:15 PM Simone Tiraboschi wrote: > > > On Fri, Jul 5, 2019 at 3:06 PM Richard Chan > wrote: > >> In libvirt/virsh the VM is called "ovirt7"; here is the domain >> definition. This VM has been upgraded from >> 3.6->4.0->4.1->4.2. This is the first time engine-setup has complained >> about the "level" of the VM. >> >> libvirt domain definition: >> > > oVirt VMs contains something like: > > http://ovirt.org/vm/tune/1.0; xmlns:ovirt-vm=" > http://ovirt.org/vm/1.0;> > > http://ovirt.org/vm/1.0;> > 4.2 > > in the XML for libvirt so you are checking the wrong VM. > Please try executing this on your engine VM: sudo -u postgres scl enable rh-postgresql95 -- psql -d engine -c "select * from vms where vm_name='agent03'" > > >> >> >> ovirt7 >> cdb0f3fd-42c7-4a16-bcd1-5d65f19aca19 >> 8388608 >> 8388608 >> 2 >> >> /machine >> >> >> hvm >> > type='pflash'>/usr/share/edk2.git/ovmf-x64/OVMF_CODE-pure-efi.fd >> /var/lib/libvirt/qemu/nvram/ovirt7_VARS.fd >> >> >> >> >> >> >> >> >> Haswell-noTSX >> >> >> >> >> >> >> >> >> >> >> >> >> >> destroy >> restart >> destroy >> >> >> >> >> >> /usr/libexec/qemu-kvm >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> > file='/var/lib/libvirt/images/ovirt7/database_01.WAEqcow2'/> >> >> >> >> >> >> >> >> >> > function='0x7'/> >> >> >> >> >> > function='0x0' multifunction='on'/> >> >> >> >> >> > function='0x1'/> >> >> >> >> >> > function='0x2'/> >> >> >> >> > function='0x0'/> >> >> >> >> >> >> >> > function='0x0'/> >> >> >> >> >> >> >> >> > function='0x0'/> >> >> >> >> >> >> >> >> >> >> >> >> >> > path='/var/lib/libvirt/qemu/channel/target/domain-15-ovirt7/org.qemu.guest_agent.0'/> >> > state='connected'/> >> >> >> >> >> > state='disconnected'/> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> > function='0x0'/> >> >> >> > primary='yes'/> >> >> > function='0x0'/> >> >> >> >> >> >> >> >> >> >> >> >> > function='0x0'/> >> >> >> >> system_u:system_r:svirt_t:s0:c194,c775 >> system_u:object_r:svirt_image_t:s0:c194,c775 >> >> >> +107:+107 >> +107:+107 >> >> >> >> On Fri, Jul 5, 2019 at 8:53 PM Simone Tiraboschi >> wrote: >> >>> >>> >>> On Fri, Jul 5, 2019 at 2:48 PM Richard Chan < >>> rich...@treeboxsolutions.com> wrote: >>> Hi, I am running 4.2 engine in a standalone libvirt KVM VM (running on a hypervisor that is not part of the oVirt infrastructure); i.e., I am not using hosted engine but still running engine in a VM. Now 4.3 won't upgrade inside this libvirt KVM VM: Failed to execute stage 'Setup validation': Cannot upgrade the Engine due to low custom_compatibility_version for virtual machines: ['agent03']. Please edit this virtual machines, in edit VM dialog go to System->Advanced Parameters -> Custom Compatibility Version and either reset to empty (cluster default) or set a value supported by the new installation: 4.1, 4.2, 4.3. engine-setup has probably detected that it is running inside a VM: 1. Where did it get 'agent03' string from 2. Any suggestions how to fool engine-setup to think this is 4.3 >>> >>> The engine is not going to check anything on hosts that are unknown at >>> engine eyes. >>> I think that you simply have in the engine a VM called 'agent03'. >>> Please check it. >>> >>> Here is the dmidecode of the standalone engine VM: # dmidecode 3.1 Getting SMBIOS data from sysfs. SMBIOS 2.8 present. 11 structures occupying 591 bytes. Table at 0xBFED7000. Handle 0x0100, DMI type 1, 27 bytes System Information Manufacturer: Red Hat Product Name: KVM Version: RHEL 7.3.0 PC (i440FX + PIIX, 1996) Serial Number: Not Specified UUID: cdb0f3fd-42c7-4a16-bcd1-5d65f19aca19 Wake-up Type: Power Switch SKU Number: Not Specified Family: Red Hat Enterprise Linux Handle 0x0300, DMI type 3, 21 bytes Chassis Information Manufacturer: Red Hat Type: Other Lock: Not Present Version: RHEL 7.3.0 PC (i440FX + PIIX, 1996)
[ovirt-users] Re: 4.3 won't upgrade engine in standalone KVM VM: low_custom_compatibility_version 'agent03'
On Fri, Jul 5, 2019 at 3:06 PM Richard Chan wrote: > In libvirt/virsh the VM is called "ovirt7"; here is the domain > definition. This VM has been upgraded from > 3.6->4.0->4.1->4.2. This is the first time engine-setup has complained > about the "level" of the VM. > > libvirt domain definition: > oVirt VMs contains something like: http://ovirt.org/vm/tune/1.0; xmlns:ovirt-vm=" http://ovirt.org/vm/1.0;> http://ovirt.org/vm/1.0;> 4.2 in the XML for libvirt so you are checking the wrong VM. > > > ovirt7 > cdb0f3fd-42c7-4a16-bcd1-5d65f19aca19 > 8388608 > 8388608 > 2 > > /machine > > > hvm > type='pflash'>/usr/share/edk2.git/ovmf-x64/OVMF_CODE-pure-efi.fd > /var/lib/libvirt/qemu/nvram/ovirt7_VARS.fd > > > > > > > > > Haswell-noTSX > > > > > > > > > > > > > > destroy > restart > destroy > > > > > > /usr/libexec/qemu-kvm > > > > > > > > > > > > > > > > > > file='/var/lib/libvirt/images/ovirt7/database_01.WAEqcow2'/> > > > > > > > > >function='0x7'/> > > > > >function='0x0' multifunction='on'/> > > > > >function='0x1'/> > > > > >function='0x2'/> > > > >function='0x0'/> > > > > > > >function='0x0'/> > > > > > > > >function='0x0'/> > > > > > > > > > > > > >path='/var/lib/libvirt/qemu/channel/target/domain-15-ovirt7/org.qemu.guest_agent.0'/> >state='connected'/> > > > > >state='disconnected'/> > > > > > > > > > > > > > > > > > > >function='0x0'/> > > >primary='yes'/> > >function='0x0'/> > > > > > > > > > > > >function='0x0'/> > > > > system_u:system_r:svirt_t:s0:c194,c775 > system_u:object_r:svirt_image_t:s0:c194,c775 > > > +107:+107 > +107:+107 > > > > On Fri, Jul 5, 2019 at 8:53 PM Simone Tiraboschi > wrote: > >> >> >> On Fri, Jul 5, 2019 at 2:48 PM Richard Chan >> wrote: >> >>> Hi, >>> >>> I am running 4.2 engine in a standalone libvirt KVM VM (running on a >>> hypervisor that is not part of the oVirt infrastructure); i.e., I am not >>> using hosted engine but still running engine in a VM. >>> >>> Now 4.3 won't upgrade inside this libvirt KVM VM: >>> >>> Failed to execute stage 'Setup validation': Cannot upgrade the Engine >>> due to low custom_compatibility_version for virtual >>> machines: ['agent03']. Please edit this virtual machines, in edit VM >>> dialog go to System->Advanced Parameters -> Custom Compatibility Version >>> and either reset to empty (cluster default) or set a value supported by the >>> new installation: 4.1, 4.2, 4.3. >>> >>> engine-setup has probably detected that it is running inside a VM: >>> 1. Where did it get 'agent03' string from >>> 2. Any suggestions how to fool engine-setup to think this is 4.3 >>> >> >> The engine is not going to check anything on hosts that are unknown at >> engine eyes. >> I think that you simply have in the engine a VM called 'agent03'. >> Please check it. >> >> >>> >>> Here is the dmidecode of the standalone engine VM: >>> >>> # dmidecode 3.1 >>> Getting SMBIOS data from sysfs. >>> SMBIOS 2.8 present. >>> 11 structures occupying 591 bytes. >>> Table at 0xBFED7000. >>> >>> Handle 0x0100, DMI type 1, 27 bytes >>> System Information >>> Manufacturer: Red Hat >>> Product Name: KVM >>> Version: RHEL 7.3.0 PC (i440FX + PIIX, 1996) >>> Serial Number: Not Specified >>> UUID: cdb0f3fd-42c7-4a16-bcd1-5d65f19aca19 >>> Wake-up Type: Power Switch >>> SKU Number: Not Specified >>> Family: Red Hat Enterprise Linux >>> >>> Handle 0x0300, DMI type 3, 21 bytes >>> Chassis Information >>> Manufacturer: Red Hat >>> Type: Other >>> Lock: Not Present >>> Version: RHEL 7.3.0 PC (i440FX + PIIX, 1996) >>> Serial Number: Not Specified >>> Asset Tag: Not Specified >>> Boot-up State: Safe >>> Power Supply State: Safe >>> Thermal State: Safe >>> Security Status: Unknown >>> OEM Information: 0x >>> Height: Unspecified >>> Number Of Power Cords: Unspecified >>> Contained Elements: 0 >>> >>> Handle 0x0400, DMI type 4, 42 bytes >>> Processor Information >>> Socket Designation: CPU 0 >>> Type: Central Processor >>> Family: Other >>> Manufacturer: Red Hat >>> ID: C1 06 03 00 FF FB 8B 07 >>> Version: RHEL 7.3.0 PC (i440FX + PIIX,
[ovirt-users] Re: 4.3 won't upgrade engine in standalone KVM VM: low_custom_compatibility_version 'agent03'
In libvirt/virsh the VM is called "ovirt7"; here is the domain definition. This VM has been upgraded from 3.6->4.0->4.1->4.2. This is the first time engine-setup has complained about the "level" of the VM. libvirt domain definition: ovirt7 cdb0f3fd-42c7-4a16-bcd1-5d65f19aca19 8388608 8388608 2 /machine hvm /usr/share/edk2.git/ovmf-x64/OVMF_CODE-pure-efi.fd /var/lib/libvirt/qemu/nvram/ovirt7_VARS.fd Haswell-noTSX destroy restart destroy /usr/libexec/qemu-kvm system_u:system_r:svirt_t:s0:c194,c775 system_u:object_r:svirt_image_t:s0:c194,c775 +107:+107 +107:+107 On Fri, Jul 5, 2019 at 8:53 PM Simone Tiraboschi wrote: > > > On Fri, Jul 5, 2019 at 2:48 PM Richard Chan > wrote: > >> Hi, >> >> I am running 4.2 engine in a standalone libvirt KVM VM (running on a >> hypervisor that is not part of the oVirt infrastructure); i.e., I am not >> using hosted engine but still running engine in a VM. >> >> Now 4.3 won't upgrade inside this libvirt KVM VM: >> >> Failed to execute stage 'Setup validation': Cannot upgrade the Engine due >> to low custom_compatibility_version for virtual >> machines: ['agent03']. Please edit this virtual machines, in edit VM >> dialog go to System->Advanced Parameters -> Custom Compatibility Version >> and either reset to empty (cluster default) or set a value supported by the >> new installation: 4.1, 4.2, 4.3. >> >> engine-setup has probably detected that it is running inside a VM: >> 1. Where did it get 'agent03' string from >> 2. Any suggestions how to fool engine-setup to think this is 4.3 >> > > The engine is not going to check anything on hosts that are unknown at > engine eyes. > I think that you simply have in the engine a VM called 'agent03'. > Please check it. > > >> >> Here is the dmidecode of the standalone engine VM: >> >> # dmidecode 3.1 >> Getting SMBIOS data from sysfs. >> SMBIOS 2.8 present. >> 11 structures occupying 591 bytes. >> Table at 0xBFED7000. >> >> Handle 0x0100, DMI type 1, 27 bytes >> System Information >> Manufacturer: Red Hat >> Product Name: KVM >> Version: RHEL 7.3.0 PC (i440FX + PIIX, 1996) >> Serial Number: Not Specified >> UUID: cdb0f3fd-42c7-4a16-bcd1-5d65f19aca19 >> Wake-up Type: Power Switch >> SKU Number: Not Specified >> Family: Red Hat Enterprise Linux >> >> Handle 0x0300, DMI type 3, 21 bytes >> Chassis Information >> Manufacturer: Red Hat >> Type: Other >> Lock: Not Present >> Version: RHEL 7.3.0 PC (i440FX + PIIX, 1996) >> Serial Number: Not Specified >> Asset Tag: Not Specified >> Boot-up State: Safe >> Power Supply State: Safe >> Thermal State: Safe >> Security Status: Unknown >> OEM Information: 0x >> Height: Unspecified >> Number Of Power Cords: Unspecified >> Contained Elements: 0 >> >> Handle 0x0400, DMI type 4, 42 bytes >> Processor Information >> Socket Designation: CPU 0 >> Type: Central Processor >> Family: Other >> Manufacturer: Red Hat >> ID: C1 06 03 00 FF FB 8B 07 >> Version: RHEL 7.3.0 PC (i440FX + PIIX, 1996) >> Voltage: Unknown >> External Clock: Unknown >> Max Speed: 2000 MHz >> Current Speed: 2000 MHz >> Status: Populated, Enabled >> Upgrade: Other >> L1 Cache Handle: Not Provided >> L2 Cache Handle: Not Provided >> L3 Cache Handle: Not Provided >> Serial Number: Not Specified >> Asset Tag: Not Specified >> Part Number: Not Specified >> Core Count: 1 >> Core Enabled: 1 >> Thread Count: 1 >> Characteristics: None >> >> Handle 0x0401, DMI type 4, 42 bytes >> Processor Information >> Socket Designation: CPU 1 >> Type: Central Processor >> Family: Other >> Manufacturer: Red Hat >> ID: C1 06 03 00 FF FB 8B 07 >> Version: RHEL 7.3.0 PC (i440FX + PIIX, 1996) >> Voltage: Unknown >> External Clock: Unknown >> Max Speed: 2000 MHz >> Current Speed: 2000 MHz >> Status: Populated, Enabled >> Upgrade: Other >> L1 Cache Handle: Not Provided >> L2 Cache Handle: Not Provided >> L3 Cache Handle: Not Provided >> Serial Number: Not Specified >> Asset Tag: Not Specified >> Part Number: Not Specified >> Core Count: 1 >> Core Enabled: 1 >> Thread Count: 1 >> Characteristics: None >> >> Handle 0x1000, DMI type 16, 23
[ovirt-users] Re: 4.3 won't upgrade engine in standalone KVM VM: low_custom_compatibility_version 'agent03'
On Fri, Jul 5, 2019 at 2:48 PM Richard Chan wrote: > Hi, > > I am running 4.2 engine in a standalone libvirt KVM VM (running on a > hypervisor that is not part of the oVirt infrastructure); i.e., I am not > using hosted engine but still running engine in a VM. > > Now 4.3 won't upgrade inside this libvirt KVM VM: > > Failed to execute stage 'Setup validation': Cannot upgrade the Engine due > to low custom_compatibility_version for virtual > machines: ['agent03']. Please edit this virtual machines, in edit VM > dialog go to System->Advanced Parameters -> Custom Compatibility Version > and either reset to empty (cluster default) or set a value supported by the > new installation: 4.1, 4.2, 4.3. > > engine-setup has probably detected that it is running inside a VM: > 1. Where did it get 'agent03' string from > 2. Any suggestions how to fool engine-setup to think this is 4.3 > The engine is not going to check anything on hosts that are unknown at engine eyes. I think that you simply have in the engine a VM called 'agent03'. Please check it. > > Here is the dmidecode of the standalone engine VM: > > # dmidecode 3.1 > Getting SMBIOS data from sysfs. > SMBIOS 2.8 present. > 11 structures occupying 591 bytes. > Table at 0xBFED7000. > > Handle 0x0100, DMI type 1, 27 bytes > System Information > Manufacturer: Red Hat > Product Name: KVM > Version: RHEL 7.3.0 PC (i440FX + PIIX, 1996) > Serial Number: Not Specified > UUID: cdb0f3fd-42c7-4a16-bcd1-5d65f19aca19 > Wake-up Type: Power Switch > SKU Number: Not Specified > Family: Red Hat Enterprise Linux > > Handle 0x0300, DMI type 3, 21 bytes > Chassis Information > Manufacturer: Red Hat > Type: Other > Lock: Not Present > Version: RHEL 7.3.0 PC (i440FX + PIIX, 1996) > Serial Number: Not Specified > Asset Tag: Not Specified > Boot-up State: Safe > Power Supply State: Safe > Thermal State: Safe > Security Status: Unknown > OEM Information: 0x > Height: Unspecified > Number Of Power Cords: Unspecified > Contained Elements: 0 > > Handle 0x0400, DMI type 4, 42 bytes > Processor Information > Socket Designation: CPU 0 > Type: Central Processor > Family: Other > Manufacturer: Red Hat > ID: C1 06 03 00 FF FB 8B 07 > Version: RHEL 7.3.0 PC (i440FX + PIIX, 1996) > Voltage: Unknown > External Clock: Unknown > Max Speed: 2000 MHz > Current Speed: 2000 MHz > Status: Populated, Enabled > Upgrade: Other > L1 Cache Handle: Not Provided > L2 Cache Handle: Not Provided > L3 Cache Handle: Not Provided > Serial Number: Not Specified > Asset Tag: Not Specified > Part Number: Not Specified > Core Count: 1 > Core Enabled: 1 > Thread Count: 1 > Characteristics: None > > Handle 0x0401, DMI type 4, 42 bytes > Processor Information > Socket Designation: CPU 1 > Type: Central Processor > Family: Other > Manufacturer: Red Hat > ID: C1 06 03 00 FF FB 8B 07 > Version: RHEL 7.3.0 PC (i440FX + PIIX, 1996) > Voltage: Unknown > External Clock: Unknown > Max Speed: 2000 MHz > Current Speed: 2000 MHz > Status: Populated, Enabled > Upgrade: Other > L1 Cache Handle: Not Provided > L2 Cache Handle: Not Provided > L3 Cache Handle: Not Provided > Serial Number: Not Specified > Asset Tag: Not Specified > Part Number: Not Specified > Core Count: 1 > Core Enabled: 1 > Thread Count: 1 > Characteristics: None > > Handle 0x1000, DMI type 16, 23 bytes > Physical Memory Array > Location: Other > Use: System Memory > Error Correction Type: Multi-bit ECC > Maximum Capacity: 8 GB > Error Information Handle: Not Provided > Number Of Devices: 1 > > Handle 0x1100, DMI type 17, 40 bytes > Memory Device > Array Handle: 0x1000 > Error Information Handle: Not Provided > Total Width: Unknown > Data Width: Unknown > Size: 8192 MB > Form Factor: DIMM > Set: None > Locator: DIMM 0 > Bank Locator: Not Specified > Type: RAM > Type Detail: Other > Speed: Unknown > Manufacturer: Red Hat > Serial Number: Not Specified > Asset Tag: Not Specified > Part Number: Not Specified > Rank: Unknown > Configured Clock Speed: Unknown > Minimum Voltage: Unknown > Maximum Voltage: Unknown > Configured Voltage: Unknown > > Handle 0x1300, DMI type 19, 31 bytes > Memory Array Mapped Address > Starting Address: 0x000 > Ending Address: 0x000BFFF > Range Size: 3 GB > Physical Array Handle: 0x1000 > Partition Width: 1 > > Handle 0x1301, DMI type 19, 31 bytes > Memory Array Mapped Address > Starting Address: 0x001 > Ending Address: 0x0023FFF > Range Size: 5 GB > Physical Array Handle: 0x1000 > Partition Width: 1 > > Handle 0x2000, DMI type 32, 11 bytes > System Boot Information > Status: No errors detected > > Handle 0x, DMI type 0, 24 bytes > BIOS Information > Vendor: EFI Development Kit II / OVMF > Version: 0.0.0 > Release Date: 02/06/2015 > Address: 0xE8000 > Runtime Size: 96 kB > ROM Size: 64 kB > Characteristics: > BIOS characteristics not supported > Targeted content distribution is supported > UEFI is supported > System is a virtual machine > BIOS Revision: 0.0 > > Handle 0xFEFF, DMI type 127, 4 bytes > End
