- Users - oVirt List Archives

Re: ovirt 4.2 HCI rollout
by Simone Tiraboschi 24 Jan '19

24 Jan '19

On Thu, Jan 24, 2019 at 2:21 PM Markus Schaufler < markus.schaufler(a)digit-all.at> wrote: > Hi, > > > thanks for the replies. > > > I updated to 4.2.8 and tried again: > > > [ INFO ] TASK [Check engine VM health] > [ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 120, "changed": > true, "cmd": ["hosted-engine", "--vm-status", "--json"], "delta": > "0:00:00.165316", "end": "2019-01-24 14:12:06.899564", "rc": 0, "start": > "2019-01-24 14:12:06.734248", "stderr": "", "stderr_lines": [], "stdout": > "{\"1\": {\"conf_on_shared_storage\": true, \"live-data\": true, \"extra\": > \"metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=3049 > (Thu Jan 24 14:11:59 > 2019)\\nhost-id=1\\nscore=3400\\nvm_conf_refresh_time=3049 (Thu Jan 24 > 14:11:59 > 2019)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineStarting\\nstopped=False\\n\", > \"hostname\": \"HCI01.res01.ads.ooe.local\", \"host-id\": 1, > \"engine-status\": {\"reason\": \"failed liveliness check\", \"health\": > \"bad\", \"vm\": \"up\", \"detail\": \"Up\"}, \"score\": 3400, \"stopped\": > false, \"maintenance\": false, \"crc32\": \"0c1a3ddb\", > \"local_conf_timestamp\": 3049, \"host-ts\": 3049}, \"global_maintenance\": > false}", "stdout_lines": ["{\"1\": {\"conf_on_shared_storage\": true, > \"live-data\": true, \"extra\": > \"metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=3049 > (Thu Jan 24 14:11:59 > 2019)\\nhost-id=1\\nscore=3400\\nvm_conf_refresh_time=3049 (Thu Jan 24 > 14:11:59 > 2019)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineStarting\\nstopped=False\\n\", > \"hostname\": \"HCI01.res01.ads.ooe.local\", \"host-id\": 1, > \"engine-status\": {\"reason\": \"failed liveliness check\", \"health\": > \"bad\", \"vm\": \"up\", \"detail\": \"Up\"}, \"score\": 3400, \"stopped\": > false, \"maintenance\": false, \"crc32\": \"0c1a3ddb\", > \"local_conf_timestamp\": 3049, \"host-ts\": 3049}, \"global_maintenance\": > false}"]} > It's still the same issue: the host fail to properly check the status of the engine over a dedicate health page. You should connect to ovirt-hci.res01.ads.ooe.local and check the status of ovirt-engine service and /var/log/ovirt-engine/engine.log there. > [ INFO ] TASK [Check VM status at virt level] > [ INFO ] changed: [localhost] > [ INFO ] TASK [Fail if engine VM is not running] > [ INFO ] skipping: [localhost] > [ INFO ] TASK [Get target engine VM IPv4 address] > [ INFO ] changed: [localhost] > [ INFO ] TASK [Get VDSM's target engine VM stats] > [ INFO ] changed: [localhost] > [ INFO ] TASK [Convert stats to JSON format] > [ INFO ] ok: [localhost] > [ INFO ] TASK [Get target engine VM IPv4 address from VDSM stats] > [ INFO ] ok: [localhost] > [ INFO ] TASK [Fail if the Engine has no IP address] > [ INFO ] skipping: [localhost] > [ INFO ] TASK [Fail if Engine IP is different from engine's FQDN resolved > IP] > [ INFO ] skipping: [localhost] > [ INFO ] TASK [Get target engine VM IPv4 address] > [ INFO ] skipping: [localhost] > [ INFO ] TASK [Reconfigure OVN central address] > [ ERROR ] fatal: [localhost]: FAILED! => {"msg": "The task includes an > option with an undefined variable. The error was: 'dict object' has no > attribute 'stdout_lines'\n\nThe error appears to have been in > '/usr/share/ovirt-hosted-engine-setup/ansible/create_target_vm.yml': line > 518, column 5, but may\nbe elsewhere in the file depending on the exact > syntax problem.\n\nThe offending line appears to be:\n\n # > https://github.com/oVirt/ovirt-engine/blob/master/packaging/playbooks/roles… > - name: Reconfigure OVN central address\n ^ here\n"} > > > > attached you'll find the setup logs. > > > best regards, > > Markus Schaufler > ------------------------------ > *Von:* Simone Tiraboschi <stirabos(a)redhat.com> > *Gesendet:* Donnerstag, 24. Jänner 2019 11:56:50 > *An:* Dominik Holler > *Cc:* Markus Schaufler; users(a)ovirt.org > *Betreff:* Re: [ovirt-users] ovirt 4.2 HCI rollout > > > > On Thu, Jan 24, 2019 at 9:40 AM Dominik Holler <dholler(a)redhat.com> wrote: > > On Tue, 22 Jan 2019 11:15:12 +0000 > Markus Schaufler <markus.schaufler(a)digit-all.at> wrote: > > > Thanks for your reply, > > > > getent ahosts ovirt-hci.res01.ads.ooe.local | cut -d' ' -f1 | uniq > > 10.1.31.20 > > > > attached you'll find the logs. > > > > Thanks, to my eyes this looks like a bug. > I tried to isolate the relevant lines in the attached playbook. > > Markus, would you be so kind to check if ovirt-4.2.8 is working for you? > > > > OK, understood: the real error was just a few lines before what Dominik > pointed out: > > "stdout": "{\"1\": {\"conf_on_shared_storage\": true, \"live-data\": > true, \"extra\": > \"metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=5792 > (Mon Jan 21 13:57:45 > 2019)\\nhost-id=1\\nscore=3000\\nvm_conf_refresh_time=5792 (Mon Jan 21 > 13:57:45 > 2019)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineStarting\\nstopped=False\\n\", > \"hostname\": \"HCI01.res01.ads.ooe.local\", \"host-id\": 1, > \"engine-status\": {\"reason\": \"failed liveliness check\", \"health\": > \"bad\", \"vm\": \"up\", \"detail\": \"Up\"}, \"score\": 3000, \"stopped\": > false, \"maintenance\": false, \"crc32\": \"ba303717\", > \"local_conf_timestamp\": 5792, \"host-ts\": 5792}, \"global_maintenance\": > false}", > "stdout_lines": [ > "{\"1\": {\"conf_on_shared_storage\": true, \"live-data\": true, > \"extra\": > \"metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=5792 > (Mon Jan 21 13:57:45 > 2019)\\nhost-id=1\\nscore=3000\\nvm_conf_refresh_time=5792 (Mon Jan 21 > 13:57:45 > 2019)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineStarting\\nstopped=False\\n\", > \"hostname\": \"HCI01.res01.ads.ooe.local\", \"host-id\": 1, > \"engine-status\": {\"reason\": \"failed liveliness check\", \"health\": > \"bad\", \"vm\": \"up\", \"detail\": \"Up\"}, \"score\": 3000, \"stopped\": > false, \"maintenance\": false, \"crc32\": \"ba303717\", > \"local_conf_timestamp\": 5792, \"host-ts\": 5792}, \"global_maintenance\": > false}" > ] > }" > 2019-01-21 13:57:46,695+0100 ERROR ansible failed {'status': 'FAILED', > 'ansible_type': 'task', 'ansible_task': u'Check engine VM health', > 'ansible_result': u'type: <type \'dict\'>\nstr: {\'_ansible_parsed\': True, > \'stderr_lines\': [], u\'changed\': True, u\'end\': u\'2019-01-21 > 13:57:46.242423\', \'_ansible_no_log\': False, u\'stdout\': u\'{"1": > {"conf_on_shared_storage": true, "live-data": true, "extra": > "metadata_parse_version=1\\\\nmetadata_feature_version=1\\\\ntimestamp=5792 > (Mon Jan 21 13:57:4', 'ansible_host': u'localhost', 'ansible_playbook': > u'/usr/share/ovirt-hosted-engine-setup/ansible/create_target_vm.yml'} > > and in particular it's here: > for some reason we got \"engine-status\": {\"reason\": \"failed > liveliness check\", \"health\": \"bad\", \"vm\": \"up\", \"detail\": > \"Up\"} > over 120 attempts: we have to check engine.log (it got collected as well > from the engine VM) to understand why the engine was failing to start. > > > > > > ________________________________ > > Von: Dominik Holler <dholler(a)redhat.com> > > Gesendet: Montag, 21. Jänner 2019 17:52:35 > > An: Markus Schaufler > > Cc: users(a)ovirt.org; Simone Tiraboschi > > Betreff: Re: [ovirt-users] ovirt 4.2 HCI rollout > > > > Would you please share the related ovirt-host-deploy-ansible-*.log > > stored on the host in /var/log/ovirt-hosted-engine-setup ? > > > > Would you please also share the output of > > getent ahosts YOUR_HOSED_ENGNE_FQDN | cut -d' ' -f1 | uniq > > if executed on this host? > > > > > > On Mon, 21 Jan 2019 13:37:53 -0000 > > "Markus Schaufler" <markus.schaufler(a)digit-all.at> wrote: > > > > > Hi, > > > > > > I'm trying a (nested) ovirt 4.2.7 HCI rollout on 3 centos VM's by > > > following > > > > https://ovirt.org/documentation/gluster-hyperconverged/chap-Deploying_Hyper… > > > gluster deployment was successful but at HE deployment "stage 5" I > > > got following error: > > > > > > [ INFO ] TASK [Reconfigure OVN central address] > > > [ ERROR ] fatal: [localhost]: FAILED! => {"msg": "The task includes > > > an option with an undefined variable. The error was: 'dict object' > > > has no attribute 'stdout_lines'\n\nThe error appears to have been > > > in > > > '/usr/share/ovirt-hosted-engine-setup/ansible/create_target_vm.yml': > > > line 522, column 5, but may\nbe elsewhere in the file depending on > > > the exact syntax problem.\n\nThe offending line appears to be:\n\n > > > # > > > > https://github.com/oVirt/ovirt-engine/blob/master/packaging/playbooks/roles… > > > - name: Reconfigure OVN central address\n ^ here\n"} > > > > > > > > > /var/log/messages: > > > Jan 21 14:09:56 HCI01 journal: ovirt-ha-agent > > > ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine ERROR > > > Engine VM stopped on localhost Jan 21 14:10:01 HCI01 systemd: > > > Started Session 22 of user root. Jan 21 14:10:02 HCI01 systemd: > > > Started Session c306 of user root. Jan 21 14:10:03 HCI01 systemd: > > > Started Session c307 of user root. Jan 21 14:10:06 HCI01 > > > vdsm[3650]: WARN executor state: count=5 workers=set([<Worker > > > name=periodic/4 waiting task#=141 at 0x7fd2d4316910>, <Worker > > > name=periodic/1 running <Task discardable <Operation > > > action=<vdsm.virt.sampling.VMBulkstatsMonitor object at > > > 0x7fd2d4679490> at 0x7fd2d4679710> timeout=7.5, duration=7 at > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> disca rded task#=413 at > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>, <Worker > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>name=periodic/3 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>waiting task#=414 at > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>, > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10><Worker > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>name=periodic/5 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>waiting > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>task#=0 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>at > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>, > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650><Worker > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>name > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>=periodic/2 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>waiting > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>task#=412 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>at > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>]) > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>Jan > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>21 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>14:10:06 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>HCI01 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>kernel: > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>ovirtmgmt: > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>port > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>2(vnet0) > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>entered > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>disabled > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>state > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>Jan > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>21 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>14:10:06 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>HCI01 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>kernel: > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>device > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>vnet0 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>left > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>promiscuous > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>mode > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>Jan > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>21 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>14:10:06 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>HCI01 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>kernel: > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>ovirtmgmt: > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>port > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>2(vnet0) > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>entered > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>disabled > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>state > > > Jan 21 14:10:06 HCI01 NetworkManager[3666]: <info> > > > [1548076206.9177] device (vnet0): state change: disconnected -> > > > unmanaged (reason 'unmanaged', sys-iface-state: 'remo ved') Jan 21 > > > 14:10:06 HCI01 NetworkManager[3666]: <info> [1548076206.9180] > > > device (vnet0): released from master device ovirtmgmt Jan 21 > > > 14:10:06 HCI01 lldpad: recvfrom(Event interface): No buffer space > > > available Jan 21 14:10:06 HCI01 libvirtd: 2019-01-21 > > > 13:10:06.925+0000: 2651: error : qemuMonitorIORead:609 : Unable to > > > read from monitor: Connection reset by peer Jan 21 14:10:07 HCI01 > > > kvm: 0 guests now active Jan 21 14:10:07 HCI01 systemd-machined: > > > Machine qemu-3-HostedEngine terminated. Jan 21 14:10:07 HCI01 > > > libvirtd: 2019-01-21 13:10:07.125+0000: 2704: warning : > > > qemuGetProcessInfo:1406 : cannot parse process status data Jan 21 > > > 14:10:07 HCI01 libvirtd: 2019-01-21 13:10:07.125+0000: 2704: > > > warning : qemuGetProcessInfo:1406 : cannot parse process status > > > data Jan 21 14:10:07 HCI01 libvirtd: 2019-01-21 13:10:07.125+0000: > > > 2704: warning : qemuGetProcessInfo:1406 : cannot parse process > > > status data Jan 21 14:10:07 HCI01 libvirtd: 2019-01-21 > > > 13:10:07.125+0000: 2704: warning : qemuGetProcessInfo:1406 : cannot > > > parse process status data Jan 21 14:10:07 HCI01 libvirtd: > > > 2019-01-21 13:10:07.126+0000: 2704: error : > > > virNetDevTapInterfaceStats:764 : internal error: /proc/net/dev: > > > Interface not found Jan 21 14:10:07 HCI01 firewalld[24040]: > > > WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -D libvirt-out > > > -m physdev --physdev-is-bridged --physdev-out vnet0 -g FP-vnet 0' > > > failed: iptables v1.4.21: goto 'FP-vnet0' is not a chain#012#012Try > > > `iptables -h' or 'iptables --help' for more information. Jan 21 > > > 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/iptables -w2 -w -D libvirt-out -m physdev --physdev-out > > > vnet0 -g FP-vnet0' failed: iptables v 1.4.21: goto 'FP-vnet0' is > > > not a chain#012#012Try `iptables -h' or 'iptables --help' for more > > > information. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -D libvirt-in -m physdev > > > --physdev-in vnet0 -g FJ-vnet0' failed: iptables v1. 4.21: goto > > > 'FJ-vnet0' is not a chain#012#012Try `iptables -h' or 'iptables > > > --help' for more information. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > > -w -D libvirt-host-in -m physdev --physdev-in vnet0 -g HJ-vnet0' > > > failed: iptable s v1.4.21: goto 'HJ-vnet0' is not a > > > chain#012#012Try `iptables -h' or 'iptables --help' for more > > > information. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -F FP-vnet0' failed: > > > iptables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > > -w -X FP-vnet0' failed: iptables: No chain/target/match by that > > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -F FJ-vnet0' failed: > > > iptables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > > -w -X FJ-vnet0' failed: iptables: No chain/target/match by that > > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -F HJ-vnet0' failed: > > > iptables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > > -w -X HJ-vnet0' failed: iptables: No chain/target/match by that > > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -D libvirt-out -m > > > physdev --physdev-is-bridged --physdev-out vnet0 -g FP-vne t0' > > > failed: ip6tables v1.4.21: goto 'FP-vnet0' is not a > > > chain#012#012Try `ip6tables -h' or 'ip6tables --help' for more > > > information. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -D libvirt-out -m > > > physdev --physdev-out vnet0 -g FP-vnet0' failed: ip6tables v1.4.21: > > > goto 'FP-vnet0' is not a chain#012#012Try `ip6tables -h' or > > > 'ip6tables --help' for more information. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 > > > -w -D libvirt-in -m physdev --physdev-in vnet0 -g FJ-vnet0' failed: > > > ip6tables v 1.4.21: goto 'FJ-vnet0' is not a chain#012#012Try > > > `ip6tables -h' or 'ip6tables --help' for more information. Jan 21 > > > 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ip6tables -w2 -w -D libvirt-host-in -m physdev > > > --physdev-in vnet0 -g HJ-vnet0' failed: ip6tab les v1.4.21: goto > > > 'HJ-vnet0' is not a chain#012#012Try `ip6tables -h' or 'ip6tables > > > --help' for more information. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 > > > -w -F FP-vnet0' failed: ip6tables: No chain/target/match by that > > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -X FP-vnet0' failed: > > > ip6tables: No chain/target/match by that name. Jan 21 14:10:07 > > > HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ip6tables -w2 -w -F FJ-vnet0' failed: ip6tables: No > > > chain/target/match by that name. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 > > > -w -X FJ-vnet0' failed: ip6tables: No chain/target/match by that > > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -F HJ-vnet0' failed: > > > ip6tables: No chain/target/match by that name. Jan 21 14:10:07 > > > HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ip6tables -w2 -w -X HJ-vnet0' failed: ip6tables: No > > > chain/target/match by that name. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables > > > --concurrent -t nat -D PREROUTING -i vnet0 -j libvirt-J-vnet0' > > > failed: Illegal target name 'libvirt-J-vnet0'. Jan 21 14:10:07 > > > HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ebtables --concurrent -t nat -D POSTROUTING -o vnet0 -j > > > libvirt-P-vnet0' failed: Illegal target name 'libvirt-P-vnet0'. Jan > > > 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ebtables --concurrent -t nat -D PREROUTING -i vnet0 -j > > > libvirt-J-vnet0' failed: Illegal targe t name 'libvirt-J-vnet0'. > > > Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ebtables --concurrent -t nat -D POSTROUTING -o vnet0 -j > > > libvirt-P-vnet0' failed: Illegal targ et name 'libvirt-P-vnet0'. > > > Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ebtables --concurrent -t nat -L libvirt-J-vnet0' failed: > > > Chain 'libvirt-J-vnet0' doesn't exis t. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables > > > --concurrent -t nat -L libvirt-P-vnet0' failed: Chain > > > 'libvirt-P-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables > > > --concurrent -t nat -F libvirt-J-vnet0' failed: Chain > > > 'libvirt-J-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables > > > --concurrent -t nat -X libvirt-J-vnet0' failed: Chain > > > 'libvirt-J-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables > > > --concurrent -t nat -F libvirt-P-vnet0' failed: Chain > > > 'libvirt-P-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables > > > --concurrent -t nat -X libvirt-P-vnet0' failed: Chain > > > 'libvirt-P-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > > -w -D libvirt-out -m physdev --physdev-is-bridged --physdev-out > > > vnet0 -g FO-vnet0' failed: iptables v1.4.21: goto 'FO-vnet0' is not > > > a chain#012#012Try `iptables -h' or 'iptables --help' for more > > > information. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -D libvirt-out -m > > > physdev --physdev-out vnet0 -g FO-vnet0' failed: iptables v1.4.21: > > > goto 'FO-vnet0' is not a chain#012#012Try `iptables -h' or > > > 'iptables --help' for more information. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > > -w -D libvirt-in -m physdev --physdev-in vnet0 -g FI-vnet0' failed: > > > iptables v1.4.21: goto 'FI-vnet0' is not a chain#012#012Try > > > `iptables -h' or 'iptables --help' for more information. Jan 21 > > > 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/iptables -w2 -w -D libvirt-host-in -m physdev > > > --physdev-in vnet0 -g HI-vnet0' failed: iptables v1.4.21: goto > > > 'HI-vnet0' is not a chain#012#012Try `iptables -h' or 'iptables > > > --help' for more information. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > > -w -D libvirt-in-post -m physdev --physdev-in vnet0 -j ACCEPT' > > > failed: iptables: Bad rule (does a matching rule exist in that > > > chain?). Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -F FO-vnet0' failed: > > > iptables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > > -w -X FO-vnet0' failed: iptables: No chain/target/match by that > > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -F FI-vnet0' failed: > > > iptables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > > -w -X FI-vnet0' failed: iptables: No chain/target/match by that > > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -F HI-vnet0' failed: > > > iptables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > > -w -X HI-vnet0' failed: iptables: No chain/target/match by that > > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -D libvirt-out -m > > > physdev --physdev-is-bridged --physdev-out vnet0 -g FO-vnet0' > > > failed: ip6tables v1.4.21: goto 'FO-vnet0' is not a > > > chain#012#012Try `ip6tables -h' or 'ip6tables --help' for more > > > information. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -D libvirt-out -m > > > physdev --physdev-out vnet0 -g FO-vnet0' failed: ip6tables v1.4.21: > > > goto 'FO-vnet0' is not a chain#012#012Try `ip6tables -h' or > > > 'ip6tables --help' for more information. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 > > > -w -D libvirt-in -m physdev --physdev-in vnet0 -g FI-vnet0' failed: > > > ip6tables v1.4.21: goto 'FI-vnet0' is not a chain#012#012Try > > > `ip6tables -h' or 'ip6tables --help' for more information. Jan 21 > > > 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ip6tables -w2 -w -D libvirt-host-in -m physdev > > > --physdev-in vnet0 -g HI-vnet0' failed: ip6tables v1.4.21: goto > > > 'HI-vnet0' is not a chain#012#012Try `ip6tables -h' or 'ip6tables > > > --help' for more information. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 > > > -w -D libvirt-in-post -m physdev --physdev-in vnet0 -j ACCEPT' > > > failed: ip6tables: Bad rule (does a matching rule exist in that > > > chain?). Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -F FO-vnet0' failed: > > > ip6tables: No chain/target/match by that name. Jan 21 14:10:07 > > > HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ip6tables -w2 -w -X FO-vnet0' failed: ip6tables: No > > > chain/target/match by that name. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 > > > -w -F FI-vnet0' failed: ip6tables: No chain/target/match by that > > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -X FI-vnet0' failed: > > > ip6tables: No chain/target/match by that name. Jan 21 14:10:07 > > > HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ip6tables -w2 -w -F HI-vnet0' failed: ip6tables: No > > > chain/target/match by that name. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 > > > -w -X HI-vnet0' failed: ip6tables: No chain/target/match by that > > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/ebtables --concurrent -t nat -D > > > POSTROUTING -o vnet0 -j libvirt-O-vnet0' failed: Illegal target > > > name 'libvirt-O-vnet0'. Jan 21 14:10:07 HCI01 firewalld[24040]: > > > WARNING: COMMAND_FAILED: '/usr/sbin/ebtables --concurrent -t nat -L > > > libvirt-O-vnet0' failed: Chain 'libvirt-O-vnet0' doesn't exist. Jan > > > 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ebtables --concurrent -t nat -F libvirt-O-vnet0' failed: > > > Chain 'libvirt-O-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables > > > --concurrent -t nat -X libvirt-O-vnet0' failed: Chain > > > 'libvirt-O-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 vdsm[3650]: > > > WARN > > > File: > /var/lib/libvirt/qemu/channels/ea1b312c-a462-45a9-ab75-78008bc4c9c9.ovirt-guest-agent.0 > > > already removed Jan 21 14:10:07 HCI01 vdsm[3650]: WARN Attempting > > > to remove a non existing network: > > > ovirtmgmt/ea1b312c-a462-45a9-ab75-78008bc4c9c9 Jan 21 14:10:07 > > > HCI01 vdsm[3650]: WARN Attempting to remove a non existing net > > > user: ovirtmgmt/ea1b312c-a462-45a9-ab75-78008bc4c9c9 Jan 21 > > > 14:10:07 HCI01 vdsm[3650]: WARN > > > File: > /var/lib/libvirt/qemu/channels/ea1b312c-a462-45a9-ab75-78008bc4c9c9.org.qemu.guest_agent.0 > > > already removed > > > > > > any ideas on that? > > > _______________________________________________ > > > Users mailing list -- users(a)ovirt.org > > > To unsubscribe send an email to users-leave(a)ovirt.org > > > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > > > oVirt Code of Conduct: > > > https://www.ovirt.org/community/about/community-guidelines/ List > > > Archives: > > > > https://lists.ovirt.org/archives/list/users@ovirt.org/message/XMMX5CY6VHFWW… > > > >

