- Users - oVirt List Archives

Re: Cannot enable maintenance mode
by Martin Perina 07 Nov '19

07 Nov '19

Hi Bruno, how have you rebooted the host? Have you used Stop/Start/Restart functions from Power Management menu in host detail in webadmin? Regards, Martin On Tue, Nov 5, 2019 at 2:29 AM Bruno Martins <bruno.o.martins(a)gfi.world> wrote: > Hi Lukas, > > Thanks for your message! > > In my cluster, I have all the VM's running under "HOST2". > The issue I'm having is that I can't enable maintenance mode on "HOST1", > in order to re-add it to oVirt Manager (SSL certificate replacement stuff). > I did it successfully on "HOST2", but the other one seems to ignore my > actions, with that message in the logs... > > Cheers, > > Bruno > > From: Lukas Svaty <lsvaty(a)redhat.com> > Sent: 16 de outubro de 2019 10:49 > To: Bruno Martins <bruno.o.martins(a)gfi.world> > Cc: users(a)ovirt.org > Subject: Re: [ovirt-users] Re: Cannot enable maintenance mode > > Did you > > "Consider manual intervention" > > such as > > "stopping" or "migrating Vms" > > which are running on that host? > > If you are trying to put host to maintenance, it will migrate all the VMs > somewhere else, thus... you might have problem with migrations (try to > migrate them to other destination host) or power them off. > > On Wed, Oct 16, 2019 at 9:15 AM Bruno Martins <mailto: > bruno.o.martins(a)gfi.world> wrote: > Hey guys, > > There are really no options left here? Is there something else I should > check? > > Thank you! > > -----Original Message----- > From: Bruno Martins <mailto:bruno.o.martins@gfi.world> > Sent: 3 de outubro de 2019 22:41 > To: Benny Zlotnik <mailto:bzlotnik@redhat.com> > Cc: mailto:users@ovirt.org > Subject: [ovirt-users] Re: Cannot enable maintenance mode > > Hello Benny, > > I did. No luck, still... > > Cheers! > > -----Original Message----- > From: Benny Zlotnik <mailto:bzlotnik@redhat.com> > Sent: 2 de outubro de 2019 19:19 > To: Bruno Martins <mailto:bruno.o.martins@gfi.world> > Cc: mailto:users@ovirt.org > Subject: Re: [ovirt-users] Re: Cannot enable maintenance mode > > Did you try the "Confirm Host has been rebooted" button? > > On Wed, Oct 2, 2019 at 9:17 PM Bruno Martins <mailto: > bruno.o.martins(a)gfi.world> wrote: > > > > Hello guys, > > > > No ideas for this issue? > > > > Thanks for your cooperation! > > > > Kind regards, > > > > -----Original Message----- > > From: Bruno Martins <mailto:bruno.o.martins@gfi.world> > > Sent: 29 de setembro de 2019 16:16 > > To: mailto:users@ovirt.org > > Subject: [ovirt-users] Cannot enable maintenance mode > > > > Hello guys, > > > > I am being unable to put a host from a two nodes cluster into > maintenance mode in order to remove it from the cluster afterwards. > > > > This is what I see in engine.log: > > > > 2019-09-27 16:20:58,364 INFO > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (org.ovirt.thread.pool-6-thread-45) [4cc251c9] Correlation ID: 4cc251c9, > Job ID: 65731fbb-db34-49a9-ab56-9fba59bc0ee0, Call Stack: null, Custom > Event ID: -1, Message: Host CentOS-H1 cannot change into maintenance mode - > not all Vms have been migrated successfully. Consider manual intervention: > stopping/migrating Vms: Non interactive user (User: admin). > > > > Host has been rebooted multiple times. vdsClient shows no VM's running. > > > > What else can I do? > > > > Kind regards, > > > > Bruno Martins > > _______________________________________________ > > Users mailing list -- mailto:users@ovirt.org To unsubscribe send an > > email to mailto:users-leave@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/X5FJWFW7 > > GXNW6YWRPFWOKA6VU3RH4WD3/ > > _______________________________________________ > > Users mailing list -- mailto:users@ovirt.org To unsubscribe send an > > email to mailto:users-leave@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/DD5DW6KK > > OOHGL3WFEKIIIS57BN3VWMAQ/ > > _______________________________________________ > Users mailing list -- mailto:users@ovirt.org To unsubscribe send an email > to mailto:users-leave@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/64GZQKZA7LX7K… > _______________________________________________ > Users mailing list -- mailto:users@ovirt.org To unsubscribe send an email > to mailto:users-leave@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/JJPEC7RDG3AUS… > > > -- > LUKAS SVATY > RHV QE > _______________________________________________ > 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/YZB2L7MK6SGQI… > -- Martin Perina Manager, Software Engineering Red Hat Czech s.r.o.

