- Users - oVirt List Archives

Re: [ovirt-users] Yum error while installing host on Centos7
by Yanir Quinn 01 Aug '17

01 Aug '17

where did you manually install the packages ? engine or host machine ? you can you provide the engine.log to see what might cause the error on the engine's side. maybe rollback the last yum transaction you did and try to run the engine again. as far as for the host installation you might need to check the exiting repositories (Cenots or other existing repos on the machine) , its not recommended to use --skip-broken usually when adding a host. On Tue, Aug 1, 2017 at 11:51 AM, Iurcev, Massimiliano <miurcev(a)inogs.it> wrote: > Unfortunately this didn't work. I tried also to disable totally selinux > without success. > > Then I decided to install gtk2 manually with the --skip-broken option, and > apparently everything went fine. > After this, the host installation goes on without errors. > It says "Installation is closing up", then gets stuck indefinitely. > Now the host-engine looks dead or messed up, even after a reboot... more > in detail, the web portal is no longer accessible. :( > > > > On 30 July 2017 at 10:58, Yanir Quinn <yquinn(a)redhat.com> wrote: > >> Might be a selinux related issue, similar threads suggest either to >> disable selinux completely or run on host: >> >> # setenforce 0 >> # yum clean expire-cache >> # yum update selinux-policy\* >> # setenforce 1 >> >> keeping an eye out for other reasons/solutions. >> >> Regards, >> Yanir Quinn >> >> On Thu, Jul 27, 2017 at 5:32 PM, Iurcev, Massimiliano <miurcev(a)inogs.it> >> wrote: >> >>> I installed ovirt-engine on Centos7. My target is to have a single host >>> machine. >>> During the installation of the (first and unique) host, I get an error: >>> >>> Failed to install Host xxxx. Yum Non-fatal POSTIN scriptlet failure in >>> rpm package gtk2-2.24.28-8.el7.x86_64. >>> >>> This error is followed by other errors: >>> >>> Failed to install Host xxxx. Failed to execute stage 'Package >>> installation': One or more elements within Yum transaction failed. >>> >>> and finally: >>> Host xxxx installation failed. Command returned failure code 1 during >>> SSH session 'root(a)xxxx.mydomain.it'. >>> >>> All other libraries are yum-installed without problems. >>> >>> _______________________________________________ >>> Users mailing list >>> Users(a)ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/users >>> >>> >> >

1 0

Re: [ovirt-users] PXE boot of oVirt Node 4.1
by Kamarasu Alagarsamy 01 Aug '17

01 Aug '17

Hi Pavol I have similar requirement for Ovirt 4.1 PXE boot on UEFI enabled systems, however not able to do successful kickstart installation. Facing two issues 1) nodectl init or imgbase layout —init not working because of the reason commands not found 2) System keeps on network install cycle due to boot loader not been set or not installed - I don’t know sure exactly why? Could you please help with these issues? kickstart file contents —————————- liveimg —url=http:/../../squasfs.img <— path shortened ignoredisk —all —initlabel zerombr clearpart —all —initlabel autopart —type=thinp bootloader —location=mbr text reboot %post —erroronfail nodectl init %end Regards Kamarasu

1 0

fence issue adding host
by Bill James 31 Jul '17

31 Jul '17