2 1

lvm problem
by Nyika Csaba 24 Jan '19

24 Jan '19

Hi all, I have an Ovirt 4.2.8 cluster. Nodes are 4.2 ovirt nodes and the volumes (5) attached to nodes by FC. 2 weeks ago i made a small vm (centos 7 based) for me to test (name A). After the test i dropped a vm. Next day a made an another vm (named B) to the developes and tired to add a new disk to the vm (B). Than a original volume group (vg) of the vm (B) missed and i got back the yesterday dropped vm`s (A) vg! I tired to restart a vm, but the vm never started again. I dropped this vm (B) too, and tired to add a new disk an older running vm (C) too, but a volume group changed to that vm`s vg what i dropped before (B). I checked this „error” and i got it ,then i delete or move disks from the end of the FC volume. Have sombody ever seen error like this? Thanks, csaba Ps: in this cluster a managed 120 productive vm, so….

1 0

Lvm problem
by csabany＠freemail.hu 24 Jan '19

24 Jan '19

Hi all, I have an Ovirt 4.2.8 cluster. Nodes are 4.2 ovirt nodes and the volumes (5) attached to nodes by FC. 2 weeks ago i made a small vm (centos 7 based) for me to test (name A). After the test i dropped a vm. Next day a made an another vm (named B) to the developes and tired to add a new disk to the vm (B). Than a original volume group (vg) of the vm (B) missed and i got back the yesterday dropped vm`s (A) vg! I tired to restart a vm, but the vm never started again. I dropped this vm (B) too, and tired to add a new disk an older running vm (C) too, but a volume group changed to that vm`s vg what i dropped before (B). I checked this „error” and i got it ,then i delete or move disks from the end of the FC volume. Have sombody ever seen error like this? Thanks, csaba Ps: in this cluster a managed 120 productive vm, so….