2 1

How to pass parameters between VDSM Hooks domxml in single run
by Vrgotic, Marko 06 Nov '19

06 Nov '19

Dear oVIrt, A while ago we discussed on ways to change/update content of parameters of domxml in certain action. As I mentioned before, we have added the VDSMHook 60_nsupdate which removes the DNS record entries when a VM is destroyed: … domxml = hooking.read_domxml() name = domxml.getElementsByTagName('name')[0] name = " ".join(name.nodeValue for name in name.childNodes if name.nodeType == name.TEXT_NODE) nsupdate_commands = """server {server_ip} update delete {vm_name}.example.com a update delete {vm_name}. example.com aaaa update delete {vm_name}. example.com txt send """.format(server_ip="172.16.1.10", vm_name=name) … The goal: However, we did not want to execute remove dns records when VM is only migrated. Since its considered a “destroy” action we took following approach. * In state “before_vm_migrate_source add hook which will write flag “is_migration” to domxml * Once VM is scheduled for migration, this hook should add the flag “is_migration” to domxml * Once 60_nsupdate is triggered, it will check for the flag and if there, skip executing dns record action, but only remove the flag “is_migration” from domxml of the VM … domxml = hooking.read_domxml() migration = domxml.createElement("is_migration") domxml.getElementsByTagName("domain")[0].appendChild(migration) logging.info("domxml_updated {}".format(domxml.toprettyxml())) hooking.write_domxml(domxml) … When executing first time, we observed that flag “ <name>hookiesvm</name> <uuid>fcfa66cb-b251-43a3-8e2b-f33b3024a749</uuid> <metadata xmlns:ns0="http://ovirt.org/vm/tune/1.0" xmlns:ns1="http://ovirt.org/vm/1.0"> <ns0:qos/> <ovirt-vm:vm xmlns:ovirt-vm="http://ovirt.org/vm/1.0"> <ovirt-vm:clusterVersion>4.3</ovirt-vm:clusterVersion> <ovirt-vm:destroy_on_reboot type="bool">False</ovirt-vm:destroy_on_reboot> <ovirt-vm:launchPaused>false</ovirt-vm:launchPaused> <ovirt-vm:memGuaranteedSize type="int">1024</ovirt-vm:memGuaranteedSize> <ovirt-vm:minGuaranteedMemoryMb type="int">1024</ovirt-vm:minGuaranteedMemoryMb> ...skipping... <address bus="0x00" domain="0x0000" function="0x0" slot="0x09" type="pci"/> </rng> </devices> <seclabel model="selinux" relabel="yes" type="dynamic"> <label>system_u:system_r:svirt_t:s0:c169,c575</label> <imagelabel>system_u:object_r:svirt_image_t:s0:c169,c575</imagelabel> </seclabel> <seclabel model="dac" relabel="yes" type="dynamic"> <label>+107:+107</label> <imagelabel>+107:+107</imagelabel> </seclabel> <is_migration/> </domain> is added to domxml, but was present once 60_nsupdate hook was executed. The question: How do we make sure that, when domxml is updated, that the update is visible/usable by following hook, in single run? How to pass these changes between hooks? Kindly awaiting your reply. — — — Met vriendelijke groet / Kind regards, Marko Vrgotic

2 6

Ansible setup host network fails on comparing sorted dictionaries
by Vrgotic, Marko 06 Nov '19

