[ovirt-users] Re: Host not becoming active due to VDSM failure

[Ales Musil]

On Fri, Jul 30, 2021 at 8:54 PM Nir Soffer  wrote:

> On Fri, Jul 30, 2021 at 7:41 PM Vinícius Ferrão via Users
>  wrote:
> ...
> > restore-net::ERROR::2021-07-30
> 12:34:56,167::restore_net_config::462::root::(restore) restoration failed.
> > Traceback (most recent call last):
> >   File
> "/usr/lib/python3.6/site-packages/vdsm/network/restore_net_config.py", line
> 460, in restore
> > unified_restoration()
> >   File
> "/usr/lib/python3.6/site-packages/vdsm/network/restore_net_config.py", line
> 112, in unified_restoration
> > classified_conf = _classify_nets_bonds_config(available_config)
> >   File
> "/usr/lib/python3.6/site-packages/vdsm/network/restore_net_config.py", line
> 237, in _classify_nets_bonds_config
> > net_info = NetInfo(netswitch.configurator.netinfo())
> >   File
> "/usr/lib/python3.6/site-packages/vdsm/network/netswitch/configurator.py",
> line 323, in netinfo
> > _netinfo = netinfo_get(vdsmnets, compatibility)
> >   File "/usr/lib/python3.6/site-packages/vdsm/network/netinfo/cache.py",
> line 268, in get
> > return _get(vdsmnets)
> >   File "/usr/lib/python3.6/site-packages/vdsm/network/netinfo/cache.py",
> line 76, in _get
> > extra_info.update(_get_devices_info_from_nmstate(state, devices))
> >   File "/usr/lib/python3.6/site-packages/vdsm/network/netinfo/cache.py",
> line 165, in _get_devices_info_from_nmstate
> > nmstate.get_interfaces(state, filter=devices)
> >   File "/usr/lib/python3.6/site-packages/vdsm/network/netinfo/cache.py",
> line 164, in 
> > for ifname, ifstate in six.viewitems(
> >   File "/usr/lib/python3.6/site-packages/vdsm/network/nmstate/api.py",
> line 228, in is_dhcp_enabled
> > return util_is_dhcp_enabled(family_info)
> >   File
> "/usr/lib/python3.6/site-packages/vdsm/network/nmstate/bridge_util.py",
> line 137, in is_dhcp_enabled
> > return family_info[InterfaceIP.ENABLED] and
> family_info[InterfaceIP.DHCP]
> > KeyError: 'dhcp'
>
> Looks like a mnstate or NetworkManager bug.
>
> You did not mention any version - are you running the latest ovirt version?
>
> Nir
>
>
Hi,

this was a bug in vdsm, in combination with newer nmstate (>=0.3) that was
fixed in version 4.40.50.3. I would suggest you upgrade past this version.

Best regards,
Ales

-- 

Ales Musil

Software Engineer - RHV Network

Red Hat EMEA 

amu...@redhat.comIM: amusil

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/6QPLGWRQ5NI2C3KKBZY6M62JBZJ6WMZM/

[ovirt-users] adding new host failed with error "CPU does not match the Cluster CPU Type"

[jimod4--- via Users]

i get the below error when i try to add a new kvm host to the cluster.  I know 
that the cpu is a haswell, Intel E5-2640 v3.  if i run "virsh capabilities" it 
returns Haswell-noTSX-IBRS.  My KVM server is redhat 8.4 fully 
patched today on an DL-360 Gen9.  oVirt is at 4.4.7.7-1.el8.  i have tried many 
diffent CPU settings for the cluster and none of them work.  this is new oVirt 
install.

ERROR:
"The host CPU does not match the Cluster CPU Type and is running in a degraded 
mode. It is missing the following CPU flags: vmx, model_Haswell-noTSX, nx. 
Please update the host CPU microcode or change the Cluster CPU Type."

MIRCOCODE:
root@kvm09 ~]# dmesg | grep 'microcode'
[0.00] microcode: microcode updated early to revision 0x46, date = 
2021-01-27
[1.625108] microcode: sig=0x306f2, pf=0x1, revision=0x46
[1.625753] microcode: Microcode Update Driver: v2.2.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/4B2TMR6MGSJF7PG57WBU3IG5CMZP7G2L/

[ovirt-users] adding new host failed with error "CPU does not match the Cluster CPU Type lscpu"

[jimod4--- via Users]

i get the below error when i try to add a new kvm host to the cluster.  I know 
that the cpu is a haswell.  if i run "virsh capabilities" it returns
Haswell-noTSX-IBRS.  My KVM server is redhat 8.4 fully patched 
today on an DL-360 Gen9.  oVirt is at 4.4.7.7-1.el8.  i have tried many diffent 
CPU settings for the cluster and none of them work.  this is new oVirt install.