1 0

latest pycurl 7.43 brokes ovirtsdk4
by Nathanaël Blanchet 24 Jan '19

24 Jan '19

Hi all, If anyone uses latest pycurl 7.43 provided by pip or ansible tower/awx, any ovirtsdk4 calling will issue with the log: The full traceback is: WARNING: The below traceback may *not* be related to the actual failure. File "/tmp/ansible_ovirt_auth_payload_L1HK9E/__main__.py", line 202, in <module> import ovirtsdk4 as sdk File "/opt/awx/embedded/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 22, in <module> import pycurl fatal: [localhost]: FAILED! => { "changed": false, "invocation": { "module_args": { "ca_file": null, "compress": true, "headers": null, "hostname": null, "insecure": true, "kerberos": false, "ovirt_auth": null, "password": "VALUE_SPECIFIED_IN_NO_LOG_PARAMETER", "state": "present", "timeout": 0, "token": null, "url": "https://acore.v100.abes.fr/ovirt-engine/api", "username": "admin@internal" } }, "msg": "ovirtsdk4 version 4.2.4 or higher is required for this module" } The only way is to set the version of pycurl with pip install -U "pycurl == 7.19.0" (Before this, in tower/awx, you should create venv) -- 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

2 4

oVirt 4.2.8 CPU Compatibility
by Stefano Danzi 24 Jan '19

24 Jan '19

Hello! I'm running oVirt 4.2.7.5-1.el7 on 3 hosts cluster. Cluster CPU Type is "AMD Opteron G3". On default cluster I can see the warning: "Warning: The CPU type 'AMD Opteron G3' will not be supported in the next minor version update'" Is it still supported in version 4.2.8? I can't see references in documentation or changelog.

5 5

ovirt 4.2 HCI rollout
by Markus Schaufler 23 Jan '19

23 Jan '19