06 Nov '19

Dear oVirt, While deploying ovirt_infra , the role oivrt.networks fails on Setup Host Networks, with following error: TypeError: '<' not supported between instances of 'dict' and 'dict' Full output: TASK [ovirt.infra/roles/ovirt.networks : Setup host networks] ****************************************************************************************************************** The full traceback is: Traceback (most recent call last): File "/var/folders/40/w2c8fp151854mddz_4n3czwm0000gn/T/ansible_ovirt_host_network_payload_s0fx52mx/__main__.py", line 396, in main (nic is None or host_networks_module.has_update(nics_service.service(nic.id))) File "/var/folders/40/w2c8fp151854mddz_4n3czwm0000gn/T/ansible_ovirt_host_network_payload_s0fx52mx/__main__.py", line 289, in has_update update = self.__compare_options(get_bond_options(bond.get('mode'), bond.get('options')), getattr(nic.bonding, 'options', [])) File "/var/folders/40/w2c8fp151854mddz_4n3czwm0000gn/T/ansible_ovirt_host_network_payload_s0fx52mx/__main__.py", line 247, in __compare_options return sorted(get_dict_of_struct(opt) for opt in new_options) != sorted(get_dict_of_struct(opt) for opt in old_options) TypeError: '<' not supported between instances of 'dict' and 'dict' failed: [localhost] (item={'name': 'ovirt-staging-hv-02.avinity.tv', 'check': True, 'save': True, 'bond': {'name': 'bond28', 'mode': 4, 'interfaces': ['p2p1', 'p2p2']}, 'networks': [{'name': 'backbone', 'boot_protocol': 'static', 'address': '172.17.28.212', 'netmask': '255.255.255.0', 'version': 'v4'}]}) => { "ansible_loop_var": "item", "changed": false, "invocation": { "module_args": { "bond": { "interfaces": [ "p2p1", "p2p2" ], "mode": 4, "name": "bond28" }, "check": true, "fetch_nested": false, "interface": null, "labels": null, "name": "ovirt-staging-hv-02.avinity.tv", "nested_attributes": [], "networks": [ { "address": "172.17.28.212", "boot_protocol": "static", "name": "backbone", "netmask": "255.255.255.0", "version": "v4" } ], "poll_interval": 3, "save": true, "state": "present", "sync_networks": false, "timeout": 180, "wait": true } }, "item": { "bond": { "interfaces": [ "p2p1", "p2p2" ], "mode": 4, "name": "bond28" }, "check": true, "name": "ovirt-staging-hv-02.avinity.tv", "networks": [ { "address": "172.17.28.212", "boot_protocol": "static", "name": "backbone", "netmask": "255.255.255.0", "version": "v4" } ], "save": true }, "msg": "'<' not supported between instances of 'dict' and 'dict'" } Read vars_file 'vars/engine_vars.yml' Read vars_file 'vars/secrets.yml' Read vars_file 'vars/ovirt_infra_vars.yml' Looking further into ovirt_host_network.py I found that issue is reported after following is executed: return sorted(get_dict_of_struct(opt) for opt in new_options) != sorted(get_dict_of_struct(opt) for opt in old_options) It seemed to be failing due to not getting the key value to sort the dicts, so I added sorting based on name, to test, and it worked in single test run: return sorted((get_dict_of_struct(opt) for opt in new_options), key=lambda x: x["name"]) != sorted((get_dict_of_struct(opt) for opt in old_options), key=lambda x: x["name"]) After rerun of the play, with changes above: TASK [ovirt.infra/roles/ovirt.networks : Setup host networks] ****************************************************************************************************************** task path: /Users/mvrgotic/Git/ovirt-engineering/roles/ovirt.infra/roles/ovirt.networks/tasks/main.yml:25 Using module file /Users/mvrgotic/.local/share/virtualenvs/ovirt-engineering-JaxzXThh/lib/python3.7/site-packages/ansible/modules/cloud/ovirt/ovirt_host_network.py Pipelining is enabled. <127.0.0.1> ESTABLISH LOCAL CONNECTION FOR USER: mvrgotic <127.0.0.1> EXEC /bin/sh -c '/Users/mvrgotic/.local/share/virtualenvs/ovirt-engineering-JaxzXThh/bin/python3 && sleep 0' changed: [localhost] => (item={'name': 'ovirt-staging-hv-02.avinity.tv', 'check': True, 'save': True, 'bond': {'name': 'bond28', 'mode': 4, 'interfaces': ['p2p1', 'p2p2']}, 'networks': [{'name': 'backbone', 'boot_protocol': 'static', 'address': '172.17.28.212', 'netmask': '255.255.255.0', 'version': 'v4'}]}) => { "ansible_loop_var": "item", "changed": true, "host_nic": { "ad_aggregator_id": 6, "bonding": { "ad_partner_mac": { "address": "44:31:92:7c:b3:11" }, "options": [ { "name": "mode", "type": "Dynamic link aggregation (802.3ad)", "value": "4" }, { "name": "xmit_hash_policy", "value": "2" } ], "slaves": [ { "href": "/ovirt-engine/api/hosts/aa1f7a65-a867-436a-9a7f-264068f4bdea/nics/01703220-570c-44f5-9729-6717ceead304", "id": "01703220-570c-44f5-9729-6717ceead304" }, { "href": "/ovirt-engine/api/hosts/aa1f7a65-a867-436a-9a7f-264068f4bdea/nics/e879c1c6-065d-4742-b282-fcdb477f95a7", "id": "e879c1c6-065d-4742-b282-fcdb477f95a7" } ] }, "boot_protocol": "static", "bridged": false, "custom_configuration": false, "host": { "href": "/ovirt-engine/api/hosts/aa1f7a65-a867-436a-9a7f-264068f4bdea", "id": "aa1f7a65-a867-436a-9a7f-264068f4bdea" }, "href": "/ovirt-engine/api/hosts/aa1f7a65-a867-436a-9a7f-264068f4bdea/nics/abce07fa-cb7f-46f2-b967-69d1feaa4075", "id": "abce07fa-cb7f-46f2-b967-69d1feaa4075", "ip": { "address": "172.17.28.212", "netmask": "255.255.255.0", "version": "v4" }, "ipv6": { "gateway": "::", "version": "v6" }, "ipv6_boot_protocol": "none", "mac": { "address": "b4:96:91:3f:47:1c" }, "mtu": 9000, "name": "bond28", "network": { "href": "/ovirt-engine/api/networks/f3ef80cf-bf3a-4fa5-aed9-7d9e7455f804", "id": "f3ef80cf-bf3a-4fa5-aed9-7d9e7455f804" }, "network_labels": [], "properties": [], "speed": 10000000000, "statistics": [], "status": "up" }, "id": "abce07fa-cb7f-46f2-b967-69d1feaa4075", "invocation": { "module_args": { "bond": { "interfaces": [ "p2p1", "p2p2" ], "mode": 4, "name": "bond28" }, "check": true, "fetch_nested": false, "interface": null, "labels": null, "name": "ovirt-staging-hv-02.avinity.tv", "nested_attributes": [], "networks": [ { "address": "172.17.28.212", "boot_protocol": "static", "id": "3e40ff7d-5384-45f1-b036-13e6f91aff56", "name": "backbone", "netmask": "255.255.255.0", "version": "v4" } ], "poll_interval": 3, "save": true, "state": "present", "sync_networks": false, "timeout": 180, "wait": true } }, "item": { "bond": { "interfaces": [ "p2p1", "p2p2" ], "mode": 4, "name": "bond28" }, "check": true, "name": "ovirt-staging-hv-02.avinity.tv", "networks": [ { "address": "172.17.28.212", "boot_protocol": "static", "name": "backbone", "netmask": "255.255.255.0", "version": "v4" } ], "save": true } } Read vars_file 'vars/engine_vars.yml' Read vars_file 'vars/secrets.yml' Read vars_file 'vars/ovirt_infra_vars.yml' Changes resulted in applying configuration exactly as intended. Not sure it this was the actual intention, but please let me know if the made change was as initially intended for sorted compare to work. My pipenv setup: Python 3.7 ansible==2.8.6 asn1crypto==1.1.0 bcrypt==3.1.7 cffi==1.13.1 cryptography==2.8 dnspython==1.16.0 ipaddress==1.0.23 Jinja2==2.10.3 jmespath==0.9.4 lxml==4.4.1 MarkupSafe==1.1.1 netaddr==0.7.19 ovirt-engine-sdk-python==4.3.3 paramiko==2.6.0 passlib==1.7.1 pyasn1==0.4.5 pycparser==2.19 pycurl==7.43.0.3 PyNaCl==1.3.0 PyYAML==5.1.2 six==1.12.0 Ansible vars and play: ================================= host_networks: - name: ovirt-staging-hv-02.avinity.tv check: true save: true bond: name: bond28 mode: 4 interfaces: - p2p1 - p2p2 networks: - name: backbone boot_protocol: static address: 172.17.28.212 netmask: 255.255.255.0 version: v4 ================================= - name: Setup host networks ovirt_host_network: auth: "{{ ovirt_auth }}" name: "{{ item.name }}" state: "{{ item.state | default(omit) }}" check: "{{ item.check | default(omit) }}" save: "{{ item.save | default(omit) }}" bond: "{{ item.bond | default(omit) }}" networks: "{{ item.networks | default(omit) }}" labels: "{{ item.labels | default(omit) }}" interface: "{{ item.interface | default(omit) }}" with_items: - "{{ host_networks | default([]) }}" tags: - host_networks - networks ====================================

