- Users - oVirt List Archives

oVirtNode 4.3.3 - Missing os-brick
by Stefano Danzi 16 Apr '19

16 Apr '19

Hello, I've just upgrade one node host to v. 4.3.3 and I can see this entry in logs every 10 seconds: ==> /var/log/vdsm/vdsm.log <== 2019-04-16 18:03:06,417+0200 INFO (jsonrpc/5) [root] managedvolume not supported: Managed Volume Not Supported. Missing package os-brick.: ('Cannot import os_brick',) (caps:150)

4 4

Gluster suggestions
by Magnus Isaksson 16 Apr '19

16 Apr '19

Hello I would like some suggestions on what type of solution with Gluster i should use. I have 4 hosts with 3 disks each, i want to user as much space as possible but also some redundancy, like raid5 or 6 The 4 hosts are running oVirt on CentOS 7 I have 2 clusters due to some licensing issues, so i cant use ovirts setup of gluster Today i have set it up as follows Type: Disperse Number of Bricks: 1 x (8 + 4) = 12 So i have 3 bricks per host (one brick per disk) But this setup is not working very well, as soon as i get some traffic on the volume this start to fail on the ovirt nodes, loosing connection etc. All hosts are connected via 10G interface So any suggestions on how i would set this up as best is much appreciated. Regards Magnus Isaksson

1 0

[ANN] oVirt 4.3.3 is now generally available
by Sandro Bonazzola 16 Apr '19

16 Apr '19

The oVirt Project is pleased to announce the general availability of oVirt 4.3.3 as of April 16th, 2019. This update is the third in a series of stabilization updates to the 4.3 series. This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later * oVirt Node 4.3 (available for x86_64 only) Experimental tech preview for x86_64 and s390x architectures for Fedora 28 is also included. See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available - oVirt Node is already available[2] oVirt Node has been updated including: - oVirt 4.3.3: http://www.ovirt.org/release/4.3.3/ - ansible-2.7.10: https://github.com/ansible/ansible/blob/stable-2.7/changelogs/CHANGELOG-v2.… - glusterfs-5.5: https://docs.gluster.org/en/latest/release-notes/5.5/ - Latest CentOS updates including: - CESA-2019:0679 Important CentOS 7 libssh2 Security Update <https://lists.centos.org/pipermail/centos-announce/2019-April/023259.html> - CESA-2019:0710 Important CentOS 7 python Security Update <https://lists.centos.org/pipermail/centos-announce/2019-April/023268.html> - CEEA-2019:0507 CentOS 7 shadow-utils Enhancement Update <https://lists.centos.org/pipermail/centos-announce/2019-March/023228.html> - CEBA-2019:0519 CentOS 7 NetworkManager BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-March/023242.html> - CEBA-2019:0509 CentOS 7 dbus BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-March/023245.html> - CEBA-2019:0515 CentOS 7 fcoe-utils BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-March/023246.html> - CEBA-2019:0728 CentOS 7 glibc BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-April/023269.html> - CEBA-2019:0518 CentOS 7 gnutls BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-March/023233.html> - CEBA-2019:0508 CentOS 7 ipa BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-March/023241.html> - CEBA-2019:0513 CentOS 7 libguestfs BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-March/023232.html> - CEBA-2019:0521 CentOS 7 libvirt BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-March/023239.html> - CEBA-2019:0500 CentOS 7 nss-pem BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-March/023240.html> - CEBA-2019:0503 CentOS 7 sos BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-March/023231.html> - CEBA-2019:0496 CentOS 7 tuned BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-March/023230.html> - CEBA-2019:0689 CentOS 7 tzdata BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-April/023260.html> - CEBA-2019:0504 CentOS 7 util-linux BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-March/023226.html> - CEBA-2019:0516 CentOS 7 xfsprogs BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-March/023227.html> Additional Resources: * Read more about the oVirt 4.3.3 release highlights: http://www.ovirt.org/release/4.3.3/ * 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.3.3/ [2] http://resources.ovirt.org/pub/ovirt-4.3/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

