Bad libvirt-spice certificate - regenerate?
by Chris Adams
I have an oVirt 4.1 cluster that was initially installed with 3.5 in
2014. The SSL certificates on the physical hosts in
/etc/pki/vdsm/libvirt-spice have a problem - the "not before" date is
invalid (it doesn't include a time zone), and so I can't connect to VM
consoles from a client with OpenSSL 1.1.0i (up to date Fedora 27).
How can I regenerate these certificates?
Also, I noticed they expire next year - is that expiration handled
automatically?
--
Chris Adams <cma(a)cmadams.net>
6 years, 1 month
Error when running hosted-engine deploy on system with bond of bonds
by Ben Webber
Hi,
I'm trying to set up ovirt using the hosted-engine --deploy command on CentOS7, but am encountering an error. I am running a slightly unusual network configuration. I have two fairly basic non stacked gigabit switches with port channels connecting the two switches together. I have a lacp bond from the host consisting of 4 ports to each switch (bond1 and bond2). I have then created an active-backup bond (bond0) using the two lacp bonds as slaves in the hope to create ha at the switch layer using my basic switches. There is then a VLAN (101) on bond0.
This network configuration runs fine on the host, however, when run, after a short while, the hosted-engine --deploy command outputs the following error:
...
[ INFO ] TASK [Force host-deploy in offline mode]
[ INFO ] ok: [localhost]
[ INFO ] TASK [Add host]
[ INFO ] changed: [localhost]
[ INFO ] TASK [Wait for the host to be up]
[ INFO ] ok: [localhost]
[ INFO ] TASK [Check host status]
[ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "The host has been set in non_operational status, please check engine logs, fix accordingly and re-deploy.\n"}
...
Looking in /var/log/ovirt-engine/engine.log on the machine created, I can see the following errors logged:
...
2018-10-04 21:51:30,116+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (EE-ManagedThreadFactory-engine-Thread-1) [59fb360a] START, HostSetupNetworksVDSCommand(HostName = ov1.test.local, HostSetupNetworksVdsCommandParameters:{hostId='7440c9b9-e530-4341-a317-d3a9041dc777', vds='Host[ov1.test.local,7440c9b9-e530-4341-a317-d3a9041dc777]', rollbackOnFailure='true', connectivityTimeout='120', networks='[HostNetwork:{defaultRoute='true', bonding='true', networkName='ovirtmgmt', vdsmName='ovirtmgmt', nicName='bond0', vlan='101', vmNetwork='true', stp='false', properties='null', ipv4BootProtocol='STATIC_IP', ipv4Address='192.168.1.11', ipv4Netmask='255.255.255.0', ipv4Gateway='192.168.1.1', ipv6BootProtocol='AUTOCONF', ipv6Address='null', ipv6Prefix='null', ipv6Gateway='null', nameServers='null'}]', removedNetworks='[]', bonds='[]', removedBonds='[]', clusterSwitchType='LEGACY'}), log id: 4f0c7eaa
2018-10-04 21:51:30,121+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (EE-ManagedThreadFactory-engine-Thread-1) [59fb360a] FINISH, HostSetupNetworksVDSCommand, log id: 4f0c7eaa
2018-10-04 21:51:30,645+01 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (EE-ManagedThreadFactory-engine-Thread-1) [59fb360a] Failed in 'HostSetupNetworksVDS' method
2018-10-04 21:51:30,687+01 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-1) [59fb360a] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM ov1.test.local command HostSetupNetworksVDS failed: Unknown nics in: ['bond1', 'bond2']
2018-10-04 21:51:30,688+01 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (EE-ManagedThreadFactory-engine-Thread-1) [59fb360a] Error: VDSGenericException: VDSErrorException: Failed to HostSetupNetworksVDS, error = Unknown nics in: ['bond1', 'bond2'], code = 23
...
It looks like when HostSetupNetworksVDS is run, it is checking that the slave interfaces to the bonds are physical network devices and being as the slaves of bond0 are bond1 and bond2, rather than physical devices, it then throws the error Unknown nics in: ['bond1', 'bond2'].
Is there anything I can do or any configuration that I can put anywhere to make it work with this "stacked bond" configuration or does ovirt just not work when bonds are set up like this?
Thanks in advance,
Ben
6 years, 1 month
Failed to lock byte 100 - when booting VM with attached CD
by Simon Vincent
I have found recently I can't boot any VMs which have a CD attached to it.
I get the following error.
VM Test is down with error. Exit message: internal error: qemu unexpectedly
closed the monitor: 2018-10-04T11:53:07.031875Z qemu-kvm: -device
ide-cd,bus=ide.1,unit=0,drive=drive-ua-5ccd6310-a1e5-4019-b989-795529c70794,id=ua-5ccd6310-a1e5-4019-b989-795529c70794,bootindex=2:
Failed to lock byte 100 2018-10-04T11:53:07.032264Z qemu-kvm: -device
ide-cd,bus=ide.1,unit=0,drive=drive-ua-5ccd6310-a1e5-4019-b989-795529c70794,id=ua-5ccd6310-a1e5-4019-b989-795529c70794,bootindex=2:
Failed to lock byte 100 2018-10-04T11:53:07.032285Z qemu-kvm: -device
ide-cd,bus=ide.1,unit=0,drive=drive-ua-5ccd6310-a1e5-4019-b989-795529c70794,id=ua-5ccd6310-a1e5-4019-b989-795529c70794,bootindex=2:
Failed to lock byte 100 Unexpected error in raw_apply_lock_bytes() at
block/file-posix.c:642: 2018-10-04T11:53:07.032665Z qemu-kvm: -device
ide-cd,bus=ide.1,unit=0,drive=drive-ua-5ccd6310-a1e5-4019-b989-795529c70794,id=ua-5ccd6310-a1e5-4019-b989-795529c70794,bootindex=2:
Failed to lock byte 100.
I have tried relaxing the permissions on the iSO NFS share and even removed
the iSO domain and added a new one, but I still get the problem.
Regards
Simon
6 years, 1 month
iso domain don't list available images
by Nathanaël Blanchet
Hello,
I detached an existing iso domain from an other ovirt instance and
attached it to on a fresh 4.2 install, but no images are available. Is
it a known bug?
--
Nathanaël Blanchet
Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5
Tél. 33 (0)4 67 54 84 55
Fax 33 (0)4 67 54 84 14
blanchet(a)abes.fr
6 years, 1 month
Unable to mount CephFS as POSIX Compliant FS
by ryan.terpstra＠gmail.com
I have a ceph filesystem that I can manually mount on my ovirt host.
[root@ovirt121 ~]# mount -t ceph ceph01:/ /mnt -o name=admin,secret=<secret removed for security>
[root@ovirt121 ~]# touch /mnt/test
works great! Then I umount that filesystem and attempt to add storage domain in ovirt engine. Settings:
Storage type: POSIX compliant FS
Host to use: ovirt121
name: cephdata
Path: ceph01:/
vfs type: ceph
mount options: name=admin,secret=<secret removed for security>
In the oVirt web UI I get a "General Exception" error. On the host I see this in vdsm.log:
2018-10-03 23:47:58,165+0000 INFO (jsonrpc/6) [vdsm.api] START connectStorageServer(domType=6, spUUID=u'00000000-0000-0000-0000-000000000000', conList=[{u'mnt_options': u'name=admin,secret=AQDJI7RbS4Z2GhAAhlyWUvX7wtPNzO6n5vqjsQ==', u'id': u'00000000-0000-0000-0000-000000000000', u'connection': u'ceph01:/', u'iqn': u'', u'user': u'', u'tpgt': u'1', u'vfs_type': u'ceph', u'password': '********', u'port': u''}], options=None) from=::ffff:10.78.7.221,54910, flow_id=ba106a2d-e204-4da7-acc7-29b70c3ff759, task_id=b5e0c87c-8838-4b49-8590-11382a02d67f (api:46)
2018-10-03 23:47:58,166+0000 INFO (jsonrpc/6) [storage.StorageServer.MountConnection] Creating directory u'/rhev/data-center/mnt/ceph01:_' (storageServer:167)
2018-10-03 23:47:58,166+0000 INFO (jsonrpc/6) [storage.fileUtils] Creating directory: /rhev/data-center/mnt/ceph01:_ mode: None (fileUtils:197)
2018-10-03 23:47:58,166+0000 INFO (jsonrpc/6) [storage.Mount] mounting ceph01:/ at /rhev/data-center/mnt/ceph01:_ (mount:204)
2018-10-03 23:47:58,218+0000 ERROR (jsonrpc/6) [storage.HSM] Could not connect to storageServer (hsm:2415)
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 2412, in connectStorageServer
conObj.connect()
File "/usr/lib/python2.7/site-packages/vdsm/storage/storageServer.py", line 183, in connect
self.getMountObj().getRecord().fs_file)
File "/usr/lib/python2.7/site-packages/vdsm/storage/mount.py", line 253, in getRecord
(self.fs_spec, self.fs_file))
OSError: [Errno 2] Mount of `ceph01:/` at `/rhev/data-center/mnt/ceph01:_` does not exist
2018-10-03 23:47:58,218+0000 INFO (jsonrpc/6) [vdsm.api] FINISH connectStorageServer return={'statuslist': [{'status': 100, 'id': u'00000000-0000-0000-0000-000000000000'}]} from=::ffff:10.78.7.221,54910, flow_id=ba106a2d-e204-4da7-acc7-29b70c3ff759, task_id=b5e0c87c-8838-4b49-8590-11382a02d67f (api:52)
However, if i run "monut" or "cat /proc/mounts" I can see the cephfs was properly mounted, I can even touch files.
[root@ovirt121 ~]# touch /rhev/data-center/mnt/ceph01\:_/ceph_ovirt_test
[root@ovirt121 ~]#
[root@ovirt121 ~]# cat /proc/mounts
<...bunch of mounts...>
10.78.71.1:/ /rhev/data-center/mnt/ceph01:_ ceph rw,relatime,name=admin,secret=<hidden>,acl,wsize=16777216 0 0
[root@ovirt121 ~]#
Any thoughts?
oVirt version is 4.2.6.4-1.el7, running on CentOS 7 18.05.
6 years, 1 month
no space left to upgrade hosted-engine
by Nathanaël Blanchet
I've deployed and hosted-engine with the hosted-engine provided appliance.
When runing hosted-engine --upgrade-appliance on one host, it tells me
"If your engine VM is already based on el7 you can also simply upgrade
the engine there."
So I launched a yum update on the hosted-engine, but it complains there
is no space left on /
[root@infra ~]# df -h
Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur
/dev/vda3 6,2G 6,2G 20K 100% /
devtmpfs 7,8G 0 7,8G 0% /dev
tmpfs 7,8G 4,0K 7,8G 1% /dev/shm
tmpfs 7,8G 9,0M 7,8G 1% /run
tmpfs 7,8G 0 7,8G 0% /sys/fs/cgroup
/dev/mapper/ovirt-home 1014M 33M 982M 4% /home
/dev/mapper/ovirt-tmp 2,0G 33M 2,0G 2% /tmp
/dev/vda1 1014M 162M 853M 16% /boot
/dev/mapper/ovirt-var 20G 631M 20G 4% /var
/dev/mapper/ovirt-log 10G 58M 10G 1% /var/log
/dev/mapper/ovirt-audit 1014M 59M 956M 6% /var/log/audit
tmpfs 1,6G 0 1,6G 0% /run/user/0
Is the only way is to deploy the new appliance?
--
Nathanaël Blanchet
Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5
Tél. 33 (0)4 67 54 84 55
Fax 33 (0)4 67 54 84 14
blanchet(a)abes.fr
6 years, 1 month
ODL and Openstack issue
by Soujanya Bargavi
I am running one controller and one compute node. Controller node is running both ODL and OpenStack. I created tenants, underthem i created networks and launched instances on them. All is see on ODL web GUI is 3 swithces, and I guess those are br-int and br-ex of controller and br-int of compute and the links are missing too. Is there anyway where I can see my whole OpenStack https://goo.gl/6CgufL topology on ODL GUI with the links?
6 years, 1 month
Reg: Enabling Nested virtualization.
by syedquadeer＠ctel.in
Dear Team,
Need help to enable nested virtualization in Ovirt VM's.
As when I checked my cpu info and kvm acceleration info, it is giving below
output.
# kvm-ok
INFO: Your CPU does not support KVM extensions
KVM acceleration can NOT be used
# cat /sys/module/kvm/parameters/nested
cat: /sys/module/kvm/parameters/nested: No such file or directory
# virsh -r list
Id Name State
----------------------------------------------------
Thanks & Regards,
Syed Abdul Qadeer.
7660022818.
6 years, 1 month