2 3

[feedback needed] oVirt master test
by Sandro Bonazzola 05 Nov '19

05 Nov '19

Hi, as part of the 4.4 development we'd like to ask for testing current master. In order to ease the test, you can take: oVirt Node: https://resources.ovirt.org/pub/ovirt-master-snapshot/iso/ovirt-node-ng-ins… when this link won't be available anymore due to nightly build rotation you can take the latest from https://resources.ovirt.org/pub/ovirt-master-snapshot/iso/ovirt-node-ng-ins… oVirt appliance: https://resources.ovirt.org/pub/ovirt-master-snapshot/rpm/el8/x86_64/ovirt-… as per oVirt Node, you can take the latest from https://resources.ovirt.org/pub/ovirt-master-snapshot/rpm/el8/x86_64/ if above link doesn't work. The above 2 builds have been tested on a single host nested VM system with 70Gb disk, 8Gb of RAM and 4 cores for the node. Both oVirt Node and oVirt Engine appliance installation succeeded on 80GB NFS external storage with static IP addressing. We have a known issue on booting with more than 1 NIC that will be addressed soon, so please use a single NIC in your tests for now. Looking forward for your feedback, thanks. -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 0

[ANN] oVirt 4.3.7 First Release Candidate is now available for testing
by Sandro Bonazzola 05 Nov '19

