July 2018 - Users - Ovirt List Archives

by Luca 'remix_tj' Lorenzetto

No, The only way you have is to configure cinder to manage ceph pool or in alternative you have to deploy an iscsi gateway, no other ways are available at the moment. So you can't use rbd directly. Luca Il dom 27 mag 2018, 16:54 Leo David <leoalex(a)gmail.com> ha scritto: > Thank you Luca, > At the moment i would try the cinder storage provider, since we already > have a proxmox cluster directly connecting to ceph. The problem is that I > just could not find a straight way to do this. > ie: Specify the ceph monitors and ceph pool to connect to. Can oVirt > directly connect to ceph monitors ? How the configuration should be done if > so ? > Thank you very much ! > > > On Sun, May 27, 2018, 17:20 Luca 'remix_tj' Lorenzetto < > lorenzetto.luca(a)gmail.com> wrote: > >> Hello, >> >> Yes, using cinder or through iscsi gateway. >> >> For a simpler setup i suggest the second option. >> >> Luca >> >> Il dom 27 mag 2018, 16:08 Leo David <leoalex(a)gmail.com> ha scritto: >> >>> Hello everyone, >>> I am new to ovirt and very impressed of its features. I would like to >>> levereage on our existing ceph cluster to provide rbd images for vm hdds, >>> is this possible to achieve ? >>> Thank you very much ! >>> Regards, >>> Leo >>> _______________________________________________ >>> Users mailing list -- users(a)ovirt.org >>> To unsubscribe send an email to users-leave(a)ovirt.org >>> >>

5 years, 7 months

3
3
0 / 0

Fwd: Re: Single node single node SelfHosted Hyperconverged

by Leo David

---------- Forwarded message ---------- From: Leo David <leoalex(a)gmail.com> Date: Tue, Jun 12, 2018 at 7:57 PM Subject: Re: [ovirt-users] Re: Single node single node SelfHosted Hyperconverged To: femi adegoke <ovirt(a)fateknollogee.com> Thank you very much for you response, now it feels I can barelly see the light ! So: multipath -ll 3614187705c01820022b002b00c52f72e dm-1 DELL ,PERC H730P Mini size=931G features='1 queue_if_no_path' hwhandler='0' wp=rw `-+- policy='service-time 0' prio=1 status=active `- 0:2:0:0 sda 8:0 active ready running lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 931G 0 disk ├─sda1 8:1 0 1G 0 part ├─sda2 8:2 0 930G 0 part └─3614187705c01820022b002b00c52f72e 253:1 0 931G 0 mpath ├─3614187705c01820022b002b00c52f72e1 253:3 0 1G 0 part /boot └─3614187705c01820022b002b00c52f72e2 253:4 0 930G 0 part ├─onn-pool00_tmeta 253:6 0 1G 0 lvm │ └─onn-pool00-tpool 253:8 0 825.2G 0 lvm │ ├─onn-ovirt--node--ng--4.2.3.1--0.20180530.0+1 253:9 0 798.2G 0 lvm / │ ├─onn-pool00 253:12 0 825.2G 0 lvm │ ├─onn-var_log_audit 253:13 0 2G 0 lvm /var/log/audit │ ├─onn-var_log 253:14 0 8G 0 lvm /var/log │ ├─onn-var 253:15 0 15G 0 lvm /var │ ├─onn-tmp 253:16 0 1G 0 lvm /tmp │ ├─onn-home 253:17 0 1G 0 lvm /home │ └─onn-var_crash 253:20 0 10G 0 lvm /var/crash ├─onn-pool00_tdata 253:7 0 825.2G 0 lvm │ └─onn-pool00-tpool 253:8 0 825.2G 0 lvm │ ├─onn-ovirt--node--ng--4.2.3.1--0.20180530.0+1 253:9 0 798.2G 0 lvm / │ ├─onn-pool00 253:12 0 825.2G 0 lvm │ ├─onn-var_log_audit 253:13 0 2G 0 lvm /var/log/audit │ ├─onn-var_log 253:14 0 8G 0 lvm /var/log │ ├─onn-var 253:15 0 15G 0 lvm /var │ ├─onn-tmp 253:16 0 1G 0 lvm /tmp │ ├─onn-home 253:17 0 1G 0 lvm /home │ └─onn-var_crash 253:20 0 10G 0 lvm /var/crash └─onn-swap 253:10 0 4G 0 lvm [SWAP] sdb 8:16 0 931G 0 disk └─sdb1 8:17 0 931G 0 part sdc 8:32 0 4.6T 0 disk └─sdc1 8:33 0 4.6T 0 part nvme0n1 259:0 0 1.1T 0 disk So the multipath "3614187705c01820022b002b00c52f72e" that was shown in the error is actually the root filesystem, which was created at node installation ( from iso ). Is this mpath ok that is activated on sda ? What should I do in this situation ? Thank you ? On Tue, Jun 12, 2018 at 5:38 PM, femi adegoke <ovirt(a)fateknollogee.com> wrote: > Are your disks "multipathing"? > > What's your output if you run the command multipath -ll > > For comparison sake, here is my gdeploy.conf (used for a single host > gluster install) - lv1 was changed to 62gb > **Credit for that pastebin to Squeakz on the IRC channel > https://pastebin.com/LTRQ78aJ > _______________________________________________ > 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/communit > y/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archiv > es/list/users(a)ovirt.org/message/EEIE4PWUFCXHHTT6PGP2EPFQXIWL6H5P/ > -- Best regards, Leo David -- Best regards, Leo David