--------------DDA22B530AEEAC5C11E37F1E Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit I'm adding 3 hardware nodes to our cluster. All 3 same type of server and software, HP DL360 G8, centos 7. One fails the fence agent test. The one I'm having problems with has a newer version of ilo firmware, not sure if related. Troublemaker: 2.54 Others: 2.53 ovirt-engine-4.1.0.4-1.el7.centos.noarch vdsm-4.19.4-1.el7.centos.x86_64 2017-07-26 15:14:30,215-07 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] EVENT_ID: FENCE_OPERATION_USING_AGENT_AND_PROXY_STARTED(9,020), Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: Executing power management status on Host ovirt6.j2noc.com using Proxy Host ovirt1.j2noc.com and Fence Agent ilo4:10.144.254.89. 2017-07-26 15:14:30,216-07 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] (default task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] START, FenceVdsVDSCommand(HostName = ovirt1.j2noc.com, FenceVdsVDSCommandParameters:{runAsync='true', hostId='23d2c0ab-5dd1-43af-9db3-2a426a539faf', targetVdsId='00000000-0000-0000-0000-000000000000', action='STATUS', agent='FenceAgent:{id='null', hostId='null', order='1', type='ilo4', ip='10.144.254.89', port='null', user='Administrator', password='***', encryptOptions='false', options='power_wait=4'}', policy='null'}), log id: 1498b3c4 *2017-07-26 15:14:30,414-07 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] (default task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] FINISH, FenceVdsVDSCommand, return: FenceOperationResult:{status='ERROR', powerStatus='UNKNOWN', message='[Failed: Unable to obtain correct plug status or plug is not available, , ]'}, log id: 1498b3c4* 2017-07-26 15:14:30,420-07 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] EVENT_ID: FENCE_OPERATION_USING_AGENT_AND_PROXY_FAILED(9,021), Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: Execution of power management status on Host ovirt6.j2noc.com using Proxy Host ovirt1.j2noc.com and Fence Agent ilo4:10.144.254.89 failed. 2017-07-26 15:14:30,420-07 WARN [org.ovirt.engine.core.bll.pm.FenceAgentExecutor] (default task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] Fence action failed using proxy host '10.144.110.99', trying another proxy 2017-07-26 15:14:30,740-07 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] EVENT_ID: FENCE_OPERATION_USING_AGENT_AND_PROXY_STARTED(9,020), Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: Executing power management status on Host ovirt6.j2noc.com using Proxy Host ovirt2.j2noc.com and Fence Agent ilo4:10.144.254.89. 2017-07-26 15:14:30,741-07 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] (default task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] START, FenceVdsVDSCommand(HostName = ovirt2.j2noc.com, FenceVdsVDSCommandParameters:{runAsync='true', hostId='91d8fa70-fd24-4530-90f7-982ff068230b', targetVdsId='00000000-0000-0000-0000-000000000000', action='STATUS', agent='FenceAgent:{id='null', hostId='null', order='1', type='ilo4', ip='10.144.254.89', port='null', user='Administrator', password='***', encryptOptions='false', options='power_wait=4'}', policy='null'}), log id: 67d837da 2017-07-26 15:14:30,898-07 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] (default task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] FINISH, FenceVdsVDSCommand, return: FenceOperationResult:{status='ERROR', powerStatus='UNKNOWN', message='[Failed: Unable to obtain correct plug status or plug is not available, , ]'}, log id: 67d837da 2017-07-26 15:14:30,903-07 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] EVENT_ID: FENCE_OPERATION_USING_AGENT_AND_PROXY_FAILED(9,021), Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: Execution of power management status on Host ovirt6.j2noc.com using Proxy Host ovirt2.j2noc.com and Fence Agent ilo4:10.144.254.89 failed. I'm not sure the right syntax for fence_ipmilan since even a "good" host fails: [root@ovirt4 prod vdsm]# fence_ipmilan -a 10.144.254.87 -P -l Administrator -p *** -o status -v chassis power status Executing: /usr/bin/ipmitool -I lanplus -H 10.144.254.87 -U Administrator -P [set] -p 623 -L ADMINISTRATOR chassis power status 1 Error: Unable to establish IPMI v2 / RMCP+ session Failed: Unable to obtain correct plug status or plug is not available Any ideas on what the issue is? --------------DDA22B530AEEAC5C11E37F1E Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: 8bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> I'm adding 3 hardware nodes to our cluster. All 3 same type of server and software, HP DL360 G8, centos 7. One fails the fence agent test. The one I'm having problems with has a newer version of ilo firmware, not sure if related. Troublemaker: 2.54 Others: 2.53 ovirt-engine-4.1.0.4-1.el7.centos.noarch vdsm-4.19.4-1.el7.centos.x86_64 2017-07-26 15:14:30,215-07 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] EVENT_ID: FENCE_OPERATION_USING_AGENT_AND_PROXY_STARTED(9,020), Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: Executing power management status on Host ovirt6.j2noc.com using Proxy Host ovirt1.j2noc.com and Fence Agent ilo4:10.144.254.89. 2017-07-26 15:14:30,216-07 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] (default task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] START, FenceVdsVDSCommand(HostName = ovirt1.j2noc.com, FenceVdsVDSCommandParameters:{runAsync='true', hostId='23d2c0ab-5dd1-43af-9db3-2a426a539faf', targetVdsId='00000000-0000-0000-0000-000000000000', action='STATUS', agent='FenceAgent:{id='null', hostId='null', order='1', type='ilo4', ip='10.144.254.89', port='null', user='Administrator', password='***', encryptOptions='false', options='power_wait=4'}', policy='null'}), log id: 1498b3c4 2017-07-26 15:14:30,414-07 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] (default task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] FINISH, FenceVdsVDSCommand, return: FenceOperationResult:{status='ERROR', powerStatus='UNKNOWN', message='[Failed: Unable to obtain correct plug status or plug is not available, , ]'}, log id: 1498b3c4 2017-07-26 15:14:30,420-07 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] EVENT_ID: FENCE_OPERATION_USING_AGENT_AND_PROXY_FAILED(9,021), Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: Execution of power management status on Host ovirt6.j2noc.com using Proxy Host ovirt1.j2noc.com and Fence Agent ilo4:10.144.254.89 failed. 2017-07-26 15:14:30,420-07 WARN [org.ovirt.engine.core.bll.pm.FenceAgentExecutor] (default task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] Fence action failed using proxy host '10.144.110.99', trying another proxy 2017-07-26 15:14:30,740-07 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] EVENT_ID: FENCE_OPERATION_USING_AGENT_AND_PROXY_STARTED(9,020), Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: Executing power management status on Host ovirt6.j2noc.com using Proxy Host ovirt2.j2noc.com and Fence Agent ilo4:10.144.254.89. 2017-07-26 15:14:30,741-07 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] (default task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] START, FenceVdsVDSCommand(HostName = ovirt2.j2noc.com, FenceVdsVDSCommandParameters:{runAsync='true', hostId='91d8fa70-fd24-4530-90f7-982ff068230b', targetVdsId='00000000-0000-0000-0000-000000000000', action='STATUS', agent='FenceAgent:{id='null', hostId='null', order='1', type='ilo4', ip='10.144.254.89', port='null', user='Administrator', password='***', encryptOptions='false', options='power_wait=4'}', policy='null'}), log id: 67d837da 2017-07-26 15:14:30,898-07 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] (default task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] FINISH, FenceVdsVDSCommand, return: FenceOperationResult:{status='ERROR', powerStatus='UNKNOWN', message='[Failed: Unable to obtain correct plug status or plug is not available, , ]'}, log id: 67d837da 2017-07-26 15:14:30,903-07 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-52) [4d72d360-2b92-43f6-b2df-e80ee305c622] EVENT_ID: FENCE_OPERATION_USING_AGENT_AND_PROXY_FAILED(9,021), Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: Execution of power management status on Host ovirt6.j2noc.com using Proxy Host ovirt2.j2noc.com and Fence Agent ilo4:10.144.254.89 failed. I'm not sure the right syntax for fence_ipmilan since even a "good" host fails: [root@ovirt4 prod vdsm]# fence_ipmilan -a 10.144.254.87 -P -l Administrator -p *** -o status -v chassis power status Executing: /usr/bin/ipmitool -I lanplus -H 10.144.254.87 -U Administrator -P [set] -p 623 -L ADMINISTRATOR chassis power status 1 Error: Unable to establish IPMI v2 / RMCP+ session Failed: Unable to obtain correct plug status or plug is not available Any ideas on what the issue is? </body> </html> --------------DDA22B530AEEAC5C11E37F1E--