05 Nov '19

The oVirt Project is pleased to announce the availability of the oVirt 4.3.7 First Release Candidate for testing, as of October 18th, 2019. This update is a release candidate of the seventh in a series of stabilization updates to the 4.3 series. This is pre-release software. This pre-release should not to be used in production. This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 7.7 or later (but <8) * CentOS Linux (or similar) 7.7 or later (but <8) This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 7.7 or later (but <8) * CentOS Linux (or similar) 7.7 or later (but <8) * oVirt Node 4.3 (available for x86_64 only) has been built consuming CentOS 7.7 Release See the release notes [1] for known issues, new features and bugs fixed. Notes: - oVirt Appliance is already available - oVirt Node is already available Additional Resources: * Read more about the oVirt 4.3.7 release highlights: http://www.ovirt.org/release/4.3.7/ * 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.7/ [2] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

5 8

Re: [ANN] oVirt 4.3.7 First Release Candidate is now available for testing
by Strahil 04 Nov '19

04 Nov '19

Hi Dominik, I think I found it - it seems that for some reason my gateway is missing in 'ip route'. Running 'ifdown ovirtmgmt; ifup ovirtmgmt' fixes it, which proves that network scripts read properly the ifcfg-ovirtmgmt file. Do you have any idea where to look for? Best Regards, Strahil NikolovOn Nov 2, 2019 17:17, Strahil <hunter86_bg(a)yahoo.com> wrote: > > I think I have a theory about ovirt1 , but I have to test it. > > 1. Ovirt1 has a team device controlled by NetworkManager , but in engine those interfaces are unused > 2. I guess that when I recently 'reinstalled' the host from UI, the old teamports' ifcfg-<DEVICENAME> was moved to ifcfg-<DEVICENAME>-1 and the original file was left empty. > 3. When the system rebooted, network.service rereads all ifcfg-* files and starts the team0 , but when NetworkManager reads the empty files - he alters the /etc/resolv.conf which leads to out-of-sync status. > > Still, this is only theory and as ovirt3 has no team device (plain gluster arbiter) - I'm not sure how close is this one. > > Best Regards, > Strahil Nikolov > > On Nov 2, 2019 09:50, Strahil Nikolov <hunter86_bg(a)yahoo.com> wrote: >> >> I saw the hint in the Cluster's tab and then on each host. I had to put the host back to maintenance in order to sync it again. >> >> Logs attached . >> >> Best Regards, >> Strahil Nikolov >> >> В четвъртък, 31 октомври 2019 г., 16:12:53 ч. Гринуич+2, Dominik Holler <dholler(a)redhat.com> написа: >> >> >> >> >> On Thu, Oct 31, 2019 at 10:06 AM Sandro Bonazzola <sbonazzo(a)redhat.com> wrote: >>> >>> >>> >>> Il giorno gio 31 ott 2019 alle ore 09:45 Strahil Nikolov <hunter86_bg(a)yahoo.com> ha scritto: >>>> >>>> Hi Sandro, >>>> >>>> I have just updated to latest release candidate (2 clusters in total - 1 AMD , 1 Intel). >>>> The only issue observed is that after patching every host's ovirtmgmt (I have another one that has none of the 4 roles which was OK) is out of sync and has to be synced before removing maintenance. >>>> >>>> Still the system was accessible. >>>> >>>> Can you guide me which log reports the out-of-sync in order to further investigate. >>> >>> >>> +Miguel Duarte de Mora Barroso , +Dominik Holler can you please help here? >>> >>> >> >> >> Do you remember if there was a hint shown as a tooltip if you hover the >> mouse pointer over ovirtmgmt in >> "Compute > Hosts > xxx > Network Interfaces > Setup Host Networks" >> ? >> >> Are you able to share the vdsm.log and engine.log after the ovirtmgmt? >> >>