active directory: how to replace user@corp.mydomain.com with user@mydomain.com
by Jarosław Prokopowski 16 Apr '19

16 Apr '19

I configured active directory authentication but the problem is I need to replace user(a)corp.mydomain.com with user(a)mydomain.com to be able to authenticate. ovirt-engine-extension-aaa-misc has been installed and I configured it as shown below but still it is not working. Do you have any idea what is wrong and how to fix it? /etc/ovirt-engine/aaa/corp.mydomain.com.properties: -------------------------------------------------- include = <ad.properties> vars.domain = corp.mydomain.com vars.user = CN=user,DC=xxx,DC=corp,DC=mydomain,DC=com vars.password = password pool.default.auth.simple.bindDN = ${global:vars.user} pool.default.auth.simple.password = ${global:vars.password} pool.default.serverset.type = srvrecord pool.default.serverset.srvrecord.domain = ${global:vars.domain} /etc/ovirt-engine/extensions.d/mapping.properties: ------------------------------------------------- ovirt.engine.extension.name = mapping ovirt.engine.extension.bindings.method = jbossmodule ovirt.engine.extension.binding.jbossmodule.module = org.ovirt.engine-extensions.aaa.misc ovirt.engine.extension.binding.jbossmodule.class = org.ovirt.engineextensions.aaa.misc.mapping.MappingExtension ovirt.engine.extension.provides = org.ovirt.engine.api.extensions.aaa.Mapping config.mapUser.type = regex config.mapUser.regex.pattern = ^(?<user>[^@]*)$ config.mapUser.regex.replacement = ${user}(a)mydomain.com config.mapUser.regex.mustMatch = false ovirt.engine.aaa.authn.mapping.plugin = mapping In the engine logs I see mapping loaded: ------------------- 2019-04-16 10:35:40,406+02 INFO [org.ovirt.engine.core.extensions.mgr.ExtensionsManager] (ServerService Thread Pool -- 44) [] Loading extension 'mapping' 2019-04-16 10:35:40,420+02 INFO [org.ovirt.engine.core.extensions.mgr.ExtensionsManager] (ServerService Thread Pool -- 44) [] Extension 'mapping' loaded 2019-04-16 10:35:40,424+02 INFO [org.ovirt.engine.core.extensions.mgr.ExtensionsManager] (ServerService Thread Pool -- 44) [] Initializing extension 'internal-authn' 2019-04-16 10:35:40,475+02 INFO [org.ovirt.engine.core.extensions.mgr.ExtensionsManager] (ServerService Thread Pool -- 44) [] Extension 'internal-authn' initialized 2019-04-16 10:35:40,476+02 INFO [org.ovirt.engine.core.extensions.mgr.ExtensionsManager] (ServerService Thread Pool -- 44) [] Initializing extension 'mapping' 2019-04-16 10:35:40,476+02 INFO [org.ovirt.engine.core.extensions.mgr.ExtensionsManager] (ServerService Thread Pool -- 44) [] Extension 'mapping' initialized But still in the logs I see the {user}(a)corp.mydomain.com is not replaced with {user}(a)mydomain.com: ------------------------------------------------------------------------------------------------- 2019-04-16 10:36:27,988+02 WARN [org.ovirt.engineextensions.aaa.ldap.Framework] (default task-3) [] Authentication exception 2019-04-16 10:36:28,231+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-4) [] EVENT_ID: USER_VDC_LOGIN_FAILED(114), User a_user(a)corp.mydomain.com connecting from '192.168.1.11' failed to log in : 'Unable to log in. Verify your login information or contact the system administrator.'. 2019-04-16 10:36:28,235+02 ERROR [org.ovirt.engine.core.sso.servlets.InteractiveAuthServlet] (default task-3) [] Cannot authenticate user 'a_user(a)corp.mydomain.com' connecting from '192.168.1.11': Unable to log in. Verify your login information or contact the system administrator. 2019-04-16 10:40:48,062+02 INFO [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-28) [e479270] Lock Acquired to object 'EngineLock:{exclusiveLocks='[fd6141fe-6a69-49c8-807d-39313cae0756=PROVIDER]', sharedLocks=''}' 2019-04-16 10:40:48,084+02 INFO [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-28) [e479270] Running command: SyncNetworkProviderCommand internal: true. 2019-04-16 10:40:48,270+02 INFO [org.ovirt.engine.extension.aaa.jdbc.core.Tasks] (default task-3) [] (house keeping) deleting failed logins prior to 2019-04-09 08:40:48Z. 2019-04-16 10:40:48,323+02 INFO [org.ovirt.engine.extension.aaa.jdbc.core.Tasks] (default task-3) [] (house keeping) deleting failed logins prior to 2019-04-09 08:40:48Z. Thanks Jarek