Hi, I'm trying a (nested) ovirt 4.2.7 HCI rollout on 3 centos VM's by following https://ovirt.org/documentation/gluster-hyperconverged/chap-Deploying_Hyper… gluster deployment was successful but at HE deployment "stage 5" I got following error: [ INFO ] TASK [Reconfigure OVN central address] [ ERROR ] fatal: [localhost]: FAILED! => {"msg": "The task includes an option with an undefined variable. The error was: 'dict object' has no attribute 'stdout_lines'\n\nThe error appears to have been in '/usr/share/ovirt-hosted-engine-setup/ansible/create_target_vm.yml': line 522, column 5, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n # https://github.com/oVirt/ovirt-engine/blob/master/packaging/playbooks/roles… - name: Reconfigure OVN central address\n ^ here\n"} /var/log/messages: Jan 21 14:09:56 HCI01 journal: ovirt-ha-agent ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine ERROR Engine VM stopped on localhost Jan 21 14:10:01 HCI01 systemd: Started Session 22 of user root. Jan 21 14:10:02 HCI01 systemd: Started Session c306 of user root. Jan 21 14:10:03 HCI01 systemd: Started Session c307 of user root. Jan 21 14:10:06 HCI01 vdsm[3650]: WARN executor state: count=5 workers=set([<Worker name=periodic/4 waiting task#=141 at 0x7fd2d4316910>, <Worker name=periodic/1 running <Task discardable <Operation action=<vdsm.virt.sampling.VMBulkstatsMonitor object at 0x7fd2d4679490> at 0x7fd2d4679710> timeout=7.5, duration=7 at 0x7fd33c1e0ed0> disca rded task#=413 at 0x7fd2d5ed0510>, <Worker name=periodic/3 waiting task#=414 at 0x7fd2d5ed0b10>, <Worker name=periodic/5 waiting task#=0 at 0x7fd2d425f650>, <Worker name =periodic/2 waiting task#=412 at 0x7fd2d5ed07d0>]) Jan 21 14:10:06 HCI01 kernel: ovirtmgmt: port 2(vnet0) entered disabled state Jan 21 14:10:06 HCI01 kernel: device vnet0 left promiscuous mode Jan 21 14:10:06 HCI01 kernel: ovirtmgmt: port 2(vnet0) entered disabled state Jan 21 14:10:06 HCI01 NetworkManager[3666]: <info> [1548076206.9177] device (vnet0): state change: disconnected -> unmanaged (reason 'unmanaged', sys-iface-state: 'remo ved') Jan 21 14:10:06 HCI01 NetworkManager[3666]: <info> [1548076206.9180] device (vnet0): released from master device ovirtmgmt Jan 21 14:10:06 HCI01 lldpad: recvfrom(Event interface): No buffer space available Jan 21 14:10:06 HCI01 libvirtd: 2019-01-21 13:10:06.925+0000: 2651: error : qemuMonitorIORead:609 : Unable to read from monitor: Connection reset by peer Jan 21 14:10:07 HCI01 kvm: 0 guests now active Jan 21 14:10:07 HCI01 systemd-machined: Machine qemu-3-HostedEngine terminated. Jan 21 14:10:07 HCI01 libvirtd: 2019-01-21 13:10:07.125+0000: 2704: warning : qemuGetProcessInfo:1406 : cannot parse process status data Jan 21 14:10:07 HCI01 libvirtd: 2019-01-21 13:10:07.125+0000: 2704: warning : qemuGetProcessInfo:1406 : cannot parse process status data Jan 21 14:10:07 HCI01 libvirtd: 2019-01-21 13:10:07.125+0000: 2704: warning : qemuGetProcessInfo:1406 : cannot parse process status data Jan 21 14:10:07 HCI01 libvirtd: 2019-01-21 13:10:07.125+0000: 2704: warning : qemuGetProcessInfo:1406 : cannot parse process status data Jan 21 14:10:07 HCI01 libvirtd: 2019-01-21 13:10:07.126+0000: 2704: error : virNetDevTapInterfaceStats:764 : internal error: /proc/net/dev: Interface not found Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -D libvirt-out -m physdev --physdev-is-bridged --physdev-out vnet0 -g FP-vnet 0' failed: iptables v1.4.21: goto 'FP-vnet0' is not a chain#012#012Try `iptables -h' or 'iptables --help' for more information. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -D libvirt-out -m physdev --physdev-out vnet0 -g FP-vnet0' failed: iptables v 1.4.21: goto 'FP-vnet0' is not a chain#012#012Try `iptables -h' or 'iptables --help' for more information. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -D libvirt-in -m physdev --physdev-in vnet0 -g FJ-vnet0' failed: iptables v1. 4.21: goto 'FJ-vnet0' is not a chain#012#012Try `iptables -h' or 'iptables --help' for more information. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -D libvirt-host-in -m physdev --physdev-in vnet0 -g HJ-vnet0' failed: iptable s v1.4.21: goto 'HJ-vnet0' is not a chain#012#012Try `iptables -h' or 'iptables --help' for more information. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -F FP-vnet0' failed: iptables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -X FP-vnet0' failed: iptables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -F FJ-vnet0' failed: iptables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -X FJ-vnet0' failed: iptables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -F HJ-vnet0' failed: iptables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -X HJ-vnet0' failed: iptables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -D libvirt-out -m physdev --physdev-is-bridged --physdev-out vnet0 -g FP-vne t0' failed: ip6tables v1.4.21: goto 'FP-vnet0' is not a chain#012#012Try `ip6tables -h' or 'ip6tables --help' for more information. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -D libvirt-out -m physdev --physdev-out vnet0 -g FP-vnet0' failed: ip6tables v1.4.21: goto 'FP-vnet0' is not a chain#012#012Try `ip6tables -h' or 'ip6tables --help' for more information. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -D libvirt-in -m physdev --physdev-in vnet0 -g FJ-vnet0' failed: ip6tables v 1.4.21: goto 'FJ-vnet0' is not a chain#012#012Try `ip6tables -h' or 'ip6tables --help' for more information. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -D libvirt-host-in -m physdev --physdev-in vnet0 -g HJ-vnet0' failed: ip6tab les v1.4.21: goto 'HJ-vnet0' is not a chain#012#012Try `ip6tables -h' or 'ip6tables --help' for more information. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -F FP-vnet0' failed: ip6tables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -X FP-vnet0' failed: ip6tables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -F FJ-vnet0' failed: ip6tables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -X FJ-vnet0' failed: ip6tables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -F HJ-vnet0' failed: ip6tables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -X HJ-vnet0' failed: ip6tables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables --concurrent -t nat -D PREROUTING -i vnet0 -j libvirt-J-vnet0' failed: Illegal target name 'libvirt-J-vnet0'. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables --concurrent -t nat -D POSTROUTING -o vnet0 -j libvirt-P-vnet0' failed: Illegal target name 'libvirt-P-vnet0'. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables --concurrent -t nat -D PREROUTING -i vnet0 -j libvirt-J-vnet0' failed: Illegal targe t name 'libvirt-J-vnet0'. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables --concurrent -t nat -D POSTROUTING -o vnet0 -j libvirt-P-vnet0' failed: Illegal targ et name 'libvirt-P-vnet0'. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables --concurrent -t nat -L libvirt-J-vnet0' failed: Chain 'libvirt-J-vnet0' doesn't exis t. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables --concurrent -t nat -L libvirt-P-vnet0' failed: Chain 'libvirt-P-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables --concurrent -t nat -F libvirt-J-vnet0' failed: Chain 'libvirt-J-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables --concurrent -t nat -X libvirt-J-vnet0' failed: Chain 'libvirt-J-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables --concurrent -t nat -F libvirt-P-vnet0' failed: Chain 'libvirt-P-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables --concurrent -t nat -X libvirt-P-vnet0' failed: Chain 'libvirt-P-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -D libvirt-out -m physdev --physdev-is-bridged --physdev-out vnet0 -g FO-vnet0' failed: iptables v1.4.21: goto 'FO-vnet0' is not a chain#012#012Try `iptables -h' or 'iptables --help' for more information. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -D libvirt-out -m physdev --physdev-out vnet0 -g FO-vnet0' failed: iptables v1.4.21: goto 'FO-vnet0' is not a chain#012#012Try `iptables -h' or 'iptables --help' for more information. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -D libvirt-in -m physdev --physdev-in vnet0 -g FI-vnet0' failed: iptables v1.4.21: goto 'FI-vnet0' is not a chain#012#012Try `iptables -h' or 'iptables --help' for more information. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -D libvirt-host-in -m physdev --physdev-in vnet0 -g HI-vnet0' failed: iptables v1.4.21: goto 'HI-vnet0' is not a chain#012#012Try `iptables -h' or 'iptables --help' for more information. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -D libvirt-in-post -m physdev --physdev-in vnet0 -j ACCEPT' failed: iptables: Bad rule (does a matching rule exist in that chain?). Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -F FO-vnet0' failed: iptables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -X FO-vnet0' failed: iptables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -F FI-vnet0' failed: iptables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -X FI-vnet0' failed: iptables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -F HI-vnet0' failed: iptables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -X HI-vnet0' failed: iptables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -D libvirt-out -m physdev --physdev-is-bridged --physdev-out vnet0 -g FO-vnet0' failed: ip6tables v1.4.21: goto 'FO-vnet0' is not a chain#012#012Try `ip6tables -h' or 'ip6tables --help' for more information. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -D libvirt-out -m physdev --physdev-out vnet0 -g FO-vnet0' failed: ip6tables v1.4.21: goto 'FO-vnet0' is not a chain#012#012Try `ip6tables -h' or 'ip6tables --help' for more information. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -D libvirt-in -m physdev --physdev-in vnet0 -g FI-vnet0' failed: ip6tables v1.4.21: goto 'FI-vnet0' is not a chain#012#012Try `ip6tables -h' or 'ip6tables --help' for more information. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -D libvirt-host-in -m physdev --physdev-in vnet0 -g HI-vnet0' failed: ip6tables v1.4.21: goto 'HI-vnet0' is not a chain#012#012Try `ip6tables -h' or 'ip6tables --help' for more information. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -D libvirt-in-post -m physdev --physdev-in vnet0 -j ACCEPT' failed: ip6tables: Bad rule (does a matching rule exist in that chain?). Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -F FO-vnet0' failed: ip6tables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -X FO-vnet0' failed: ip6tables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -F FI-vnet0' failed: ip6tables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -X FI-vnet0' failed: ip6tables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -F HI-vnet0' failed: ip6tables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -X HI-vnet0' failed: ip6tables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables --concurrent -t nat -D POSTROUTING -o vnet0 -j libvirt-O-vnet0' failed: Illegal target name 'libvirt-O-vnet0'. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables --concurrent -t nat -L libvirt-O-vnet0' failed: Chain 'libvirt-O-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables --concurrent -t nat -F libvirt-O-vnet0' failed: Chain 'libvirt-O-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables --concurrent -t nat -X libvirt-O-vnet0' failed: Chain 'libvirt-O-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 vdsm[3650]: WARN File: /var/lib/libvirt/qemu/channels/ea1b312c-a462-45a9-ab75-78008bc4c9c9.ovirt-guest-agent.0 already removed Jan 21 14:10:07 HCI01 vdsm[3650]: WARN Attempting to remove a non existing network: ovirtmgmt/ea1b312c-a462-45a9-ab75-78008bc4c9c9 Jan 21 14:10:07 HCI01 vdsm[3650]: WARN Attempting to remove a non existing net user: ovirtmgmt/ea1b312c-a462-45a9-ab75-78008bc4c9c9 Jan 21 14:10:07 HCI01 vdsm[3650]: WARN File: /var/lib/libvirt/qemu/channels/ea1b312c-a462-45a9-ab75-78008bc4c9c9.org.qemu.guest_agent.0 already removed any ideas on that?

2 2

Q: Is it safe to execute on node "saslpasswd2 -a libvirt username" ?
by Andrei Verovski 23 Jan '19

23 Jan '19

Hi ! Is it safe to execute on oVirt node this command ? saslpasswd2 -a libvirt username Its a production environment, screwing up anything is not an option. I have no idea how VDSM interacts with libvirt, so not sure about this. Thanks in advance Andrei

2 1

Host non-responsive after yum update CentOS7/Ovirt3.6
by jaherring＠usa.net 23 Jan '19

23 Jan '19

Hi, I working on a CentOS7 based Ovirt 3.6 system (ovirt-engine/db on one machine, two separate ovirt vm hosts) which has been running fine but mostly ignored for 2-3 of years. Recently it was decided to update the OS as it was far behind on security updates, so one host was put into maintenance mode, yum update'd, rebooted, and then it was attempted to take out of maintenance mode but it's "non-responsive" now. If I look in /var/log/ovirt-engine/engine.log on the engine machine I see for this host (vmserver2): "ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand] (DefaultQuartzScheduler_Worker-36) [2bc0978d] Command 'GetCapabilitiesVDSCommand(HostName = vmserver2, VdsIdAndVdsVDSCommandParametersBase:{runAsync='true', hostId='6725086f-42c0-40eb-91f1-0f2411ea9432', vds='Host[vmserver2,6725086f-42c0-40eb-91f1-0f2411ea9432]'})' execution failed: org.ovirt.vdsm.jsonrpc.client.ClientConnectionException: Connection failed" and thereafter more errors. This keep repeating in the log. In the Ovirt GUI I see multiple occurrences of log entries for the problem host: "vmserver2...command failed: Vds timeout occurred" "vmserver2...command failed: Heartbeat exceeded" "vmserver2...command failed: internal error: Unknown CPU model Broadwell-noTSX-IBRS" Firewall rules look identical to the host which is working normally but has not been updated. Any thoughts about how to fix or further troubleshoot this?

6 7

Re: Cannot Increase Hosted Engine VM Memory
by Douglas Duckworth 23 Jan '19

23 Jan '19