3 3

Re: Disk encryption in oVirt
by Strahil 04 Nov '19

04 Nov '19

Hi, Maybe a gluster encryption will also cover your needs in a hyper converged setup? Best Regards, Strahil Nikolov On Oct 22, 2019 14:43, Sandro Bonazzola <sbonazzo(a)redhat.com> wrote: > > > > Il giorno mar 22 ott 2019 alle ore 12:32 MIMMIK _ <dmarini(a)it.iliad.com> ha scritto: >> >> Is there a way to get a full disk encryption on virtual disks used by VMs in oVirt? > > > You can use encrypted file system managed from within the VM itself if the OS support it (dm-crypt with LUKS on GNU Linux, BitLocker) which is the most secure choice on this topic. > Encrypting the storage hosting the VM disks won't help once you access the storage for booting the VM, at that point disks will be accessible without encryption. > > > > >> >> >> Regards >> _______________________________________________ >> 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/3FMGDSRBHRWYR… > > > > -- > > Sandro Bonazzola > > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > > Red Hat EMEA > > sbonazzo(a)redhat.com > > Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.

2 1

Re: oVirt/RHV 4.3.6: How to boot a Q35/UEFI VM from CD?
by Strahil 04 Nov '19

04 Nov '19

Hi, Can you give a try of the workaround in https://bugzilla.redhat.com/show_bug.cgi?id=1727987#c0 ? At least it works for RHEL 8 (and most probably CentOS 8). Best Regards, Strahil NikolovOn Nov 3, 2019 12:14, Mathieu Simon <mathieu.simon(a)gymneufeld.ch> wrote: > > Hi > > Am Sa., 2. Nov. 2019 um 08:51 Uhr schrieb Strahil Nikolov > <hunter86_bg(a)yahoo.com>: > > > Have you tried with another ISO ? > This is quite weird, still better than my initial testing but here it > goes. I've slimmed down my attempts to Q35 and UEFI (both on and off): > > - Server 2019 ISO boots into installer with or without SecureBoot > enabled (I clearly remember it didn't work in any combination I've > tried, but now it did, anyhow). The OS installes and boots with > SecureBoot enabled > - Server 2016 ISO fails to boot right at the windows bootloader*, > however I don't care for Server 2016 that much anymore at that point > in time, and it could well be that the ISO image could be of an older > revision > (MS does release updated images from time to time) > - Debian 10 boots of the CD, however it doesn't seem like NVRAM > changes are saved in oVirt / RHV guests yet. So at boot the OS doesn't > start and you have to once boot from file (EFI disk -> EFI -> debian > -> shimx64.efi) > After the boot you you have to copy all (or only shimx64.efi?) to > /boot/efi/EFI/BOOT as BOOTX64.EFI like Windows. Debian 10 has a > Microsoft-signed shim loader so SecureBoot actually works. > - Ubuntu 18.04 boots of the disc, installs and boots since their > installer puts a copy of shimx64.efi into /boot/efi/EFI/BOOT which is > where OVMF looks for a loader > > I'm I correctly guessing based on looking at the "VM devices" list per > VM that oVirt/RHV doesn't yet provide a way to provide a persistent > NVRAM image to guests? > Sso for the time being we're actually stuck on Linux systems to have a > EFI/BOOT/BOOTX64.EFI present? Is this the issue you wrote about? > (I've encountered this very same issue on plain KVM and Proxmox, in > both cases a small disk image is required per VM to make the content > of the NVRAM persistent across VM reboots) > > Regards > Mathieu > > * See screenshot uploaded here: https://imgur.com/a/ZsnbCOM > _______________________________________________ > 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/PTQRSIUTCWI4V…