ERROR:
"The host CPU does not match the Cluster CPU Type and is running in a degraded 
mode. It is missing the following CPU flags: vmx, model_Haswell-noTSX, nx. 
Please update the host CPU microcode or change the Cluster CPU Type."

MIRCOCODE:
root@kvm09 ~]# dmesg | grep 'microcode'
[0.00] microcode: microcode updated early to revision 0x46, date = 
2021-01-27
[1.625108] microcode: sig=0x306f2, pf=0x1, revision=0x46
[1.625753] microcode: Microcode Update Driver: v2.2.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/4MH5XBW7NLL3IQ6RL7FJTNS4UIFMAC2I/

[ovirt-users] Re: Change lease storage domain while VM running

[Klaas Demter]

I wrote an example for changing the lease via python sdk, it was never 
merged though.


https://gerrit.ovirt.org/c/ovirt-engine-sdk/+/99712


Greetings

Klaas

On 7/30/21 4:13 PM, Gianluca Cecchi wrote:

Hello,
on a 4.4.6 environment where I'm moving storage I want to change the 
lease domain for an HA VM.
The VM is running and if I go and edit, change sd and then press ok 
button, I get a window with:


"
Changes that can be applied immediately:

    VM Lease
"

I don't select the "apply later" check box. But then instead when I 
confirm, I get an error window with:


"
vm_name:

    Cannot edit VM. Hot swapping of VM leases is not supported, please 
remove the current lease and then set a new one.

"

Possibly it is possible to hot add a lease but not swap? So I think 
the first window should be changed. Is this a known issue?
No problem if I change the lease storage domain while the VM is 
powered off.


I don't know if it is already fixed in 4.4.7... I'm going to check 
next days..


Gianluca

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/2T75KL33773P3QVF7ZHITEPOZYEIKTUH/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/UNSXXJOVJB2WDHO4IZMXRJEWXXLHUQVF/

[ovirt-users] Re: Change lease storage domain while VM running

[Eyal Shenitzky]

Hi Gianluca,

You can add and remove a VM lease while the VM is running but not swapping
it.
Technically I don't see why we can't implement VM lease swapping (hot
remove + add new) but we should prioritize it first.

If needed please file an RFE for this feature.

On Fri, 30 Jul 2021 at 17:14, Gianluca Cecchi 
wrote:

> Hello,
> on a 4.4.6 environment where I'm moving storage I want to change the lease
> domain for an HA VM.
> The VM is running and if I go and edit, change sd and then press ok
> button, I get a window with:
>
> "
> Changes that can be applied immediately:
>
> VM Lease
> "
>
> I don't select the "apply later" check box. But then instead when I
> confirm, I get an error window with:
>
> "
> vm_name:
>
> Cannot edit VM. Hot swapping of VM leases is not supported, please
> remove the current lease and then set a new one.
> "
>
> Possibly it is possible to hot add a lease but not swap? So I think the
> first window should be changed. Is this a known issue?
> No problem if I change the lease storage domain while the VM is powered
> off.
>
> I don't know if it is already fixed in 4.4.7... I'm going to check next
> days..
>
> Gianluca
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/2T75KL33773P3QVF7ZHITEPOZYEIKTUH/
>


-- 
Regards,
Eyal Shenitzky
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/BM42ISXIOGARCWSXNNYGQLHCURIPGI6C/

[ovirt-users] Re: Upload Image to NFS Storage Domain Doesn't Work

[Eyal Shenitzky]

+Bella Khizgiyaev  can you please take a look?

On Fri, 30 Jul 2021 at 16:15, Nur Imam Febrianto 
wrote:

> Hi,
>
>
>
> Lastly in 4.4.6, I have a problem that I couldn’t upload any image to
> storage domain without clicking Test Connection. Well, after it was
> acknowledge as a bug and solved at 4.4.7 now I have similar issue. If I
> upload any image to Storage Domain that uses NFS it only show locked, and
> then showing OK even if no data are uploaded (can confirm 5GB ISO showing
> OK after only 1 second). This issue only occurs with NFS backend, another
> storage domain that uses iSCSI work fine though. Any idea how to solve this
> ? I’m using NFS Storage Domain for storing ISO and this issue bugged me all
> the time.
>
>
>
> Thanks before.
>
>
>
> Regards,
>
>
>
> Nur Imam Febrianto
>
>
>
>
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/ACUKBWAM2ORQZL3SUH523B7JFWRC7XT3/
>


-- 
Regards,
Eyal Shenitzky
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/R534QUNKCLQHZAJM4QAGRULFNPJ33I33/