5 years, 8 months

3
16
0 / 0

vacuumdb: could not connect to database ovirt_engine_history

by emanuel.santosvarina＠mahle.com

..trying to update from 4.2.3 to 4.2.4 engine-setup fails with the following error: --snip 2018-06-28 16:26:45,507+0200 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine_dwh.db.vacuum plugin.execute:926 execute-output: ['/usr/share/ovirt-engine-dwh/bin/dwh-vacuum.sh', '-f', '-v'] stderr: vacuumdb: could not connect to database ovirt_engine_history: FATAL: password authentication failed for user "ovirt_engine_history" 2018-06-28 16:26:45,507+0200 DEBUG otopi.context context._executeMethod:143 method exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/context.py", line 133, in _executeMethod method['method']() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine-dwh/db/vacuum.py", line 126, in _vacuum self.execute(args=args) File "/usr/lib/python2.7/site-packages/otopi/plugin.py", line 931, in execute command=args[0], RuntimeError: Command '/usr/share/ovirt-engine-dwh/bin/dwh-vacuum.sh' failed to execute 2018-06-28 16:26:45,508+0200 ERROR otopi.context context._executeMethod:152 Failed to execute stage 'Misc configuration': Command '/usr/share/ovirt-engine-dwh/bin/dwh-vacuum.sh' failed to execute 2018-06-28 16:26:45,508+0200 DEBUG otopi.transaction transaction.abort:119 aborting 'Yum Transaction' --snap Any ideas? Thank You, Ema

5 years, 8 months

5
8
0 / 0

Network issues with oVirt 4.2 and cloud-init

by Berger, Sandy