2 1

Re: Cannot enable maintenance mode
by Bruno Martins 04 Nov '19

04 Nov '19

Hi Lukas, Thanks for your message! In my cluster, I have all the VM's running under "HOST2". The issue I'm having is that I can't enable maintenance mode on "HOST1", in order to re-add it to oVirt Manager (SSL certificate replacement stuff). I did it successfully on "HOST2", but the other one seems to ignore my actions, with that message in the logs... Cheers, Bruno From: Lukas Svaty <lsvaty(a)redhat.com> Sent: 16 de outubro de 2019 10:49 To: Bruno Martins <bruno.o.martins(a)gfi.world> Cc: users(a)ovirt.org Subject: Re: [ovirt-users] Re: Cannot enable maintenance mode Did you "Consider manual intervention" such as "stopping" or "migrating Vms" which are running on that host? If you are trying to put host to maintenance, it will migrate all the VMs somewhere else, thus... you might have problem with migrations (try to migrate them to other destination host) or power them off. On Wed, Oct 16, 2019 at 9:15 AM Bruno Martins <mailto:bruno.o.martins@gfi.world> wrote: Hey guys, There are really no options left here? Is there something else I should check? Thank you! -----Original Message----- From: Bruno Martins <mailto:bruno.o.martins@gfi.world> Sent: 3 de outubro de 2019 22:41 To: Benny Zlotnik <mailto:bzlotnik@redhat.com> Cc: mailto:users@ovirt.org Subject: [ovirt-users] Re: Cannot enable maintenance mode Hello Benny, I did. No luck, still... Cheers! -----Original Message----- From: Benny Zlotnik <mailto:bzlotnik@redhat.com> Sent: 2 de outubro de 2019 19:19 To: Bruno Martins <mailto:bruno.o.martins@gfi.world> Cc: mailto:users@ovirt.org Subject: Re: [ovirt-users] Re: Cannot enable maintenance mode Did you try the "Confirm Host has been rebooted" button? On Wed, Oct 2, 2019 at 9:17 PM Bruno Martins <mailto:bruno.o.martins@gfi.world> wrote: > > Hello guys, > > No ideas for this issue? > > Thanks for your cooperation! > > Kind regards, > > -----Original Message----- > From: Bruno Martins <mailto:bruno.o.martins@gfi.world> > Sent: 29 de setembro de 2019 16:16 > To: mailto:users@ovirt.org > Subject: [ovirt-users] Cannot enable maintenance mode > > Hello guys, > > I am being unable to put a host from a two nodes cluster into maintenance mode in order to remove it from the cluster afterwards. > > This is what I see in engine.log: > > 2019-09-27 16:20:58,364 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-6-thread-45) [4cc251c9] Correlation ID: 4cc251c9, Job ID: 65731fbb-db34-49a9-ab56-9fba59bc0ee0, Call Stack: null, Custom Event ID: -1, Message: Host CentOS-H1 cannot change into maintenance mode - not all Vms have been migrated successfully. Consider manual intervention: stopping/migrating Vms: Non interactive user (User: admin). > > Host has been rebooted multiple times. vdsClient shows no VM's running. > > What else can I do? > > Kind regards, > > Bruno Martins > _______________________________________________ > Users mailing list -- mailto:users@ovirt.org To unsubscribe send an > email to mailto:users-leave@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/X5FJWFW7 > GXNW6YWRPFWOKA6VU3RH4WD3/ > _______________________________________________ > Users mailing list -- mailto:users@ovirt.org To unsubscribe send an > email to mailto:users-leave@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/DD5DW6KK > OOHGL3WFEKIIIS57BN3VWMAQ/ _______________________________________________ Users mailing list -- mailto:users@ovirt.org To unsubscribe send an email to mailto:users-leave@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/64GZQKZA7LX7K… _______________________________________________ Users mailing list -- mailto:users@ovirt.org To unsubscribe send an email to mailto:users-leave@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/JJPEC7RDG3AUS… -- LUKAS SVATY RHV QE

