- Users - oVirt List Archives

glusterfs backup-volfile-servers lost
by g.vasilopoulos＠uoc.gr 19 Jun '18

19 Jun '18

I have a 4 node setup (centos 7) with hosted engine on glusterfs (replica 3 arbiter1). Gluster fs is like this ohost01 104G brick (real data) ohost02 104g brick (real data) ohost04 104g brick (arbiter) ohost05 104g partition used as nfs-storage. hosted engine is on gluster. I also have an fc domain of 3,6 TB mount of gluster is like this storage=172.16.224.10:/engine mnt_options=backup-volfile-servers=172.16.224.11:172.16.224.13 172.16.224.10 is ohost01 storage network 172.16.224.12 is ohost02 storage network 172.16.224.13 is ohost04 storage network Today I upgraded all nodes. I did it like this: hosted-engine was running on ohost05 at the time Put ohost04 (arbiter) on maintenance and did upgrade (ok) Same with ohost02 Ohost01 was spm so I did ohost05 spm then put ohost01 on maintenance and then upgraded it. I notticed that engine VM paused during the process (which usualy does not happen) as I have backup-volfile-servers mount option. But today I notticed that this option is ignored. On the hosts I also noted that mount is like this 172.16.224.10:/engine on /rhev/data-center/mnt/glusterSD/172.16.224.10:_engine type fuse.glusterfs (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072) so reduduncy is gone from gluster and I cannot figure out why. If I restart ohost01 (after maintenance) hosted engine get paused until ohost01 comes back up. How can I solve this issue

2 6

Lost host after upgrade/reboot
by Nicolas Ecarnot 19 Jun '18

19 Jun '18

Hello, TL;DR : engine stops talking with rebooted host. [oVirt 4.2.3.5-1.el7.centos] - From the web gui, upgrading a host, allowing the reboot checkbox checked - upgrade is OK (/var/log/yum.log is showing successful updates + the Ansible host deploy log is also OK) - reboot is OK (clean, SSH OK...) - the host eventually appears as "Install failed" - the engine.log is telling : > 2018-06-19 10:02:24,896+02 ERROR > [org.ovirt.engine.core.bll.SshHostRebootCommand] > (EE-ManagedThreadFactory-commandCoordinator-Thread-7) [6e32b3ac] SSH > reboot command failed on host 'serv-hv-prds06': SSH session timeout > host 'root@ serv-hv-prds06' Stdout: Stderr: 2018-06-19 > 10:02:25,028+02 ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (EE-ManagedThreadFactory-commandCoordinator-Thread-7) [6e32b3ac] > EVENT_ID: SYSTEM_FAILED_SSH_HOST_RESTART(198), A restart usin g SSH > initiated by the engine to Host serv-hv-prds06 has failed. 2018-06-19 > 10:02:25,185+02 INFO > [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] > (EE-ManagedThreadFactory-commandCoordinator-Thread-7) [6e32b3ac] > START, SetVdsStatusVDSCommand(HostName = serv-hv-prds06, > SetVdsStatusVDSCom > mandParameters:{hostId='9c1566a4-8432-4de6-b30d-fd3b8e5fafca', > status='InstallFailed', nonOperationalReason='NONE', > stopSpmFailureLogged='false', maintenanceReason='null'}), log id: > 833f9bd 2018-06-19 10:02:25,191+02 INFO > [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] > (EE-ManagedThreadFactory-commandCoordinator-Thread-7) [6e32b3ac] > FINISH, SetVdsStatusVDSCommand, log id: 833f9bd 2018-06-19 > 10:02:25,191+02 ERROR > [org.ovirt.engine.core.bll.hostdeploy.UpgradeHostInternalCommand] > (EE-ManagedThreadFactory-commandCoordinator-Thread-7) [6e32b3ac] > Engine failed to restart via ssh host 'serv-hv-prds06' ('9c1566a4- > 8432-4de6-b30d-fd3b8e5fafca') after upgrade 2018-06-19 > 10:02:25,256+02 ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (EE-ManagedThreadFactory-commandCoordinator-Thread-7) > [8b7c6e7d-1a22-407c-818b-849e67b94051] EVENT_ID: > HOST_UPGRADE_FAILED(841 ), Failed to upgrade Host serv-hv-prds06 > (User: necarnot@sdis.isere.fr@SDIS38-authz). 2018-06-19 > 10:02:30,755+02 ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (EE-ManagedThreadFactory-engineScheduled-Thread-69) > [8b7c6e7d-1a22-407c-818b-849e67b94051] EVENT_ID: > HOST_UPGRADE_FAILED(841), Failed to upgrade Host serv-hv-prds06 > (User: necarnot@sdis.isere.fr@SDIS38-authz). - Manually activating the host puts it back on track without issue The usual SSH communications between the engine and the host are usually very sound (VM migrations, maintenance...). On this oVirt DC, I reproduced this issue twice on 2 different hosts. In this engine log above, you see that I'm using my account to manage this engine, as I 'm doing for years with no issue. I'll try the exact same path with admin@internal to see what could change, but I don't see the link. What other logs could I give you to debug this? Regards, -- Nicolas ECARNOT