1 2

Gluster arbiter volume storage domain - change
by Leo David 16 Apr '19

16 Apr '19

Hi Everyone, I have wrongly configured the main gluster volume ( 12 identical 1tb ssd disks, replica 3 distributed-replicated, across 6 nodes - 2 per node ) with arbiter one. Oviously I am wasting storage space in this scenario with the arbiter bricks, and I would like to convert the volume to non-arbitrated one, so having all the data evenly spreaded across all the disks. Considering the the storage is being used by about 40 vms in production, what would it be the steps, or is there any chance to change the volume type to non-arbitrated on the fly and then rebalance ? Thank you very much !

3 4

Re: Gluster suggestions
by Sahina Bose 16 Apr '19

16 Apr '19

On Tue, Apr 16, 2019 at 2:39 PM Magnus Isaksson <magnus(a)vmar.se> wrote: > > I have 2 hosts per cluster, and i have 2 clusters, 4 hosts (its an Huawei x6000) > > I know oVirt don't support disperse, that's why i run gluster outside of oVirt. > And doing that i get a bit more freedom with setting up gluster. > So what would be an good setup to be able to use as much space as possible and some redundancy with the 4 hosts i have? Even if you run gluster outside of oVirt, you are using the disperse volume as storage domain? For a supported config, you can create a distributed-replica+arbiter gluster volume. Since you have 12 disks, you can use a 5 x 3 (arbiter) setup, where a disk is partitioned to multiple arbiter bricks, something like this (c11,c12, a31, a32 are arbiter bricks) : a1 b1 c11 a2 b2 c12 b3 c13 d1 a31 c2 d2 a32 c3 d3 > > //Magnus > > > ________________________________ > From: Sahina Bose <sabose(a)redhat.com> > Sent: 16 April 2019 10:55 > To: Magnus Isaksson > Cc: users > Subject: Re: [ovirt-users] Gluster suggestions > > On Tue, Apr 16, 2019 at 1:42 PM <magnus(a)vmar.se> wrote: > > > > Hello > > > > I would like some suggestions on what type of solution with Gluster i should use. > > > > I have 4 hosts with 3 disks each, i want to user as much space as possible but also some redundancy, like raid5 or 6 > > The 4 hosts are running oVirt on CentOS 7 > > I have 2 clusters due to some licensing issues, so i cant use ovirts setup of gluster > > I did not quite get this - are you saying you can have only 2 nodes in > one cluster? > > > > > Today i have set it up as follows > > Type: Disperse > > Number of Bricks: 1 x (8 + 4) = 12 > > Disperse volumes are not supported with oVirt. It's either replica 3 > or replica 2 + arbiter. > > > > > So i have 3 bricks per host (one brick per disk) > > > > But this setup is not working very well, as soon as i get some traffic on the volume this start to fail on the ovirt nodes, loosing connection etc. > > > > All hosts are connected via 10G interface > > > > So any suggestions on how i would set this up as best is much appreciated. > > > > Regards > > Magnus Isaksson > > _______________________________________________ > > 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/AIEPMRANHFB7J…