3 4

[ANN] oVirt 4.1.4 GA is now available
by Lev Veyde 31 Jul '17

31 Jul '17

The oVirt Project is pleased to announce the general availability of the oVirt 4.1.4, as of July 31th, 2017 This update is the GA release to the 4.1 series. 4.1.4 brings more than 20 enhancements and more than 90 bugfixes, including more than 70 high or urgent severity fixes, on top of oVirt 4.1 series This release is available now for: * Fedora 24 (tech preview) * Red Hat Enterprise Linux 7.3 or later * CentOS Linux (or similar) 7.3 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.3 or later * CentOS Linux (or similar) 7.3 or later * oVirt Node 4.1 * Fedora 24 (tech preview) See the release notes draft [3] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available - oVirt Live is already available[4] - oVirt Node is already available[4] Additional Resources: * Read more about the oVirt 4.1.4 release highlights: http://www.ovirt.org/release/4.1.4/ * 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] https://www.ovirt.org/community/ [2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt [3] http://www.ovirt.org/release/4.1.4/ [4] resources.ovirt.org/pub/ovirt-4.1/iso/ -- Lev Veyde Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

3 2

official status of Windows support in oVirt/RHEV ?
by Matthias Leopold 31 Jul '17

31 Jul '17

Hi, can someone please point me to resources about official status of Windows support in oVirt and RHEV? are there differences between oVirt and RHEV? i'm not talking about technical details, i know that eg. Windows 2008 or 2016 runs in oVirt, it's about support contracts. i looked at https://www.redhat.com/cms/managed-files/rh-red-hat-virtualization-datashee…, there you have the terms "Full support", "Support" and "Vendor Support". What's the difference? thx matthias

2 2