Hi Simone Can I get help with this issue? Still cannot increase memory for Hosted Engine. Thanks, Douglas Duckworth, MSc, LFCS HPC System Administrator Scientific Computing Unit<https://scu.med.cornell.edu> Weill Cornell Medicine 1300 York Avenue New York, NY 10065 E: doug(a)med.cornell.edu<mailto:doug@med.cornell.edu> O: 212-746-6305 F: 212-746-8690 On Thu, Jan 17, 2019 at 8:08 AM Douglas Duckworth <dod2014(a)med.cornell.edu<mailto:dod2014@med.cornell.edu>> wrote: Sure, they're attached. In "first attempt" the error seems to be: 2019-01-17 07:49:24,795-05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-29) [680f82b3-7612-4d91-afdc-43937aa298a2] EVENT_ID: FAILED_HOT_SET_MEMORY_NOT_DIVIDABLE(2,048), Failed to hot plug memory to VM HostedEngine. Amount of added memory (4000MiB) is not dividable by 256MiB. Followed by: 2019-01-17 07:49:24,814-05 WARN [org.ovirt.engine.core.bll.UpdateRngDeviceCommand] (default task-29) [26f5f3ed] Validation of action 'UpdateRngDevice' failed for user admin@internal-authz. Reasons: ACTION_TYPE_FAILED_VM_IS_RUNNING 2019-01-17 07:49:24,815-05 ERROR [org.ovirt.engine.core.bll.UpdateVmCommand] (default task-29) [26f5f3ed] Updating RNG device of VM HostedEngine (adf14389-1563-4b1a-9af6-4b40370a825b) failed. Old RNG device = VmRngDevice:{id='VmDeviceId:{deviceId='6435b2b5-163c-4f0c-934e-7994da60dc89', vmId='adf14389-1563-4b1a-9af6-4b40370a825b'}', device='virtio', type='RNG', specParams='[source=urandom]', address='', managed='true', plugged='true', readOnly='false', deviceAlias='', customProperties='null', snapshotId='null', logicalName='null', hostDevice='null'}. New RNG device = VmRngDevice:{id='VmDeviceId:{deviceId='6435b2b5-163c-4f0c-934e-7994da60dc89', vmId='adf14389-1563-4b1a-9af6-4b40370a825b'}', device='virtio', type='RNG', specParams='[source=urandom]', address='', managed='true', plugged='true', readOnly='false', deviceAlias='', customProperties='null', snapshotId='null', logicalName='null', hostDevice='null'}. In "second attempt" I used values that are dividable by 256 MiB so that's no longer present. Though same error: 2019-01-17 07:56:59,795-05 INFO [org.ovirt.engine.core.vdsbroker.SetAmountOfMemoryVDSCommand] (default task-22) [7059a48f] START, SetAmountOfMemoryVDSCommand(HostName = ovirt-hv1.med.cornell.edu<http://ovirt-hv1.med.cornell.edu>, Params:{hostId='cdd5ffda-95c7-4ffa-ae40-be66f1d15c30', vmId='adf14389-1563-4b1a-9af6-4b40370a825b', memoryDevice='VmDevice:{id='VmDeviceId:{deviceId='7f7d97cc-c273-4033-af53-bc9033ea3abe', vmId='adf14389-1563-4b1a-9af6-4b40370a825b'}', device='memory', type='MEMORY', specParams='[node=0, size=2048]', address='', managed='true', plugged='true', readOnly='false', deviceAlias='', customProperties='null', snapshotId='null', logicalName='null', hostDevice='null'}', minAllocatedMem='6144'}), log id: 50873daa 2019-01-17 07:56:59,855-05 INFO [org.ovirt.engine.core.vdsbroker.SetAmountOfMemoryVDSCommand] (default task-22) [7059a48f] FINISH, SetAmountOfMemoryVDSCommand, log id: 50873daa 2019-01-17 07:56:59,862-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-22) [7059a48f] EVENT_ID: HOT_SET_MEMORY(2,039), Hotset memory: changed the amount of memory on VM HostedEngine from 4096 to 4096 2019-01-17 07:56:59,881-05 WARN [org.ovirt.engine.core.bll.UpdateRngDeviceCommand] (default task-22) [28fd4c82] Validation of action 'UpdateRngDevice' failed for user admin@internal-authz. Reasons: ACTION_TYPE_FAILED_VM_IS_RUNNING 2019-01-17 07:56:59,882-05 ERROR [org.ovirt.engine.core.bll.UpdateVmCommand] (default task-22) [28fd4c82] Updating RNG device of VM HostedEngine (adf14389-1563-4b1a-9af6-4b40370a825b) failed. Old RNG device = VmRngDevice:{id='VmDeviceId:{deviceId='6435b2b5-163c-4f0c-934e-7994da60dc89', vmId='adf14389-1563-4b1a-9af6-4b40370a825b'}', device='virtio', type='RNG', specParams='[source=urandom]', address='', managed='true', plugged='true', readOnly='false', deviceAlias='', customProperties='null', snapshotId='null', logicalName='null', hostDevice='null'}. New RNG device = VmRngDevice:{id='VmDeviceId:{deviceId='6435b2b5-163c-4f0c-934e-7994da60dc89', vmId='adf14389-1563-4b1a-9af6-4b40370a825b'}', device='virtio', type='RNG', specParams='[source=urandom]', address='', managed='true', plugged='true', readOnly='false', deviceAlias='', customProperties='null', snapshotId='null', logicalName='null', hostDevice='null'}. This message repeats throughout engine.log: 2019-01-17 07:55:43,270-05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-89) [] EVENT_ID: VM_MEMORY_UNDER_GUARANTEED_VALUE(148), VM HostedEngine on host ovirt-hv1.med.cornell.edu<http://ovirt-hv1.med.cornell.edu> was guaranteed 8192 MB but currently has 4224 MB As you can see attached the host has plenty of memory. Thank you Simone! Thanks, Douglas Duckworth, MSc, LFCS HPC System Administrator Scientific Computing Unit<https://scu.med.cornell.edu> Weill Cornell Medicine 1300 York Avenue New York, NY 10065 E: doug(a)med.cornell.edu<mailto:doug@med.cornell.edu> O: 212-746-6305 F: 212-746-8690 On Thu, Jan 17, 2019 at 5:09 AM Simone Tiraboschi <stirabos(a)redhat.com<mailto:stirabos@redhat.com>> wrote: On Wed, Jan 16, 2019 at 8:22 PM Douglas Duckworth <dod2014(a)med.cornell.edu<mailto:dod2014@med.cornell.edu>> wrote: Sorry for accidental send. Anyway I try to increase physical memory however it won't go above 4096MB. The hypervisor has 64GB. Do I need to modify this value with Hosted Engine offline? No, it's not required. Can you please attach your engine.log for the relevant time frame? Thanks, Douglas Duckworth, MSc, LFCS HPC System Administrator Scientific Computing Unit<https://scu.med.cornell.edu> Weill Cornell Medicine 1300 York Avenue New York, NY 10065 E: doug(a)med.cornell.edu<mailto:doug@med.cornell.edu> O: 212-746-6305 F: 212-746-8690 On Wed, Jan 16, 2019 at 1:58 PM Douglas Duckworth <dod2014(a)med.cornell.edu<mailto:dod2014@med.cornell.edu>> wrote: Hello I am trying to increase Hosted Engine physical memory above 4GB Thanks, Douglas Duckworth, MSc, LFCS HPC System Administrator Scientific Computing Unit<https://scu.med.cornell.edu> Weill Cornell Medicine 1300 York Avenue New York, NY 10065 E: doug(a)med.cornell.edu<mailto:doug@med.cornell.edu> O: 212-746-6305 F: 212-746-8690 _______________________________________________ Users mailing list -- users(a)ovirt.org<mailto:users@ovirt.org> To unsubscribe send an email to users-leave(a)ovirt.org<mailto:users-leave@ovirt.org> Privacy Statement: https://www.ovirt.org/site/privacy-policy/<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ovirt.org_site_pri…> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ovirt.org_communit…> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/WGSXQVVPJJ2CR…<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.ovirt.org_archiv…>

2 1

Re: Hosted Engine VM and Storage not showing up
by Simone Tiraboschi 23 Jan '19

23 Jan '19

On Mon, Jan 7, 2019 at 2:03 PM Vinícius Ferrão <ferrao(a)versatushpc.com.br> wrote: > Hello Simone, > > Sent from my iPhone > > On 7 Jan 2019, at 07:11, Simone Tiraboschi <stirabos(a)redhat.com> wrote: > > > > On Sun, Jan 6, 2019 at 5:31 PM <ferrao(a)versatushpc.com.br> wrote: > >> Hello, >> >> I’ve a new oVirt installation using oVirt 4.2.7.1 Node and after >> deploying the hosted engine it does not show up on the interface even after >> adding the first storage. >> >> The Datacenter is up but the engine VM and the engine storage does not >> appear. >> >> I have the following message repeated constantly on /var/log/messages: >> >> Jan 4 20:17:30 ovirt1 journal: ovirt-ha-agent >> ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm ERROR >> Unable to identify the OVF_STORE volume, falling back to initial vm.conf. >> Please ensure you already added your first data domain for regular VMs >> >> What’s wrong? Am I doing something different? >> > > The import of external VM is broken in 4.2.7 as for > https://bugzilla.redhat.com/show_bug.cgi?id=1649615 > It will be fixed with 4.2.8. > > In the mean time I strongly suggest to use the regular flow for > hosted-engine deployment (simply skip --noansible option) since only the > vintage deprecated flow is affected by this issue. > > > > Thanks for pointing the issue. I was unable the find this on bugzilla by > myself. The title isn’t helping either. > > But on other hand, I only used the legacy mode because ansible mode fails. > Can you please attach a log of the issue? > > I’m not sure why it fails. I can try it again, but I can ask in advance: > the management network is bonded, is this an issue? I think I’ve read > something about this on this list but I’m unsure. > No, but you should set bond mode 1, 2, 3, or 4. Teaming is not supported. > > Thanks, > > >> >> Additional infos: >> >> [root@ovirt1 ~]# vdsm-tool list-nets >> ovirtmgmt (default route) >> storage >> >> [root@ovirt1 ~]# ip a | grep "inet " >> inet 127.0.0.1/8 scope host lo >> inet 10.20.0.101/24 brd 10.20.0.255 scope global dynamic ovirtmgmt >> inet 192.168.10.1/29 brd 192.168.10.7 scope global storage >> >> [root@ovirt1 ~]# mount | grep -i nfs >> sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime) >> 10.20.0.200:/mnt/pool0/ovirt/he on /rhev/data-center/mnt/10.20.0.200:_mnt_pool0_ovirt_he >> type nfs4 >> (rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,soft,nosharecache,proto=tcp,timeo=600,retrans=6,sec=sys,clientaddr=10.20.0.101,local_lock=none,addr=10.20.0.200) >> >> [root@ovirt1 ~]# hosted-engine --check-deployed >> Returns nothing! >> >> [root@ovirt1 ~]# hosted-engine --check-liveliness >> Hosted Engine is up! >> >> [root@ovirt1 ~]# hosted-engine --vm-status >> >> --== Host 1 status ==-- >> >> conf_on_shared_storage : True >> Status up-to-date : True >> Hostname : ovirt1.local.versatushpc.com.br >> Host ID : 1 >> Engine status : {"health": "good", "vm": "up", >> "detail": "Up"} >> Score : 3400 >> stopped : False >> Local maintenance : False >> crc32 : 1736a87d >> local_conf_timestamp : 7836 >> Host timestamp : 7836 >> Extra metadata (valid at timestamp): >> metadata_parse_version=1 >> metadata_feature_version=1 >> timestamp=7836 (Fri Jan 4 20:18:10 2019) >> host-id=1 >> score=3400 >> vm_conf_refresh_time=7836 (Fri Jan 4 20:18:10 2019) >> conf_on_shared_storage=True >> maintenance=False >> state=EngineUp >> stopped=False >> >> >> Thanks in advance, >> >> PS: Log files are available here: >> http://www.if.ufrj.br/~ferrao/ovirt/issues/he-not-showing/ >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org >> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >> oVirt Code of Conduct: >> https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: >> https://lists.ovirt.org/archives/list/users@ovirt.org/message/IQHM6YQ7HVBHL… >> > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/BPJAV4AVRN55Y… > >