1 0

Self-Hosted Engine + vxlan + networkd
by pavel＠gremwell.com 04 Nov '19

04 Nov '19

Dear oVirt Community, It appears that oVirt self-hosted engine does not support network configurations based on systemd-networkd? Am I correct? Does oVirt self-hosted engine deployment support VXLAN interface to configure "ovirtmgmt" on top of it? My setup: - three bare-metal servers: two of them are CentOS 7 based, clean installation. the third one is Ubuntu based served as a storage. - all three of them have public Internet connectivity, via basic Ethernet. - in order to emulate internal network, VXLAN was configured between those three. Mainly for testing purposes. - network configuration was done using systemd-networkd, internal communications worked fine. - DNS server was configured on this internal network. worked as direct/reverse resolver. Thus, the main host which I tried to convert to self-hosted engine following https://www.ovirt.org/documentation/self-hosted/chap-Deploying_Self-Hosted_… guide, has the following network interfaces (redacted): - eth0, static IPv4, connected to the Internet; - vxlan0, on top of eth0, has private IPv4, 192.168.200.1; - hosts names resolve via private VXLAN network using 192.168.200.254. I started deployment saying that: Engine FQDN:ovirt-e1.example.com Network Configuration:Static VM IP Address:192.168.200.250/24 Gateway Address:192.168.200.1 DNS Servers:192.168.200.254 hostname of this host on the management network: ovirt-h1.example.com Deployment fails with error "Host ovirt-h1.example.com installation failed. Failed to configure management network on the host." After failure the system (host) does not have "ovirtmgmt" bridge. The same situation was when the host moved from networkd configuration to "network-scripts" (with VXLAN support added). I suspect that the root cause of the problem is that ansible scenarios were not able to create "ovirtmgmt" bridge on top of vxlan0. No switching to VLAN-based management interface... (did not actually tried yet).

1 0