2 1

sysprep properties file
by Florian Rädler 16 Apr '19

16 Apr '19

How can i overwrite the credentials in the sysprep.w10x64 file. I have created a file /etc/ovirt-engine/osinfo.conf.d/10-domainjoin.properties Which contains the following: os.windows_10x64.identification.credentials.domain.value = logondomain os.windows_10x64.identification.credentials.password.value = xxxxxxxx os.windows_10x64.identification.credentials.username.value = username os.windows_10x64.joindomain.value = joindomain If I change the credentials section in /usr/share/ovirt-engine/conf/sysprep/sysprep.w10x64 the domainjoin works. What did I wrong? Thanks for your help. BR Florian ________________________________ Pflichtangaben anzeigen<http://www.deutschebahn.com/pflichtangaben/20190408> Nähere Informationen zur Datenverarbeitung im DB-Konzern finden Sie hier: http://www.deutschebahn.com/de/konzern/datenschutz

1 0

Re: hosted engine does not start
by Sahina Bose 16 Apr '19

16 Apr '19

Can you check if there are any errors in the engine volume's mount logs (/var/logs/glusterfs/rrhev-data-center-mnt-glusterSD-<engine volume>.log) On Tue, Apr 16, 2019 at 2:33 PM Stefan Wolf <shb256(a)gmail.com> wrote: > > Sorry i forgot to wrote, > > > > This is everything I got. > > > > No keyboard input > > > > I ve read to mount the harddrive with losetup and use fsck > > > > [root@kvm360 /]# fdisk -lu /mnt/36663740-576a-4498-b28e-0a402628c6a7/images/50d59094-7f24-4fed-9c4e-d3bb6b42eb6a/38252d8a-49fd-474e-a449-d40b3ef4b7dc > > > > Disk /mnt/36663740-576a-4498-b28e-0a402628c6a7/images/50d59094-7f24-4fed-9c4e-d3bb6b42eb6a/38252d8a-49fd-474e-a449-d40b3ef4b7dc: 53.7 GB, 53687091200 bytes, 104857600 sectors > > Units = Sektoren of 1 * 512 = 512 bytes > > Sector size (logical/physical): 512 bytes / 512 bytes > > I/O size (minimum/optimal): 512 bytes / 512 bytes > > Disk label type: dos > > Disk identifier: 0x000aff89 > > > > Gerät boot. Anfang Ende Blöcke Id System > > /mnt/36663740-576a-4498-b28e-0a402628c6a7/images/50d59094-7f24-4fed-9c4e-d3bb6b42eb6a/38252d8a-49fd-474e-a449-d40b3ef4b7dc1 * 2048 2099199 1048576 83 Linux > > /mnt/36663740-576a-4498-b28e-0a402628c6a7/images/50d59094-7f24-4fed-9c4e-d3bb6b42eb6a/38252d8a-49fd-474e-a449-d40b3ef4b7dc2 2099200 92012543 44956672 8e Linux LVM > > /mnt/36663740-576a-4498-b28e-0a402628c6a7/images/50d59094-7f24-4fed-9c4e-d3bb6b42eb6a/38252d8a-49fd-474e-a449-d40b3ef4b7dc3 92012544 104855551 6421504 83 Linux > > [root@kvm360 /]# losetup -o 2099200 /dev/loop0 /mnt/36663740-576a-4498-b28e-0a402628c6a7/images/50d59094-7f24-4fed-9c4e-d3bb6b42eb6a/38252d8a-49fd-474e-a449-d40b3ef4b7dc > > [root@kvm360 /]# mount /dev/loop0 /test/ > > mount: /dev/loop0 is write-protected, mounting read-only > > mount: wrong fs type, bad option, bad superblock on /dev/loop0, > > missing codepage or helper program, or other error > > > > In some cases useful info is found in syslog - try > > dmesg | tail or so. > > [root@kvm360 /]# > > > > But I suck on mounting partition > > > > -----Ursprüngliche Nachricht----- > Von: Sahina Bose <sabose(a)redhat.com> > Gesendet: Dienstag, 16. April 2019 10:57 > An: Stefan Wolf <shb256(a)gmail.com> > Cc: users <users(a)ovirt.org> > Betreff: Re: [ovirt-users] hosted engine does not start > > > > On Tue, Apr 16, 2019 at 1:07 AM Stefan Wolf <shb256(a)gmail.com> wrote: > > > > > > Hello all, > > > > > > > > > > > > after a powerloss the hosted engine won’t start up anymore. > > > > > > I ‘ve the current ovirt installed. > > > > > > Storage is glusterfs und it is up and running > > > > > > > > > > > > It is trying to start up hosted engine but it does not work, but I can’t see where the problem is. > > > > > > > > > > > > [root@kvm320 ~]# hosted-engine --vm-status > > > > > > > > > > > > > > > > > > --== Host 1 status ==-- > > > > > > > > > > > > conf_on_shared_storage : True > > > > > > Status up-to-date : True > > > > > > Hostname : kvm380.durchhalten.intern > > > > > > Host ID : 1 > > > > > > Engine status : {"reason": "bad vm status", "health": "bad", "vm": "down", "detail": "Down"} > > > > > > Score : 1800 > > > > > > stopped : False > > > > > > Local maintenance : False > > > > > > crc32 : 3ad6d0bd > > > > > > local_conf_timestamp : 14594 > > > > > > Host timestamp : 14594 > > > > > > Extra metadata (valid at timestamp): > > > > > > metadata_parse_version=1 > > > > > > metadata_feature_version=1 > > > > > > timestamp=14594 (Mon Apr 15 21:25:12 2019) > > > > > > host-id=1 > > > > > > score=1800 > > > > > > vm_conf_refresh_time=14594 (Mon Apr 15 21:25:12 2019) > > > > > > conf_on_shared_storage=True > > > > > > maintenance=False > > > > > > state=GlobalMaintenance > > > > > > stopped=False > > > > > > > > > > > > > > > > > > --== Host 2 status ==-- > > > > > > > > > > > > conf_on_shared_storage : True > > > > > > Status up-to-date : True > > > > > > Hostname : kvm320.durchhalten.intern > > > > > > Host ID : 2 > > > > > > Engine status : {"reason": "failed liveliness check", "health": "bad", "vm": "up", "detail": "Up"} > > > > > > Score : 0 > > > > > > stopped : False > > > > > > Local maintenance : False > > > > > > crc32 : e7d4840d > > > > > > local_conf_timestamp : 21500 > > > > > > Host timestamp : 21500 > > > > > > Extra metadata (valid at timestamp): > > > > > > metadata_parse_version=1 > > > > > > metadata_feature_version=1 > > > > > > timestamp=21500 (Mon Apr 15 21:25:22 2019) > > > > > > host-id=2 > > > > > > score=0 > > > > > > vm_conf_refresh_time=21500 (Mon Apr 15 21:25:22 2019) > > > > > > conf_on_shared_storage=True > > > > > > maintenance=False > > > > > > state=ReinitializeFSM > > > > > > stopped=False > > > > > > > > > > > > > > > > > > --== Host 3 status ==-- > > > > > > > > > > > > conf_on_shared_storage : True > > > > > > Status up-to-date : True > > > > > > Hostname : kvm360.durchhalten.intern > > > > > > Host ID : 3 > > > > > > Engine status : {"reason": "vm not running on this host", "health": "bad", "vm": "down", "detail": "unknown"} > > > > > > Score : 1800 > > > > > > stopped : False > > > > > > Local maintenance : False > > > > > > crc32 : cf9221cb > > > > > > local_conf_timestamp : 22121 > > > > > > Host timestamp : 22120 > > > > > > Extra metadata (valid at timestamp): > > > > > > metadata_parse_version=1 > > > > > > metadata_feature_version=1 > > > > > > timestamp=22120 (Mon Apr 15 21:25:18 2019) > > > > > > host-id=3 > > > > > > score=1800 > > > > > > vm_conf_refresh_time=22121 (Mon Apr 15 21:25:18 2019) > > > > > > conf_on_shared_storage=True > > > > > > maintenance=False > > > > > > state=GlobalMaintenance > > > > > > stopped=False > > > > > > > > > > > > [root@kvm320 ~]# virsh -r list > > > > > > Id Name Status > > > > > > ---------------------------------------------------- > > > > > > 6 HostedEngine laufend > > > > > > > > > > > > [root@kvm320 ~]# hosted-engine --console > > > > > > The engine VM is running on this host > > > > > > Verbunden mit der Domain: HostedEngine > > > > > > Escape-Zeichen ist ^] > > > > > > Fehler: Interner Fehler: Zeichengerät <null> kann nicht gefunden > > > warden > > > > > > > > > > > > In engish it should be this > > > > > > > > > > > > [root@mgmt~]# hosted-engine --console > > > The engine VM is running on this host > > > Connected to domain HostedEngine > > > Escape character is ^] > > > error: internal error: cannot find character device > > > > > > > > > > > > This is in the log > > > > > > > > > > > > [root@kvm320 ~]# tail -f /var/log/ovirt-hosted-engine-ha/agent.log > > > > > > MainThread::INFO::2019-04-15 > > > 21:28:33,032::hosted_engine::491::ovirt_hosted_engine_ha.agent.hosted_ > > > engine.HostedEngine::(_monitoring_loop) Current state EngineStarting > > > (score: 1800) > > > > > > MainThread::INFO::2019-04-15 21:28:43,050::states::779::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(consume) VM is powering up.. > > > > > > MainThread::INFO::2019-04-15 > > > 21:28:43,165::hosted_engine::491::ovirt_hosted_engine_ha.agent.hosted_ > > > engine.HostedEngine::(_monitoring_loop) Current state EngineStarting > > > (score: 1800) > > > > > > MainThread::INFO::2019-04-15 21:28:53,183::states::779::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(consume) VM is powering up.. > > > > > > MainThread::INFO::2019-04-15 > > > 21:28:53,300::hosted_engine::491::ovirt_hosted_engine_ha.agent.hosted_ > > > engine.HostedEngine::(_monitoring_loop) Current state EngineStarting > > > (score: 1800) > > > > > > MainThread::INFO::2019-04-15 21:29:03,317::states::779::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(consume) VM is powering up.. > > > > > > MainThread::INFO::2019-04-15 > > > 21:29:03,434::hosted_engine::491::ovirt_hosted_engine_ha.agent.hosted_ > > > engine.HostedEngine::(_monitoring_loop) Current state EngineStarting > > > (score: 1800) > > > > > > MainThread::INFO::2019-04-15 21:29:13,453::states::779::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(consume) VM is powering up.. > > > > > > MainThread::INFO::2019-04-15 > > > 21:29:13,571::states::136::ovirt_hosted_engine_ha.agent.hosted_engine. > > > HostedEngine::(score) Penalizing score by 1600 due to gateway status > > > > > > MainThread::INFO::2019-04-15 > > > 21:29:13,571::hosted_engine::491::ovirt_hosted_engine_ha.agent.hosted_ > > > engine.HostedEngine::(_monitoring_loop) Current state EngineStarting > > > (score: 1800) > > > > > > MainThread::INFO::2019-04-15 21:29:22,589::states::779::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(consume) VM is powering up.. > > > > > > MainThread::INFO::2019-04-15 > > > 21:29:22,712::hosted_engine::491::ovirt_hosted_engine_ha.agent.hosted_ > > > engine.HostedEngine::(_monitoring_loop) Current state EngineStarting > > > (score: 1800) > > > > > > > > > > > > But it is not reachable over the network > > > > > > > > > > > > [root@kvm320 ~]# ping 192.168.200.211 > > > > > > PING 192.168.200.211 (192.168.200.211) 56(84) bytes of data. > > > > > > From 192.168.200.231 icmp_seq=1 Destination Host Unreachable > > > > > > From 192.168.200.231 icmp_seq=2 Destination Host Unreachable > > > > > > From 192.168.200.231 icmp_seq=3 Destination Host Unreachable > > > > > > From 192.168.200.231 icmp_seq=4 Destination Host Unreachable > > > > > > > > > > > > I tried to stop and start the vm again, but it didn’t helped > > > > > > > > > > > > Maybe someone can give me some advice how to get the hosted engine > > > running again > > > > Can you access the VNC console of the Hosted Engine VM and check? > > > > > > > > > > > > > > Thx by stefan > > > > > > _______________________________________________ > > > 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/7PNLN5C4 > > > X6GRVZZ22KJYBHTLOBLUWS27/