2 9

Migrating Hosted Engine environment from untagged to LACP bonded interfaces with tagged ovirtmgmt network
by Bernhard Dick 23 Jan '19

23 Jan '19

Hi, I have an oVirt 4.2 environment running with the engine in hosted engine state. We are now going to change our whole setup migrating to redundancy on switch side and using a different VLAN for the ovirt management traffic. Currently all host and management-traffic is running untagged on one network interface on all of our hosts and we want to change this to be VLAN-tagged inside LACP-Bonds (each bond containing two network interfaces) on all hosts. While changing the configuration for the VM networks should be straight forward as I can shutdown all VMs during the migration I'm asking how to handle this for the hosted engine VM and configuration. Is there any information how to do such a change? Regards Bernhard

1 0

Adding host with local-storage VMs configured
by Callum Smith 23 Jan '19

23 Jan '19

Dear All, We’re in a world where we had to recover from outage by installing a clean hosted engine and importing VMs from storage. We do, however, have a host that is configured for local-storage and has a VM running on it. What is the best way to re-introduce this host to a new hosted-engine with minimal outage of the VM on that host. Regards, Callum -- Callum Smith Research Computing Core Wellcome Trust Centre for Human Genetics University of Oxford e. callum(a)well.ox.ac.uk<mailto:callum@well.ox.ac.uk>

1 0

Q: "virsh list" on oVirt node
by Andrei Verovski 23 Jan '19

23 Jan '19

Hi ! “virsh” can’t be executed on oVirt node directly due to authentication problem. Only "virsh —readonly” are working. Someone have recommended adding new password with this: saslpasswd2 -a libvirt username I know this is somewhat depreciated to hacking directly into oVirt node yet I’m still need this. What is correct, non-destructive to accomplish this? Thanks in advance. Andrei

1 0

Re: The built in group Everyone is troublesome.
by Jacob Green 22 Jan '19

22 Jan '19

Thank you for your help! This worked flawlessly and helped me understand the engine database a little more! On 12/04/2018 12:00 PM, Staniforth, Paul wrote: > > Get the id for the everyone group > https://engine.example.com/ovirt-engine/api/groups?search=everyone > > Get the id for the UserRole > https://engine.example.com/ovirt-engine/api/roles > > connect to the engine database > > e.g. > > psql -h localhost -U engine -d engine > > select * from permissions where ad_element_id='groupid'; > > note the id of the permission, probably the last one but you can check > by the role_id > then delete the permission. > > delete from permissions where id='noted before'; > > you should make a backup of your system before you do this. > > > Regards, > > Paul S. > > ------------------------------------------------------------------------ > *From:* Staniforth, Paul > *Sent:* 04 December 2018 17:23 > *To:* Jacob Green > *Subject:* Re: [ovirt-users] The built in group Everyone is troublesome. > > Yes, that's not good you need to remove the UserRole system permission > but they fixed it so you can't. > > https://bugzilla.redhat.com/show_bug.cgi?id=1366205 > > > I think there maybe a bug that allows you to add system permissions to > the everyone group in 4.2, you're only supposed to be able to change > the permissions with a dbscript. > > > I'll look up my notes on how to remove the permission from the DB. > > > Regards, > > Paul S. > > > ------------------------------------------------------------------------ > *From:* Jacob Green <jgreen(a)aasteel.com> > *Sent:* 04 December 2018 16:59 > *To:* Staniforth, Paul > *Subject:* Re: [ovirt-users] The built in group Everyone is troublesome. > > > If the picture does not come through. The following are the permisstions > > Group > Everyone > > Everyone > Role - UserRole,UserProfileEditor Object : (System) > > > On 12/04/2018 10:20 AM, Staniforth, Paul wrote: >> What are the permissions for the group everyone, in particular the system permission should be just UserProfileEditor. >> >> Regards, >> Paul S. >> ________________________________________ >> From: Jacob Green<jgreen(a)aasteel.com> >> Sent: 04 December 2018 15:20 >> To: users >> Subject: [ovirt-users] The built in group Everyone is troublesome. >> >> So all my VMs are inheriting system permissions from group >> everyone and giving all my users access to all my VMs, in ovirt 4.2. Is >> there a best practices guide or any recommendation on how to clear this >> up? Clicking remove on everyone does not work because Ovirt won't allow >> me to remove a built in account. >> >> >> Thank you >> >> -- >> Jacob Green >> >> Systems Admin >> >> American Alloy Steel >> >> 713-300-5690 >> _______________________________________________ >> Users mailing list --users(a)ovirt.org >> To unsubscribe send an email tousers-leave(a)ovirt.org >> Privacy Statement:https://www.ovirt.org/site/privacy-policy/ >> oVirt Code of Conduct:https://www.ovirt.org/community/about/community-guidelines/ >> List Archives:https://lists.ovirt.org/archives/list/users@ovirt.org/message/A5MW… >> To view the terms under which this email is distributed, please go to:- >> http://leedsbeckett.ac.uk/disclaimer/email/ > > -- > Jacob Green > > Systems Admin > > American Alloy Steel > > 713-300-5690 > To view the terms under which this email is distributed, please go to:- > http://leedsbeckett.ac.uk/disclaimer/email/ -- Jacob Green Systems Admin American Alloy Steel 713-300-5690

3 2

oVirt 4.2.7 export VM seems stuck at end of sparse disk
by Gianluca Cecchi 22 Jan '19

22 Jan '19

Hello, it happened two times, always with VMs composed by more than 1 disk. Now I have a VM with 9 disks and a total of about 370Gb: 1 x 90Gb 5 x 50Gb 3 x 10Gb I export vm to an export domain and it started 2 hours and 10 minutes ago at 15:46. At beginning the write rate on export domain was 120MB/s (in line with I/O capabilities of storage subsystem). It seems 5 disks completed ok, while 4 don't complete, even if it seems to be some reading activity: with command iotop -d 3 -k -o -P I get this on hypervisor where qemu-img convert command is executing Total DISK READ : 5712.75 K/s | Total DISK WRITE : 746.58 K/s Actual DISK READ: 6537.11 K/s | Actual DISK WRITE: 6.89 K/s PID PRIO USER DISK READ> DISK WRITE SWAPIN IO COMMAND 21238 idle vdsm 1344.18 K/s 183.12 K/s 0.00 % 0.15 % qemu-img convert -p -t non~1d23-4829-8350-f81fa16ea8b0 21454 idle vdsm 1344.18 K/s 183.12 K/s 0.00 % 0.06 % qemu-img convert -p -t non~443d-4563-8879-3dbd711b6936 21455 idle vdsm 1344.18 K/s 189.68 K/s 0.00 % 0.08 % qemu-img convert -p -t non~b67d-4acd-9bb5-485bc3ffdf2e 21548 idle vdsm 1344.18 K/s 190.67 K/s 0.00 % 0.06 % qemu-img convert -p -t non~7fc On export share [root@xfer ~]# ll -td /export/ovirt/a6a289ea-f160-4d35-b3aa-e59d171b4633/images/* drwxr-xr-x 2 36 36 4096 Jan 21 17:21 /export/ovirt/a6a289ea-f160-4d35-b3aa-e59d171b4633/images/ac33a8fe-f10e-4cbb-b121-2956f9925ade drwxr-xr-x 2 36 36 4096 Jan 21 17:06 /export/ovirt/a6a289ea-f160-4d35-b3aa-e59d171b4633/images/20c07082-d5ed-4804-867d-1f3f7c202b0e drwxr-xr-x 2 36 36 4096 Jan 21 17:02 /export/ovirt/a6a289ea-f160-4d35-b3aa-e59d171b4633/images/f8b1c6bc-de13-4416-9fe6-d7c26fb082b1 drwxr-xr-x 2 36 36 4096 Jan 21 17:02 /export/ovirt/a6a289ea-f160-4d35-b3aa-e59d171b4633/images/1b5313ef-0ee5-4f9a-b2a6-baa153ff0984 drwxr-xr-x 2 36 36 4096 Jan 21 17:02 /export/ovirt/a6a289ea-f160-4d35-b3aa-e59d171b4633/images/3f21c566-bc00-4dab-acbb-db9a3a1d76fa drwxr-xr-x 2 36 36 4096 Jan 21 15:47 /export/ovirt/a6a289ea-f160-4d35-b3aa-e59d171b4633/images/ed3a721e-fd1b-4fea-ad41-7ca56e94890e drwxr-xr-x 2 36 36 4096 Jan 21 15:46 /export/ovirt/a6a289ea-f160-4d35-b3aa-e59d171b4633/images/213f9ce9-6c34-4911-820e-4d1a96ba1791 drwxr-xr-x 2 36 36 4096 Jan 21 15:46 /export/ovirt/a6a289ea-f160-4d35-b3aa-e59d171b4633/images/28fef57c-4254-4469-9f3f-0d1f114d4f78 drwxr-xr-x 2 36 36 4096 Jan 21 15:46 /export/ovirt/a6a289ea-f160-4d35-b3aa-e59d171b4633/images/ea4fa5b1-a93a-4cb9-9552-e8ec67c5ff75 [root@xfer ~]# du -sh /export/ovirt/a6a289ea-f160-4d35-b3aa-e59d171b4633/images/* 11G /export/ovirt/a6a289ea-f160-4d35-b3aa-e59d171b4633/images/1b5313ef-0ee5-4f9a-b2a6-baa153ff0984 51G /export/ovirt/a6a289ea-f160-4d35-b3aa-e59d171b4633/images/20c07082-d5ed-4804-867d-1f3f7c202b0e 51G /export/ovirt/a6a289ea-f160-4d35-b3aa-e59d171b4633/images/213f9ce9-6c34-4911-820e-4d1a96ba1791 51G /export/ovirt/a6a289ea-f160-4d35-b3aa-e59d171b4633/images/28fef57c-4254-4469-9f3f-0d1f114d4f78 11G /export/ovirt/a6a289ea-f160-4d35-b3aa-e59d171b4633/images/3f21c566-bc00-4dab-acbb-db9a3a1d76fa 85G /export/ovirt/a6a289ea-f160-4d35-b3aa-e59d171b4633/images/ac33a8fe-f10e-4cbb-b121-2956f9925ade 51G /export/ovirt/a6a289ea-f160-4d35-b3aa-e59d171b4633/images/ea4fa5b1-a93a-4cb9-9552-e8ec67c5ff75 51G /export/ovirt/a6a289ea-f160-4d35-b3aa-e59d171b4633/images/ed3a721e-fd1b-4fea-ad41-7ca56e94890e 11G /export/ovirt/a6a289ea-f160-4d35-b3aa-e59d171b4633/images/f8b1c6bc-de13-4416-9fe6-d7c26fb082b1 [root@xfer ~]# It seems more than 30 minutes no more progress.... I see no errors in vdsm.log of hypervisor and in engine.log I keep this message every 10 seconds: 2019-01-21 18:08:19,060+01 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-10) [a1c0e39f-1924-4ae8-8b48-30bcce669278] Command 'ExportVm' (id: 'dc0a58bd-e8ca-42a9-8de0-dd3ccabe0512') waiting on child command id: '29d40db8-a0b9-4408-9e62-1abf3bccca65' type:'CopyImageGroup' to complete All the disks except the "apparently" not completed one (the 90Gb disk) are preallocated. Any other hint on what to check? Thanks, Gianluca