--_000_DM5PR05MB316161E1C7E2EB8EA09A76A0D5D40DM5PR05MB3161namp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable We're using cloud-init to customize VMs built from a template. We're using = static IPV4 settings so we're specifying an IP address, subnet mask, and ga= teway. There is apparently a bug in the current version of cloud-init shipp= ing as part of CentOS 7.4 (https://bugzilla.redhat.com/show_bug.cgi?id=3D14= 92726) that fails to set the gateway properly. In the description of the bu= g, it says it is fixed in RHEL 7.5 but also says one can use https://people= .redhat.com/rmccabe/cloud-init/cloud-init-0.7.9-20.el7.x86_64.rpm which is = what we're doing. When the new VM first boots, the 3 IPv4 settings are all set correctly. Reb= oots of the VM maintain the settings properly. But, if the VM is shut down = and started again via the oVirt GUI, all of the IPV4 settings on the eth0 v= irtual NIC are lost and the /etc/sysconfig/network-scripts/ifcfg-eth0 shows= that the NIC is now set up for DHCP. Are we doing something incorrectly? Sandy Berger IT - Infrastructure Engineer II Quad/Graphics Performance through Innovation Sussex, Wisconsin 414.566.2123 phone 414.566.4010/2123 pager/PIN sandy.berger(a)qg.com<mailto:sandy.berger@qg.com> www.QG.com<http://www.qg.com/> Follow Us: Facebook<http://www.qg.com/social1> | Twitter<http://www.qg.com/= social2> | LinkedIn<http://www.qg.com/social3> | YouTube<http://www.qg.com/= social4> --_000_DM5PR05MB316161E1C7E2EB8EA09A76A0D5D40DM5PR05MB3161namp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:= //www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"= > <meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72"> <div class=3D"WordSection1"> We’re using cloud-init to customize VMs built = from a template. We’re using static IPV4 settings so we’re spec= ifying an IP address, subnet mask, and gateway. There is apparently a bug i= n the current version of cloud-init shipping as part of CentOS 7.4 (<a href=3D"https://bugzilla.redhat.com/show_bug.cgi?id=3D14= 92726">https://bugzilla.redhat.com/show_bug.cgi?id=3D1492726</a>) that fail= s to set the gateway properly. In the description of the bug, it says it is= fixed in RHEL 7.5 but also says one can use <a href=3D"https://people.redhat.com/rmccabe/cloud-init/cloud-init-0.7= .9-20.el7.x86_64.rpm"> https://people.redhat.com/rmccabe/cloud-init/cloud-init-0.7.9-20.el7.x86_64= .rpm</a> which is what we’re doing.<o:p></o:p> <o:p> </o:p> When the new VM first boots, the 3 IPv4 settings are= all set correctly. Reboots of the VM maintain the settings properly. But, = if the VM is shut down and started again via the oVirt GUI, all of the IPV4= settings on the eth0 virtual NIC are lost and the /etc/sysconfig/network-scripts/ifcfg-eth0 shows that the = NIC is now set up for DHCP.<o:p></o:p> <o:p> </o:p> Are we doing something incorrectly?<o:p></o:p> <o:p> </o:p> Sandy Berger <o:p></o:p> IT – Infrastructure Engineer I= I<o:p></o:p>  <o:p></o:p> Quad/Graphics<o:p><= /o:p> Performance&nb= sp;through Innovation<o:= p></o:p>  <o:p></o:p></= span> Sussex, Wisconsin<o= :p></o:p> 414.566.2123 phone<= o:p></o:p> 414.566.4010/2123 pager/PIN<span= style=3D"font-size:10.5pt;font-family:"Arial",sans-serif;color:#= 444444"><o:p></o:p>  <= /span><o:p></o:p> <a href=3D"mailto:sandy.berger@qg.com"><s= pan style=3D"color:blue">sandy.berger(a)qg.com</a><o:p></o:p> <a href=3D"http://www.qg.com/">www.QG.com</a><o:p></o:p></span= > <o:p> </o:p> </div> Follow Us: <a href=3D"http://www.qg.com/social1">Facebook</a> | <a href=3D"= http://www.qg.com/social2"> Twitter</a> | <a href=3D"http://www.qg.com/social3">LinkedIn</a> | <a href= =3D"http://www.qg.com/social4"> YouTube</a> </body> </html> --_000_DM5PR05MB316161E1C7E2EB8EA09A76A0D5D40DM5PR05MB3161namp_--

5 years, 8 months

4
5
0 / 0

oVirt node 4.2.x - custom multipath.conf and external storage availability

by Roberto Nunin

HI all How can I provide to my oVirt hosts a custom multipath.conf, considering that we are using shared/mirrored FC storage from HPE 3PAR with high availability of provided LUNs, using peer-persistance feature ? To configure correctly this require a custom multipath.conf is required. How I can avoid it will be overwritten during upgrades ? Second topic: Is ALUA feature supported also in oVirt nodes, like for standard RHEL 6/7 and/or CentOS 6/7 ? I was digging for a while into user's digest, but not able to find focused informations. This is the feature needed by peer-persistance, allowing two different volumes to be masked toward a given host with the same WWN and LUN number. Thanks in advance -- Roberto

5 years, 8 months

2
2
0 / 0

Drive letter / scsi id not consistent