1 1

oVirt Node 4.1 at www.ovirt.org/node/ is 404
by clam2718＠gmail.com 19 Jun '18

19 Jun '18

I am trying to download Node 4.1 from https://www.ovirt.org/node but am receiving a 404 error. Is there an alternative link to try for the latest stable release? Thanks, Charles

3 2

RHEL 7.5 as an oVirt host - missing packages
by jasonmicron＠gmail.com 19 Jun '18

19 Jun '18

Hello everyone, I believe there is a potential issue with the RHEL 7 yum repos and at least one missing RPM to convert a pre-existing RHEL 7.5 system into an oVirt host node. I have the following YUM repos enabled in my RHEL 7 system, according to the documentation: rhel-7-server-rpms rhel-7-server-optional-rpms rhel-7-server-extras-rpms I installed the oVirt 4.2 RPM: ovirt-release42-4.2.3.1-1.el7.noarch I then go to the engine GUI to add the new host, and during the installation process I am informed that there is a YUM transaction error with the following package being unavailable: python-qpid-proton (as a dependency install for the python-gofer-proton package) I dug around Red Hat's YUM repos and discovered that this package only exists in the rhel-7-server-satellite-tools-6.{1..3}-rpms YUM repos from the official Red Hat site. I tried enabling this repo (specifically the rhel-7-server-satellite-tools-6.3-rpms repo) to see which version of the package would be installed, and it appears to be a custom spin for Satellite in the release version: ============================================================================================================= Package Arch Version Repository Size ============================================================================================================= Installing: python-gofer-proton noarch 2.7.7-3.el7sat lab1-rhel-7-server-satellite-tools-6.3-rpms 54 k Installing for dependencies: python-gofer noarch 2.7.7-3.el7sat lab1-rhel-7-server-satellite-tools-6.3-rpms 132 k python-qpid-proton x86_64 0.16.0-7.el7 lab1-rhel-7-server-satellite-tools-6.3-rpms 216 k qpid-proton-c x86_64 0.16.0-7.el7 lab1-rhel-7-server-satellite-tools-6.3-rpms 131 k Transaction Summary ============================================================================================================== Install 1 Package (+3 Dependent packages) Since I shouldn't even require this repo according to the official oVirt install documentation for hosts, and the fact that these packages appear to be custom spins (el7sat) versions, I was curious if this is OK to use for oVirt or if I have encountered a dependency bug with RHEL 7.5 and oVirt 4.2? Any advice would be welcomed.

2 2

Gluster Deployment: Repositories, Packages
by femi adegoke 18 Jun '18

18 Jun '18

In Step 2 of the HE deployment what should be filled in here? Repositories: ?? Packages: ??

4 5

oVirt 4.2 vm-portal console
by Staniforth, Paul 18 Jun '18

18 Jun '18

Hello, I have installed a test system for oVirt 4.2 and it seems that in the vm portal I can't change the console to vnc or spice+vnc. It seems that this is only available in the admin portal. Am I missing something? Thanks, Paul S. To view the terms under which this email is distributed, please go to:- http://disclaimer.leedsbeckett.ac.uk/disclaimer/disclaimer.html

2 1

Ovirt Node NG (4.2.3.1-0.20180530) Boot fail ISCSI using ibft after installation
by Ralf Schenk 18 Jun '18