1 1

How to connect 2 hosts
by adamantini.peratikou＠ouc.ac.cy 22 Jan '19

22 Jan '19

I have the following configuraton: 1 cluster, 2 Hosts I would like to use a Vm-router under Host 1 to act as a dhcp server for both HOST1 and HOST2 VMs is it possible?

4 7

User Management
by Sakhi Hadebe 22 Jan '19

22 Jan '19

Hi, I need some pointers to documentation that will help me to configure users to have access and some rights (access to console, starting and shutting down own VMs) on their VMs on the VM portal. I have created a user using the ovirt-aaa-jdbc-tool utility, but I am unable to login to the cockpit portal. It gives an error: *The user shadebe@internal is not **authorized** to perform login* User details: [root@hostedengine ~]# ovirt-aaa-jdbc-tool query --what=user --pattern="name=s*" -- User shadebe(a35e8e14-d32b-4ff9-89e0-fd090a87146a) -- Namespace: * Name: shadebe ID: a35e8e14-d32b-4ff9-89e0-fd090a87146a Display Name: Email: sakhi(a)sanren.ac.za First Name: Sakhi Last Name: Hadebe Department: Title: Description: Account Disabled: false Account Locked: false Account Unlocked At: 1970-01-01 00:00:00Z Account Valid From: 2019-01-16 09:08:48Z Account Valid To: 2219-01-16 09:08:48Z Account Without Password: false Last successful Login At: 2019-01-16 09:32:52Z Last unsuccessful Login At: 2019-01-16 09:32:36Z Password Valid To: 2029-01-16 10:30:00Z Please help. -- Regards, Sakhi Hadebe Engineer: South African National Research Network (SANReN)Competency Area, Meraka, CSIR Tel: +27 12 841 2308 <+27128414213> Fax: +27 12 841 4223 <+27128414223> Cell: +27 71 331 9622 <+27823034657> Email: sakhi(a)sanren.ac.za <shadebe(a)csir.co.za>

2 2

[ANN] oVirt 4.2.8 is now generally available
by Sandro Bonazzola 22 Jan '19

22 Jan '19

The oVirt Project is pleased to announce the general availability of oVirt 4.2.8, as of January 22nd, 2019. This update is the eighth and last in a series of stabilization updates to the 4.2 series. Please note that no further updates will be issued for the 4.2 series. We encourage users to upgrade to 4.3 series when generally available to receive new features and updates. This release is available now for: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later * oVirt Node 4.2 See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is available - oVirt Node update is available, ISO will be available soon [2] - oVirt Tools Setup ISO is available[2] oVirt Node has been updated including: - oVirt 4.2.8: http://www.ovirt.org/release/4.2.8/ - Release for CentOS Linux 7 (1810) ( https://lists.centos.org/pipermail/centos-announce/2018-December/023082.html ) - Ansible 2.7.5: https://github.com/ansible/ansible/blob/stable-2.7/changelogs/CHANGELOG-v2.… Relevant CentOS Errata included: - CEBA-2019:0037 CentOS 7 tzdata BugFix Update ( https://lists.centos.org/pipermail/centos-announce/2019-January/023142.html ) - CESA-2019:0049 Important CentOS 7 systemd Security Update ( https://lists.centos.org/pipermail/centos-announce/2019-January/023143.html ) - CESA-2018:3651 Moderate CentOS 7 kernel Security Update ( https://lists.centos.org/pipermail/centos-announce/2018-December/023132.html ) - CEBA-2018:3338 CentOS 7 sos BugFix Update ( https://lists.centos.org/pipermail/centos-announce/2018-December/023125.html ) - CEBA-2018:3664 CentOS 7 selinux-policy BugFix Update ( https://lists.centos.org/pipermail/centos-announce/2018-December/023124.html ) - CESA-2018:3738 Important CentOS 7 ruby Security Update ( https://lists.centos.org/pipermail/centos-announce/2018-December/023122.html ) - CESA-2018:3347 Critical CentOS 7 python-paramiko Security Update ( https://lists.centos.org/pipermail/centos-announce/2018-December/023119.html ) - CESA-2018:3665 Important CentOS 7 NetworkManager Security Update ( https://lists.centos.org/pipermail/centos-announce/2018-December/023116.html ) - CEBA-2018:3442 CentOS 7 lvm2 BugFix Update ( https://lists.centos.org/pipermail/centos-announce/2018-December/023112.html ) - CEBA-2018:3669 CentOS 7 libvirt BugFix Update ( https://lists.centos.org/pipermail/centos-announce/2018-December/023110.html ) - CEBA-2018:3659 CentOS 7 libguestfs BugFix Update ( https://lists.centos.org/pipermail/centos-announce/2018-December/023108.html ) Additional Resources: * Read more about the oVirt 4.2.8 release highlights: http://www.ovirt.org/release/4.2.8/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.2.8/ [2] http://resources.ovirt.org/pub/ovirt-4.2/iso/ -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

1 0

Unable to start or create a virtual machine
by Shikhar Verma 22 Jan '19

22 Jan '19