[ovirt-users] Re: Self hosted engine installation - Failed to deploy the VM on ISCSI storage

[Yedidyah Bar David]

On Sat, Jul 31, 2021 at 10:15 AM  wrote:
>
> I was trying to install the latest ovirt engine v4.4.7 but it failed at the 
> following step when I was using the command line.
>
> I have tried installing as user root or other sudoers, but same issue.
>
> [ INFO ] changed: [localhost]
> [ INFO ] TASK [ovirt.hosted_engine_setup : Copy configuration archive to 
> storage]
> [ ERROR ] fatal: [localhost]: FAILED! => {"changed": true, "cmd": ["dd", 
> "bs=20480", "count=1", "oflag=direct", 
> "if=/var/tmp/localvmV8yIIX/5607a2c3-7e94-4403-ad86-7c3bcc745b16", 
> "of=/rhev/data-center/mnt/blockSD/61612a87-4b25-4e09-aecd-02b63c679cf1/images/f9ebe70c-58f4-4229-a149-a18a09571d08/5607a2c3-7e94-4403-ad86-"],
>  "delta": "0:00:00.011759", "end": "2020-08-14 09:03:35.702527", "msg": 
> "non-zero return code", "rc": 1, "start": "2020-08-14 09:03:35.690768", 
> "stderr": "dd: failed to open 
> â/var/tmp/localvmV8yIIX/5607a2c3-7e94-4403-ad86-7c3bcc745b16â: Permission 
> denied", "stderr_lines": ["dd: failed to open 
> â/var/tmp/localvmV8yIIX/5607a2c3-7e94-4403-ad86-: Permission 
> denied"], "stdout": "", "stdout_lines": []}
> [ ERROR ] Failed to execute stage 'Closing up': Failed executing 
> ansible-playbook
> [ INFO ] Stage: Clean up
> [ INFO ] Cleaning temporary resources
>
> Just curious if anyone hits the same issue? Thank you.

Seems similar to https://bugzilla.redhat.com/show_bug.cgi?id=1564873 .
Perhaps wrong permissions on /var/tmp, or check 'tar tvf
/usr/share/ovirt-engine-appliance*.ova' .

Best regards,
-- 
Didi
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/KSPDQ74ELD3JZZOCPENKI2USWATIR3G5/

[ovirt-users] Re: Error when trying to change master storage domain

[Shani Leviim]

Hi Matthew,

You might need to sync back the master version and domain between the
engine and vdsm.
To verify those parameters on vdsm, run this command on the SPM host:
vdsm-client StoragePool getInfo
storagepoolID="f72ec125-69a1-4c1b-a5e1-313fcb70b6ff"

The result should be something like:
"info": {
"domains": "1234:Active,5678:Active,91011:Active",
"isoprefix": "",
"lver": 6,

*"master_uuid": "123","master_ver": 14,*
"name": "No Description",
"pool_status": "connected",
"spm_id": 1,
"type": "NFS",
"version": "5"
}


Then, compare the master version value with the engine:
engine=> select * from storage_pool where id =
'f72ec125-69a1-4c1b-a5e1-313fcb70b6ff';

And the master domain:
engine=> select * from storage_domains where
storage_pool_id='f72ec125-69a1-4c1b-a5e1-313fcb70b6ff'  and
storage_domain_type='0';

(0 means master, for reference, see
https://github.com/oVirt/ovirt-engine/blob/a65cf0eae8858ab2278c3f537dc427e3ff20eba7/backend/manager/modules/common/src/main/java/org/ovirt/engine/core/common/businessentities/StorageDomainType.java
)

Then we can get the bigger picture (and update the engine data to match the
vdsm)


*Regards,*

*Shani Leviim*


On Thu, Jul 29, 2021 at 8:40 PM Matthew Benstead  wrote:

> Thanks Shani - yes we plan to upgrade to 4.4 in the future, but we're on
> 4.3 right now due to only running CentOS 7 at the moment.
>
> I was able to clear the job from the SPM:
>
> [root@daccs01 ~]# vdsm-client Host getAllTasksStatuses
> {
> "5fa9edf0-56c3-40e4-9327-47bf7764d28d": {
> "message": "1 jobs completed successfully",
> "code": 0,
> "taskID": "5fa9edf0-56c3-40e4-9327-47bf7764d28d",
> "taskResult": "success",
> "taskState": "finished"
> }
> }
> [root@daccs01 ~]# vdsm-client Task clear
> taskID=5fa9edf0-56c3-40e4-9327-47bf7764d28d
> true
> [root@daccs01 ~]# vdsm-client Host getAllTasksStatuses
> {}
>
> And confirm there were no async_tasks:
>
> engine=# select * from async_tasks;
>  task_id | action_type | status | result | step_id | command_id |
> started_at | storage_pool_id | task_type | vdsm_task_id | root_command_id |
> user_id
>
> -+-+++-+++-+---+--+-+-
> (0 rows)
>
>
> However, when putting the vm-storage-ssd domain into maintenance mode, it
> failed again:
>
>
>
>
>
>
>
>
>
> Here are some the logs entries - anything else I can look at?
>
>
> 2021-07-29 10:30:37,848-07 ERROR
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (EE-ManagedThreadFactory-engineScheduled-Thread-25) [35c5b47] EVENT_ID:
> VDS_BROKER_COMMAND_FAILURE(10,802),
>  VDSM compute7.pcic.uvic.ca command ConnectStoragePoolVDS failed: Wrong
> Master domain or its version: u'SD=a5a83df1-47e2-4927-9add-079199ca7ef8,
> pool=f72ec125-69a1-4c1b-a5e1-313fcb70b6ff'
> 2021-07-29 10:30:37,848-07 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand]
> (EE-ManagedThreadFactory-engineScheduled-Thread-25) [35c5b47] Command
> 'org.ovirt.engine.core.vdsbroker.vd
> sbroker.ConnectStoragePoolVDSCommand' return value 'StatusOnlyReturn
> [status=Status [code=324, message=Wrong Master domain or its version:
> u'SD=a5a83df1-47e2-4927-9add-079199ca7ef8, pool=f72ec125-69a1-4c1b-a5e1-
> 313fcb70b6ff']]'
> ...
> 2021-07-29 10:30:37,848-07 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand]
> (EE-ManagedThreadFactory-engineScheduled-Thread-25) [35c5b47] HostName =
> compute7.pcic.uvic.ca
> 2021-07-29 10:30:37,849-07 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand]
> (EE-ManagedThreadFactory-engineScheduled-Thread-25) [35c5b47] Command
> 'ConnectStoragePoolVDSCommand(HostN
> ame = compute7.pcic.uvic.ca,
> ConnectStoragePoolVDSCommandParameters:{hostId='51769733-0cf6-4270-8288-ec96474b7609',
> vdsId='51769733-0cf6-4270-8288-ec96474b7609',
> storagePoolId='f72ec125-69a1-4c1b-a5e1-313fcb70b6
> ff', masterVersion='288'})' execution failed: IRSGenericException:
> IRSErrorException: IRSNoMasterDomainException: Wrong Master domain or its
> version: u'SD=a5a83df1-47e2-4927-9add-079199ca7ef8, pool=f72ec125-69a1
> -4c1b-a5e1-313fcb70b6ff'
> ...
> 2021-07-29 10:30:37,849-07 ERROR
> [org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand]
> (EE-ManagedThreadFactory-engineScheduled-Thread-25) [35c5b47]
> IrsBroker::Failed::DeactivateStorageDomainVDS: IRSGener
> icException: IRSErrorException: IRSNoMasterDomainException: Wrong Master
> domain or its version: u'SD=a5a83df1-47e2-4927-9add-079199ca7ef8,
> pool=f72ec125-69a1-4c1b-a5e1-313fcb70b6ff'
> 2021-07-29 10:30:37,855-07 INFO
> [org.ovirt.engine.core.vdsbroker.irsbroker.DeactivateStorageDomainVDSCommand]
> (EE-ManagedThreadFactory-engineScheduled-Thread-25) [35c5b47] FINISH,
> DeactivateStorageDomainVDSComm
> and, return: , log id: 

[ovirt-users] Re: Question about cloud-init

[Liran Rotenberg]

On Sat, Jul 31, 2021 at 7:09 AM tommy  wrote:
>
> Hello, I have a question about cloud-init:
>
> After installing vm, I installed cloud-init immediately, and enabled its four 
> services, and then I can use cloud-init in the admin interface.
>
>
>
> However, I don't know how cloud-init knows where to get the relevant 
> information (such as host name, SSH secret key, etc.) that I configured on 
> the admin interface ?  For I haven't configured the data source for 
> cloud-init.

Hi,
The relevant information comes as a payload to the VM, a CD-ROM
containing the data source.
>
> Why it can works ?
>
Cloud-init detects the data source and configures the OS.
Please note that once the VM booted, the only way to provide the
cloud-init payload is by using Run-Once.
For a VM that didn't boot, a regular run will work as well.

Regards,
Liran
>
>
> Thanks!
>
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct: 
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives: 
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/O5NKQO5642X3WYES3QQBSSDZUQN6N5XX/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/NVP4IUIN7NQDI5OVN6NRKJQYQBMJ7M77/