18 Jun '18

Hello, I successfully installed Ovirt Node NG from ISO to an ISCSI target attached via first network interface by using following extensions to the grub cmdline: "rd.iscsi.ibft=1 ip=ibft ip=eno2:dhcp" I want to use the server as diskless ovirt-node-ng Server. After successful install the system reboots and starts up but it fails later in dracut even having detected correctly the disk and all the LV's. I think "iscsistart" is run multiple times even after already being logged in to the ISCSI-Target and that fails finally like that: *[ 147.644872] localhost dracut-initqueue[1075]: iscsistart: initiator reported error (15 - session exists)* [ 147.645588] localhost dracut-initqueue[1075]: iscsistart: Logging into iqn.2018-01.de.databay.office:storage01.epycdphv02-disk1 172.16.1.3:3260,1 [ 147.651027] localhost dracut-initqueue[1075]: Warning: 'iscsistart -b ' failed with return code 0 [ 147.807510] localhost systemd[1]: Starting Login iSCSI Target... [ 147.809293] localhost iscsistart[6716]: iscsistart: TargetName not set. Exiting iscsistart [ 147.813625] localhost systemd[1]: iscsistart_iscsi.service: main process exited, code=exited, status=7/NOTRUNNING [ 147.824897] localhost systemd[1]: Failed to start Login iSCSI Target. [ 147.825050] localhost systemd[1]: Unit iscsistart_iscsi.service entered failed state. [ 147.825185] localhost systemd[1]: iscsistart_iscsi.service failed. -- Mit freundlichen Grüßen Ralf Schenk

2 1

HostedEngine and affinity groups
by tehnic＠take3.ro 18 Jun '18

18 Jun '18

Hi, i operate a 3 node ovirt42 cluster (hyperconverged). Now i would like to isolate the HostedEngine from the other VMs. The reason is to minimize the impact of outage of one of the nodes. When the node with the HE is away there is no impact at all on the running VMs. If one of the other nodes goes down, then i have still a running HE which restarts the missing VMs on remaining nodes fast again. I cannot use hard affinity because in case of failure i need all resources of the 2 remaining modes, so i configured a soft negative affinity group for every VM between this VM and the HE. As a first test i migrated the HE to a node with VMs but even after a while nothing happened. I would have expected that either the HE or the VMs on this node would have been migrated to fullfill the soft negative affinity. Now my questions: Are my thoughts correct? Is there a better solution than making one (soft negative) affinity group for every VM to isolate from HE? Does the affinity group enforcement engine work at all with soft rules? Regards, Robert

2 1

Ovirt 4.2 hosted engine deploy failed
by Lakhwinder Rai 18 Jun '18

18 Jun '18

i have error while installing hosted engine.if anybody have solution for this,please help i stuck here from two days. [ INFO ] TASK [Wait for the host to be up] [ ERROR ] fatal: [localhost]: FAILED! => {"ansible_facts": {"ovirt_hosts": []}, "attempts": 120, "changed": false} [ INFO ] TASK [include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [Remove local vm dir] [ INFO ] changed: [localhost] [ INFO ] TASK [Notify the user about a failure] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "The system may not be provisioned according to the playbook results: please check the logs for the issue, fix accordingly or re-deploy from scratch.\n"} thanks

3 2

VM can't start: Unknown CPU-Model
by Tobias Scheinert 18 Jun '18

18 Jun '18

Hi, we see here a confusing problem. A college reboots/shutdown his VMs for maintenance. After that he starts the VMs (~20), but one of them throws following error: > VM <name> is down with error. Exit message: internal error: Unknown CPU-Model SandyBridge,+spec-ctrl All nodes of the clusters are reporting: > CPU Type: > Intel SandyBridge IBRS Family And the cluster is configured with: > Cluster CPU Type: > Intel SandyBridge IBRS Family My quick fix for the vm was, that I used a specific (not the cluster default) CPU-Model without the spectre/meltdown mitigation: > Guest CPU Type: > SandyBridge I've also tried to select manually "SandyBridge,+spec-ctrl". But when I do this the wizard blocks and surround the field with a red border (see picture in the attachment). Any idea? Greeting Tobias

1 0