Hi, I have created the virtual machine from ovirt manager but when I am trying to get the console of the vm to do the installation of it but it is only giving two two line and even i have tried as run once and selected CD ROM as first priority and attached the ISO of centos7 SeaBIOS (version 1.11.0-2.e17) Machine UUID ------- Also, from manager, newly launched vm is showing green.. And from the host machine, it is showing this error Jan 21 19:23:24 servera libvirtd: 2019-01-21 13:53:24.286+0000: 12800: error : qemuDomainAgentAvailable:9133 : Guest agent is not responding: QEMU guest agent is not connected I am using the latest version version of ovirt-engine & host as well. Setup I have create on my Laptop using vmware workstation: Centos server : Manager : server.example.com (192.168.28.128) Centos : Host : servera.example.com 192.168.28.130 Centos : NFS Server : utility.example.com 192.168.28.129 (create fs's as /exports and exported as /exports/iso & /exports/data1 ) In /exports/iso ==> I have rhel 7 & centos 7 iso images and /exports/data1 ( will be using for disk images of vms) From Manager : I have added host and also create domains one as datadomain (/exports/data1) and another one is isodomain (/exports/iso) Now issue i am facing when I am trying to create a vm, it is allowing me to create vm but console is blank.

1 0

Vdo based storage domain
by Leo David 22 Jan '19

22 Jan '19

Hi everyone, I have read and tried to understand how vdo works, and it seems pretty impressive, but i feel like i am missing something. At the end of the day, my question is: Can I entirelly rely on the 10 times increased usable space ? As and example, I have created a 4.8tb volume based on 3x480gb samsung sm863a enterprise ssd devices. (full replica 3). Should I be confident that I can use 4.8tb for my storage domain (vms data store) without concerning about data repetabilitty in the future ? I am just trying to think as an end-user consumer that cannot predict if data that will be written to the device will be compresable or not, and only see 4.8tb as trully usable space. Any thoughts, any experience to share ? Im sorry if my question sounds noob, but i'm just trying to get under end user's hat. Thank you very much, Have a good day ! Leo

1 0

failed to attach a samba active directory
by adam_xu＠adagene.com.cn 22 Jan '19

22 Jan '19

Hello ovirt developers. I have attached a samba ad dc successfully more then 10 times before via this link https://www.ovirt.org/documentation/admin-guide/chap-Users_and_Roles.html but this time, when I try to attach a samba ad dc, I got some certificate error. my test engine version: 4.2.7 or 4.2.8 (both have been tested) full procedure like below: # ovirt-engine-extension-aaa-ldap-setup [ INFO ] Stage: Initializing [ INFO ] Stage: Environment setup Configuration files: ['/etc/ovirt-engine-extension-aaa-ldap-setup.conf.d/10-packaging.conf'] Log file: /tmp/ovirt-engine-extension-aaa-ldap-setup-20190122102450-0b1sjq.log Version: otopi-1.7.8 (otopi-1.7.8-1.el7) [ INFO ] Stage: Environment packages setup [ INFO ] Stage: Programs detection [ INFO ] Stage: Environment customization Welcome to LDAP extension configuration program Available LDAP implementations: 1 - 389ds 2 - 389ds RFC-2307 Schema 3 - Active Directory 4 - IBM Security Directory Server 5 - IBM Security Directory Server RFC-2307 Schema 6 - IPA 7 - Novell eDirectory RFC-2307 Schema 8 - OpenLDAP RFC-2307 Schema 9 - OpenLDAP Standard Schema 10 - Oracle Unified Directory RFC-2307 Schema 11 - RFC-2307 Schema (Generic) 12 - RHDS 13 - RHDS RFC-2307 Schema 14 - iPlanet Please select: 3 Please enter Active Directory Forest name: ntbaobei.com [ INFO ] Resolving Global Catalog SRV record for ntbaobei.com NOTE: It is highly recommended to use secure protocol to access the LDAP server. Protocol startTLS is the standard recommended method to do so. Only in cases in which the startTLS is not supported, fallback to non standard ldaps protocol. Use plain for test environments only. Please select protocol to use (startTLS, ldaps, plain) [startTLS]: Please select method to obtain PEM encoded CA certificate (File, URL, Inline, System, Insecure): File File path: /etc/pki/ca-trust/extracted/pem/ca.pem [ INFO ] Resolving SRV record 'ntbaobei.com' [ INFO ] Connecting to LDAP using 'ldap://dc1.ntbaobei.com:389' [ INFO ] Executing startTLS [ INFO ] Connection succeeded Enter search user DN (for example uid=username,dc=example,dc=com or leave empty for anonymous): vmail(a)ntbaobei.com Enter search user password: [ INFO ] Attempting to bind using 'vmail(a)ntbaobei.com' Are you going to use Single Sign-On for Virtual Machines (Yes, No) [Yes]: NOTE: Profile name has to match domain name, otherwise Single Sign-On for Virtual Machines will not work. Please specify profile name that will be visible to users [ntbaobei.com] [ INFO ] Stage: Setup validation NOTE: It is highly recommended to test drive the configuration before applying it into engine. Login sequence is executed automatically, but it is recommended to also execute Search sequence manually after successful Login sequence. Please provide credentials to test login flow: Enter user name: xingya_xu Enter user password: [ INFO ] Executing login sequence... Login output: 2019-01-22 10:26:06,777+08 INFO ======================================================================== 2019-01-22 10:26:06,800+08 INFO ============================ Initialization ============================ 2019-01-22 10:26:06,801+08 INFO ======================================================================== 2019-01-22 10:26:06,841+08 INFO Loading extension 'ntbaobei.com-authn' 2019-01-22 10:26:06,911+08 INFO Extension 'ntbaobei.com-authn' loaded 2019-01-22 10:26:06,917+08 INFO Loading extension 'ntbaobei.com' 2019-01-22 10:26:06,953+08 INFO Extension 'ntbaobei.com' loaded 2019-01-22 10:26:06,954+08 INFO Initializing extension 'ntbaobei.com-authn' 2019-01-22 10:26:06,960+08 INFO [ovirt-engine-extension-aaa-ldap.authn::ntbaobei.com-authn] Creating LDAP pool 'authz' 2019-01-22 10:26:07,324+08 WARNING Exception: The connection reader was unable to successfully complete TLS negotiation: SSLHandshakeException(sun.security.validator.ValidatorException: No trusted certificate found), ldapSDKVersion=4.0.5, revision=b28fb50058dfe2864171df2448ad2ad2b4c2ad58 2019-01-22 10:26:07,325+08 INFO [ovirt-engine-extension-aaa-ldap.authn::ntbaobei.com-authn] Creating LDAP pool 'authn' 2019-01-22 10:26:08,748+08 WARNING Exception: The connection reader was unable to successfully complete TLS negotiation: SSLHandshakeException(sun.security.validator.ValidatorException: No trusted certificate found), ldapSDKVersion=4.0.5, revision=b28fb50058dfe2864171df2448ad2ad2b4c2ad58 2019-01-22 10:26:08,773+08 WARNING Ignoring records from pool: 'authz' 2019-01-22 10:26:08,774+08 WARNING Ignoring records from pool: 'authz' 2019-01-22 10:26:08,775+08 INFO Extension 'ntbaobei.com-authn' initialized 2019-01-22 10:26:08,776+08 INFO Initializing extension 'ntbaobei.com' 2019-01-22 10:26:08,776+08 INFO [ovirt-engine-extension-aaa-ldap.authz::ntbaobei.com] Creating LDAP pool 'authz' 2019-01-22 10:26:09,414+08 INFO [ovirt-engine-extension-aaa-ldap.authz::ntbaobei.com] LDAP pool 'authz' information: vendor='Samba Team (https://www.samba.org)' version='4.8.8-SerNet-RedHat-18.el7' 2019-01-22 10:26:09,415+08 INFO [ovirt-engine-extension-aaa-ldap.authz::ntbaobei.com] Creating LDAP pool 'gc' 2019-01-22 10:26:10,148+08 WARNING Exception: The connection reader was unable to successfully complete TLS negotiation: SSLHandshakeException(sun.security.validator.ValidatorException: No trusted certificate found), ldapSDKVersion=4.0.5, revision=b28fb50058dfe2864171df2448ad2ad2b4c2ad58 2019-01-22 10:26:10,179+08 INFO [ovirt-engine-extension-aaa-ldap.authz::ntbaobei.com] Creating LDAP pool 'authz(a)ntbaobei.com' 2019-01-22 10:26:10,269+08 WARNING Exception: The connection reader was unable to successfully complete TLS negotiation: SSLHandshakeException(sun.security.validator.ValidatorException: No trusted certificate found), ldapSDKVersion=4.0.5, revision=b28fb50058dfe2864171df2448ad2ad2b4c2ad58 2019-01-22 10:26:10,270+08 WARNING Ignoring records from pool: 'authz(a)ntbaobei.com' 2019-01-22 10:26:10,282+08 WARNING Ignoring records from pool: 'authz(a)ntbaobei.com' 2019-01-22 10:26:10,283+08 INFO [ovirt-engine-extension-aaa-ldap.authz::ntbaobei.com] Available Namespaces: [] 2019-01-22 10:26:10,283+08 INFO Extension 'ntbaobei.com' initialized 2019-01-22 10:26:10,284+08 INFO Start of enabled extensions list 2019-01-22 10:26:10,284+08 INFO Instance name: 'ntbaobei.com', Extension name: 'ovirt-engine-extension-aaa-ldap.authz', Version: '1.3.8', Notes: 'Display name: ovirt-engine-extension-aaa-ldap-1.3.8-1.el7', License: 'ASL 2.0', Home: 'http://www.ovirt.org', Author 'The oVirt Project', Build interface Version: '0', File: '/tmp/tmp01ChKj/extensions.d/ntbaobei.com.properties', Initialized: 'true' 2019-01-22 10:26:10,285+08 INFO Instance name: 'ntbaobei.com-authn', Extension name: 'ovirt-engine-extension-aaa-ldap.authn', Version: '1.3.8', Notes: 'Display name: ovirt-engine-extension-aaa-ldap-1.3.8-1.el7', License: 'ASL 2.0', Home: 'http://www.ovirt.org', Author 'The oVirt Project', Build interface Version: '0', File: '/tmp/tmp01ChKj/extensions.d/ntbaobei.com-authn.properties', Initialized: 'true' 2019-01-22 10:26:10,285+08 INFO End of enabled extensions list 2019-01-22 10:26:10,285+08 INFO ======================================================================== 2019-01-22 10:26:10,285+08 INFO ============================== Execution =============================== 2019-01-22 10:26:10,286+08 INFO ======================================================================== 2019-01-22 10:26:10,286+08 INFO Iteration: 0 2019-01-22 10:26:10,287+08 INFO Profile='ntbaobei.com' authn='ntbaobei.com-authn' authz='ntbaobei.com' mapping='null' 2019-01-22 10:26:10,287+08 INFO API: -->Authn.InvokeCommands.AUTHENTICATE_CREDENTIALS profile='ntbaobei.com' user='testusernamehere' 2019-01-22 10:26:10,290+08 INFO API: <--Authn.InvokeCommands.AUTHENTICATE_CREDENTIALS profile='ntbaobei.com' result=GENERAL_ERROR 2019-01-22 10:26:10,296+08 SEVERE Authn.Result code is: GENERAL_ERROR [ ERROR ] Login sequence failed Please investigate details of the failure (search for lines containing SEVERE log level). Select test sequence to execute (Done, Abort, Login, Search) [Abort]: [ ERROR ] Failed to execute stage 'Setup validation': Aborted by user [ INFO ] Stage: Clean up Log file is available at /tmp/ovirt-engine-extension-aaa-ldap-setup-20190122102450-0b1sjq.log: [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination I have copy the CA certificate file from samba ad dc to /etc/pki/ca-trust/extracted/pem/ca.pem in the engine server. I think the warning "SSLHandshakeException(sun.security.validator.ValidatorException: No trusted certificate found), " is the reason why I can not pass user login test? I once passed the user login test in some older version such as 4.2.6. I can still pass the user login test using startTLS Insecure way. full log has been attached to this mail. thanks. yours Adam

1 0

Re: oVirt Node install - kickstart postintall
by Ryan Barry 21 Jan '19

21 Jan '19

The quick answer is that operations in %post must be performed before 'nodectl init'. If that's done, they'll happily stick. On Mon, Jan 14, 2019, 9:29 PM Brad Riemann <Brad.Riemann(a)cloud5.com wrote: > Can you send over the whole %post segment i via pastebin? I think i've run > across something similar that i addressed, but just want to be sure. > > > Brad Riemann > Sr. System Architect > Cloud5 Communications > > ------------------------------ > *From:* jeanbaptiste(a)nfrance.com <jeanbaptiste(a)nfrance.com> > *Sent:* Friday, January 11, 2019 1:51:14 AM > *To:* users(a)ovirt.org > *Subject:* [ovirt-users] oVirt Node install - kickstart postintall > > CAUTION: This email originated from outside of CLOUD5. Do not click links > or open attachments unless you recognize the sender and know the content is > safe. > > > Hello everybody, > > Since days, I'm trying to install oVirt (via Foreman) in network mode > (TFTP net install). > All is great, but I want to make some actions in postinstall (%post). > Some actions are relatated to /etc/sysconfig/network-interfaces and > another action is related to root authorized_keys. > > When I try to add pub-key to a created authorized_keys for root, I work > (verified into anaconda. > But after installation and anaconda reboot, I've noticed all my %post > actions in /(root) are discared. After reboot, there is nothing in > /root/.ssh for example. > Whereas, in /etc, all my modications are preserved. > > I thought to a Selinux relative issue, but It is not relative to Selinux > > I miss something. Please can you help to understand how oVirt install / > partition work ? > > thanks for all > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/BCQEKHCPSFDEF… > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/TGT7K3N245SH3… >

2 1

multiple engines (active passive)
by maoz zadok 21 Jan '19

21 Jan '19

Hello users, After a painful experience with a crashed engine and a problematic recovery from a backup, I was thinking to create one more engine in standby mode in the same network, that will automatically recover backup files from the active engine on a daily/hourly basis. This way I'll run recovery tests every day automatically and easily switch in case of engine failure with a DNS record change to the passive engine. So the main question, is it harmful to have more then one engine alive if only one is been modified? can the standby engine affect the host nodes?

9 10

Re: GlusterFS and oVirt
by Strahil 21 Jan '19

21 Jan '19

1 0

How to import from another oVirt / RHV environment
by Gianluca Cecchi 20 Jan '19

20 Jan '19

Hello, I have two different oVirt 4.2 environments and I want to migrate some big VMs from one to another. I'm not able to detach and attach the block based domain where are the disks of source. And I cannot use export domain functionality. But the 2 environments, both hosts and engines, are able to communicate. Can I use in some way the import Virtual Machine functionality with the "KVM(via Libvirt)" source type? Or is there (eventually via command line) a way to use virt-v2v in this case? Thanks, Gianluca

3 9