by Nathan March

Hi, Managing disks in the ovirt gui seems completely error prone since the GUI ordering does not seem to be used in any practical way. The scsi ID's are not exposed via the GUI either, so if you have 2 drives of the same size on NFS there's no way to identify which is which without resorting to dumping the xml. I see in the xml that the target dev is correct and matches up with the GUI's drive order, but the scsi unit seems to be generated based on the order of last activated: <disk type='file' device='disk' snapshot='no'> <driver name='qemu' type='raw' cache='none' error_policy='stop' io='threads'/> <source file='/rhev/data-center/mnt/10.1.32.10:_sas01/2060a19f-f26c-4dba-a559-83541a4d0c7a/images/b622cde9-ffc4-487b-8038-f7cb7fbc00a1/7240b4b2-5ab1-40ab-99bb-09c69fd835f6'/> <backingStore/> <target dev='sda' bus='scsi'/> <serial>b622cde9-ffc4-487b-8038-f7cb7fbc00a1</serial> <boot order='1'/> <alias name='ua-b622cde9-ffc4-487b-8038-f7cb7fbc00a1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <disk type='file' device='disk' snapshot='no'> <driver name='qemu' type='raw' cache='none' error_policy='stop' io='threads'/> <source file='/rhev/data-center/mnt/10.1.32.10:_sas01/2060a19f-f26c-4dba-a559-83541a4d0c7a/images/86765f60-4240-44f4-b437-f22b2cc3df1a/482a363e-461a-4f37-876c-43ceb529a93a'/> <backingStore/> <target dev='sdb' bus='scsi'/> <serial>86765f60-4240-44f4-b437-f22b2cc3df1a</serial> <alias name='ua-86765f60-4240-44f4-b437-f22b2cc3df1a'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='disk' snapshot='no'> <driver name='qemu' type='raw' cache='none' error_policy='stop' io='threads'/> <source file='/rhev/data-center/mnt/10.1.32.10:_sas01/2060a19f-f26c-4dba-a559-83541a4d0c7a/images/0b020d24-3dea-4be7-931a-9c25ccfeec48/7e3957ff-a3bf-4080-a7b6-ddad7f63a299'/> <backingStore/> <target dev='sdc' bus='scsi'/> <serial>0b020d24-3dea-4be7-931a-9c25ccfeec48</serial> <alias name='scsi0-0-0-3'/> <address type='drive' controller='0' bus='0' target='0' unit='3'/> </disk> After deactivating the other 2 disks and rebooting the machine, sda has now become unit 3: <target dev='sda' bus='scsi'/> <serial>b622cde9-ffc4-487b-8038-f7cb7fbc00a1</serial> <boot order='1'/> <alias name='ua-b622cde9-ffc4-487b-8038-f7cb7fbc00a1'/> <address type='drive' controller='0' bus='0' target='0' unit='3'/> and then I shutdown, activated the extra 2 drives, booted it back up but now I'm still on unit 3: <disk type='file' device='disk' snapshot='no'> <driver name='qemu' type='raw' cache='none' error_policy='stop' io='threads'/> <source file='/rhev/data-center/mnt/10.1.32.10:_sas01/2060a19f-f26c-4dba-a559-83541a4d0c7a/images/b622cde9-ffc4-487b-8038-f7cb7fbc00a1/7240b4b2-5ab1-40ab-99bb-09c69fd835f6'/> <backingStore/> <target dev='sda' bus='scsi'/> <serial>b622cde9-ffc4-487b-8038-f7cb7fbc00a1</serial> <boot order='1'/> <alias name='ua-b622cde9-ffc4-487b-8038-f7cb7fbc00a1'/> <address type='drive' controller='0' bus='0' target='0' unit='3'/> </disk> <disk type='file' device='disk' snapshot='no'> <driver name='qemu' type='raw' cache='none' error_policy='stop' io='threads'/> <source file='/rhev/data-center/mnt/10.1.32.10:_sas01/2060a19f-f26c-4dba-a559-83541a4d0c7a/images/86765f60-4240-44f4-b437-f22b2cc3df1a/482a363e-461a-4f37-876c-43ceb529a93a'/> <backingStore/> <target dev='sdb' bus='scsi'/> <serial>86765f60-4240-44f4-b437-f22b2cc3df1a</serial> <alias name='ua-86765f60-4240-44f4-b437-f22b2cc3df1a'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='disk' snapshot='no'> <driver name='qemu' type='raw' cache='none' error_policy='stop' io='threads'/> <source file='/rhev/data-center/mnt/10.1.32.10:_sas01/2060a19f-f26c-4dba-a559-83541a4d0c7a/images/0b020d24-3dea-4be7-931a-9c25ccfeec48/7e3957ff-a3bf-4080-a7b6-ddad7f63a299'/> <backingStore/> <target dev='sdc' bus='scsi'/> <serial>0b020d24-3dea-4be7-931a-9c25ccfeec48</serial> <alias name='ua-0b020d24-3dea-4be7-931a-9c25ccfeec48'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> I managed to get things into the correct state by shutting down the VM, deactivating all the disks, then activating them in the order I want them to show up. This sets the correct order of unit 0 for sda, unit 1 for sdb, unit 2 for sdc. Is there some way to make ovirt treat this in a sane way and always expose the scsi devices in the same order as the GUI (and the "target dev" field)? Cheers! Nathan