1 0

Gluster suggestions
by magnus＠vmar.se 16 Apr '19

16 Apr '19

Hello I would like some suggestions on what type of solution with Gluster i should use. I have 4 hosts with 3 disks each, i want to user as much space as possible but also some redundancy, like raid5 or 6 The 4 hosts are running oVirt on CentOS 7 I have 2 clusters due to some licensing issues, so i cant use ovirts setup of gluster Today i have set it up as follows Type: Disperse Number of Bricks: 1 x (8 + 4) = 12 So i have 3 bricks per host (one brick per disk) But this setup is not working very well, as soon as i get some traffic on the volume this start to fail on the ovirt nodes, loosing connection etc. All hosts are connected via 10G interface So any suggestions on how i would set this up as best is much appreciated. Regards Magnus Isaksson

3 3

hosted engine does not start
by Stefan Wolf 16 Apr '19

16 Apr '19

Hello all, after a powerloss the hosted engine wont start up anymore. I ve the current ovirt installed. Storage is glusterfs und it is up and running It is trying to start up hosted engine but it does not work, but I cant see where the problem is. [root@kvm320 ~]# hosted-engine --vm-status --== Host 1 status ==-- conf_on_shared_storage : True Status up-to-date : True Hostname : kvm380.durchhalten.intern Host ID : 1 Engine status : {"reason": "bad vm status", "health": "bad", "vm": "down", "detail": "Down"} Score : 1800 stopped : False Local maintenance : False crc32 : 3ad6d0bd local_conf_timestamp : 14594 Host timestamp : 14594 Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=14594 (Mon Apr 15 21:25:12 2019) host-id=1 score=1800 vm_conf_refresh_time=14594 (Mon Apr 15 21:25:12 2019) conf_on_shared_storage=True maintenance=False state=GlobalMaintenance stopped=False --== Host 2 status ==-- conf_on_shared_storage : True Status up-to-date : True Hostname : kvm320.durchhalten.intern Host ID : 2 Engine status : {"reason": "failed liveliness check", "health": "bad", "vm": "up", "detail": "Up"} Score : 0 stopped : False Local maintenance : False crc32 : e7d4840d local_conf_timestamp : 21500 Host timestamp : 21500 Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=21500 (Mon Apr 15 21:25:22 2019) host-id=2 score=0 vm_conf_refresh_time=21500 (Mon Apr 15 21:25:22 2019) conf_on_shared_storage=True maintenance=False state=ReinitializeFSM stopped=False --== Host 3 status ==-- conf_on_shared_storage : True Status up-to-date : True Hostname : kvm360.durchhalten.intern Host ID : 3 Engine status : {"reason": "vm not running on this host", "health": "bad", "vm": "down", "detail": "unknown"} Score : 1800 stopped : False Local maintenance : False crc32 : cf9221cb local_conf_timestamp : 22121 Host timestamp : 22120 Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=22120 (Mon Apr 15 21:25:18 2019) host-id=3 score=1800 vm_conf_refresh_time=22121 (Mon Apr 15 21:25:18 2019) conf_on_shared_storage=True maintenance=False state=GlobalMaintenance stopped=False [root@kvm320 ~]# virsh -r list Id Name Status ---------------------------------------------------- 6 HostedEngine laufend [root@kvm320 ~]# hosted-engine --console The engine VM is running on this host Verbunden mit der Domain: HostedEngine Escape-Zeichen ist ^] Fehler: Interner Fehler: Zeichengerät <null> kann nicht gefunden warden In engish it should be this [root@mgmt~]# hosted-engine --console The engine VM is running on this host Connected to domain HostedEngine Escape character is ^] error: internal error: cannot find character device This is in the log [root@kvm320 ~]# tail -f /var/log/ovirt-hosted-engine-ha/agent.log MainThread::INFO::2019-04-15 21:28:33,032::hosted_engine::491::ovirt_hosted_engine_ha.agent.hosted_engine .HostedEngine::(_monitoring_loop) Current state EngineStarting (score: 1800) MainThread::INFO::2019-04-15 21:28:43,050::states::779::ovirt_hosted_engine_ha.agent.hosted_engine.Hosted Engine::(consume) VM is powering up.. MainThread::INFO::2019-04-15 21:28:43,165::hosted_engine::491::ovirt_hosted_engine_ha.agent.hosted_engine .HostedEngine::(_monitoring_loop) Current state EngineStarting (score: 1800) MainThread::INFO::2019-04-15 21:28:53,183::states::779::ovirt_hosted_engine_ha.agent.hosted_engine.Hosted Engine::(consume) VM is powering up.. MainThread::INFO::2019-04-15 21:28:53,300::hosted_engine::491::ovirt_hosted_engine_ha.agent.hosted_engine .HostedEngine::(_monitoring_loop) Current state EngineStarting (score: 1800) MainThread::INFO::2019-04-15 21:29:03,317::states::779::ovirt_hosted_engine_ha.agent.hosted_engine.Hosted Engine::(consume) VM is powering up.. MainThread::INFO::2019-04-15 21:29:03,434::hosted_engine::491::ovirt_hosted_engine_ha.agent.hosted_engine .HostedEngine::(_monitoring_loop) Current state EngineStarting (score: 1800) MainThread::INFO::2019-04-15 21:29:13,453::states::779::ovirt_hosted_engine_ha.agent.hosted_engine.Hosted Engine::(consume) VM is powering up.. MainThread::INFO::2019-04-15 21:29:13,571::states::136::ovirt_hosted_engine_ha.agent.hosted_engine.Hosted Engine::(score) Penalizing score by 1600 due to gateway status MainThread::INFO::2019-04-15 21:29:13,571::hosted_engine::491::ovirt_hosted_engine_ha.agent.hosted_engine .HostedEngine::(_monitoring_loop) Current state EngineStarting (score: 1800) MainThread::INFO::2019-04-15 21:29:22,589::states::779::ovirt_hosted_engine_ha.agent.hosted_engine.Hosted Engine::(consume) VM is powering up.. MainThread::INFO::2019-04-15 21:29:22,712::hosted_engine::491::ovirt_hosted_engine_ha.agent.hosted_engine .HostedEngine::(_monitoring_loop) Current state EngineStarting (score: 1800) But it is not reachable over the network [root@kvm320 ~]# ping 192.168.200.211 PING 192.168.200.211 (192.168.200.211) 56(84) bytes of data. From 192.168.200.231 icmp_seq=1 Destination Host Unreachable From 192.168.200.231 icmp_seq=2 Destination Host Unreachable From 192.168.200.231 icmp_seq=3 Destination Host Unreachable From 192.168.200.231 icmp_seq=4 Destination Host Unreachable I tried to stop and start the vm again, but it didnt helped Maybe someone can give me some advice how to get the hosted engine running again Thx by stefan

2 1