problem while moving/copying disks: vdsm low level image copy failed
by Johan Bernhardsson 31 Jul '17

31 Jul '17

Hello, We get this error message while moving or copying some of the disks on our main cluster running 4.1.2 on centos7 This is shown in the engine: VDSM vbgkvm02 command HSMGetAllTasksStatusesVDS failed: low level Image copy failed I can copy it inside the host. And i can use dd to copy. Haven't tried to run qemu-img manually yet. This is from vdsm.log on the host: 2017-07-28 09:07:22,741+0200 ERROR (tasks/6) [root] Job u'c82d4c53- 3eb4-405e-a2d5-c4c77519360e' failed (jobs:217) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/jobs.py", line 154, in run self._run() File "/usr/share/vdsm/storage/sdm/api/copy_data.py", line 88, in _run self._operation.wait_for_completion() File "/usr/lib/python2.7/site-packages/vdsm/qemuimg.py", line 329, in wait_for_completion self.poll(timeout) File "/usr/lib/python2.7/site-packages/vdsm/qemuimg.py", line 324, in poll self.error) QImgError: cmd=['/usr/bin/taskset', '--cpu-list', '0-15', '/usr/bin/nice', '-n', '19', '/usr/bin/ionice', '-c', '3', '/usr/bin/qemu-img', 'convert', '-p', '-t', 'none', '-T', 'none', '-f', 'raw', u'/rhev/data-center/mnt/glusterSD/vbgsan02:_fs02/0924ff77-ef51- 43 5b-b90d-50bfbf2e8de7/images/750f4184-b852-4b00-94fc- 476f3f5b93c7/3fe43487-3302-4b34-865a-07c5c6aedbf2', '-O', 'raw', u'/rhev/data-center/mnt/glusterSD/10.137.30.105:_fs03/5d47a297-a21f- 4587-bb7c-dd00d52010d5/images/750f4184-b852-4b00-94fc- 476f3f5b93c7/3fe43487-3302-4b34-865 a-07c5c6aedbf2'], ecode=1, stdout=, stderr=qemu-img: error while reading sector 12197886: No data available , message=None The storage domains are all based on gluster. The storage domains that we see this on is configured as dispersed volumes. Found a way to "fix" the problem. And that is to run dd if=/dev/vda of=/dev/null bs=1M inside the virtual guest. After that we can copy an image or use storage livemigration. Is this a gluster problem or an vdsm problem? Or could it be something with qemu-img? /Johan

2 4

Hosted Engine increase memory
by gregor 30 Jul '17

30 Jul '17

Hi, is it possible to increase the memory of an hosted engine after the installation? cheers gregor

3 2

Yum error while installing host on Centos7
by Iurcev, Massimiliano 30 Jul '17

30 Jul '17

I installed ovirt-engine on Centos7. My target is to have a single host machine. During the installation of the (first and unique) host, I get an error: Failed to install Host xxxx. Yum Non-fatal POSTIN scriptlet failure in rpm package gtk2-2.24.28-8.el7.x86_64. This error is followed by other errors: Failed to install Host xxxx. Failed to execute stage 'Package installation': One or more elements within Yum transaction failed. and finally: Host xxxx installation failed. Command returned failure code 1 during SSH session 'root(a)xxxx.mydomain.it'. All other libraries are yum-installed without problems.

2 1

ovirt and mixed selinux
by Bill James 30 Jul '17

30 Jul '17

I was hoping to migrate my systems to using selinux gradually. I added 3 new nodes with selinux in permissive mode. Migration fails to any of the previous hosts that currently have selinux disabled. Is it an all or nothing deal? Obviously not easy to reboot all nodes at once. 2017-07-28 09:35:43,616 ERROR (migsrc/8c566813) [virt.vm] (vmId='8c566813-4bee-4f04-be23-c9fc10e1e1f2') unsupported configuration: Unable to find security driver for model selinux (migration:265) 2017-07-28 09:35:43,641 ERROR (migsrc/8c566813) [virt.vm] (vmId='8c566813-4bee-4f04-be23-c9fc10e1e1f2') Failed to migrate (migration:405) Traceback (most recent call last): ovirt-engine-4.1.0.4-1.el7.centos.noarch libselinux-utils-2.5-6.el7.x86_64 related: http://lists.ovirt.org/pipermail/users/2016-October/076878.html

2 1

Quick way to generate vmconsole host keys?
by Richard Chan 30 Jul '17

30 Jul '17

Is there a quick way to generate the vmconsole host keys without putting the host into maintenance and reinstalling? -- Richard Chan

1 0