5 years, 8 months

2
2
0 / 0

better understand ovirt-engine functions

by stuartk＠alleninstitute.org

I've been reading through documentation https://www.ovirt.org/documentation/architecture/architecture/ https://www.ovirt.org/documentation/self-hosted/Self-Hosted_Engine_Guide/ But am struggling still to understand the role ovirt-engine plays. Would anyone have recommends for additional reads? The problem I'm tackling currently looks like this: - We have (2) oVirt Data Centers, each populated by a single Cluster. The Data Centers are physically & network-wise 'distant' from one another - hosted-engine runs on (3) of the (4) Hosts in Data Center A / Cluster A. hosted-engine does not run on Data Center B / Cluster B - When we disrupt network connectivity around Cluster A (yes, that's Cluster *A*), Hosts in Cluster B crash (requiring a power cycle) and Guests in Cluster B get stopped and paused I'm struggling to understand why mussing with Cluster A affects Cluster B. From pcaps, I can see plenty of TLS traffic from Cluster A's Hosts -- presumably from ovirt-engine running on Cluster A -- exchanged with Cluster B. So, during my last maintenance window, I put hosted-engine into maintenance mode ... but Hosts/VMs in Cluster B were still affected. Where do I go to better understand what ovirt-engine does when it is 'managing' Hosts & VMs? --sk

5 years, 8 months

3
6
0 / 0

MoM - Not working ? How to use it ?

by jeanbaptiste＠nfrance.com

Hello, I'm trying to test Memory balloon useful functionality, but l'm unable to make it work successfuly. Firstly, I enable the MOM on my Cluster: Memory Balloon Enable Memory Balloon Optimization Secondly, I configure a VM virtual machine like this: On system tab: Memory Size : 28672 MB Maximum memory : 28672 MB On Ressource allocation tab: Memory Allocation: Physical Memory Guaranteed : 2048 MB Memory Balloon Device: Enabled Thirdly, I test 1- I boot the VM. After boot VM consume 200MB 2- I lauch perl program which consume 26GB. 3- During this, Host RAM usage is near 90% 4- I stop the perl program, and on guest side, RAM usage drop down to 200Mo 5- On host side, RAM usage keep to 24 - 26GB. I wait some time to show if the qemu-vm process drop is host-ram-usage. Ram usage keep to 24GB. 6- I try to launch another VM like the first one (but with 8GB RAM and 2GB Guaranteed) , on the host (to "force" Mom ?) but I'm unable to lauch it, Host free mem is insufficient I change MoM log to debug to show something: 2018-07-31 11:49:31,887 - mom.RPCServer - INFO - ping() 2018-07-31 11:49:31,888 - mom.RPCServer - INFO - getStatistics() 2018-07-31 11:49:31,888 - mom.Monitor - DEBUG - Field 'mem_free' not known. Ignoring. 2018-07-31 11:49:43,313 - mom.VdsmRpcBase - DEBUG - VM List: [u'9632443f-d302-43f7-a279-778e64ee98f4'] 2018-07-31 11:49:43,465 - mom.VdsmRpcBase - DEBUG - Memory stats: {'swap_out': 0, 'swap_usage': 0, 'mem_free': 28221020, 'major_fault': 0, 'swap_in': 0, 'swap_total': 0, 'mem_available': 28650472, 'minor_fault': 99, 'mem_unused': 28221020} 2018-07-31 11:49:43,468 - mom.Monitor - DEBUG - Collector <mom.Collectors.GuestIoTuneOptional.GuestIoTuneOptional instance at 0x167de18> did not return any data 2018-07-31 11:49:43,931 - mom.RPCServer - INFO - ping() 2018-07-31 11:49:43,932 - mom.RPCServer - INFO - getStatistics() 2018-07-31 11:49:43,932 - mom.Monitor - DEBUG - Field 'mem_free' not known. Ignoring. 2018-07-31 11:49:44,258 - mom.Monitor - DEBUG - Field 'mem_free' not known. Ignoring. 2018-07-31 11:49:44,284 - mom.Evaluator - DEBUG - debug: ('No shared pages, setting ksm_merge_across_nodes to', 1) 2018-07-31 11:49:44,286 - mom.Evaluator - DEBUG - debug: ('entry: apply_NUMA_policy',) 2018-07-31 11:49:44,286 - mom.Evaluator - DEBUG - debug: (1, '=ksm_merge_across_nodes ACTUAL from kernel') 2018-07-31 11:49:44,286 - mom.Evaluator - DEBUG - debug: (1, '=ksmMergeAcrossNodes REQUIRED from oVirt-engine') 2018-07-31 11:49:44,289 - mom.Evaluator - DEBUG - debug: ('exit: apply_NUMA_policy return_value = ', 0) 2018-07-31 11:49:44,310 - mom.Policy - DEBUG - Results: [0, 1, 1, 1, 0, 1, 1, 0.2, 0.05, 0.2, 0.05, 0.0025, 'change_big_enough', 'shrink_guest', 'grow_guest', 0.22506353015141964, 'balloon_logic', [0], 'guest_qos', [0], 300, -50, 64, 1250, 10, 0.2, 'change_npages', 'apply_NUMA_policy', 6550590.4, 30058208, None, 0, 0, None, -1, 100000, 'check_and_set_quota', 'reset_quota_and_period', [None], 0, 'set_io_limits', 'reset_io_limits', [0]] Does I miss something ? MoM behavior ? Thanks for all !

5 years, 8 months

3
9
0 / 0

Pool

by suporte＠logicworks.pt

I create a pool with 3 VMs, V. 4.2. Now I want to delete just one VM of that pool. Is that possible? Thanks Josá -- Jose Ferradeira http://www.logicworks.pt

5 years, 8 months

3
11
0 / 0

Unable to revive host after a reboot

by Julius Schwartzenberg

Hi, I recently had to shutdown my oVirt system which contains both the engine and the host. After it came back up, the host was not able to initialize anymore from the oVirt UI. First it kept getting stuck in a loop with setting "ExecutingStarted: Jul 30, 2018, 9:06:21 AMSetting Host pc331 to Non-Operational mode." This was being repeated over and over again. It also gave this error: Host pc331 does not comply with the cluster Default networks, the following networks are missing on host: 'ovirtmgmt' Even though I am using that interface (ovirtmgmt) to access the system and 'ip addr show' shows that it's set up properly. I tried some more things, including upgrading the host, When I do that, the status changes to 'Installing' and later to 'Install Failed'. Here are the engine.log, vdsm.log and ovirt-host-deploy*.log: https://drive.google.com/open?id=13vIUDVjPynmAK0pnFRLabDfUlG1lmkpI https://drive.google.com/open?id=10Zm2dDpxM2k5A2bEs_l6gOv_yWv4cjlN https://drive.google.com/open?id=1AieWMzRuA0gZj3x5yDH1AGnsT2E3VtOM Any idea what is going wrong (what I'm doing wrong) and how to solve it? Thanks in advance! Best regards, Julius

5 years, 8 months

5
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Users July 2018