April 2019 - Users - oVirt List Archives

Installing VM - Fedora installer stuck on "Setting up installation source..."
by Jarosław Prokopowski 10 Apr '19

10 Apr '19

Hello, I installed oVirt 4.3.2, added NFS ISO domain and trying to create Fedora 26 VM. The installer starts but is stuck on "Installation Source Setting up installation source..." on the "INSTALLATION SUMMARY" screen. I cannot find any useful information in logs. Do you have any idea what can cause the issue and how to fix that? Thanks Jarek

2 3

Re: Vagrant Plugin
by Jeremy Tourville 10 Apr '19

10 Apr '19

Thanks for your reply Luca, I confirmed the cluster name, it is "Default". I even tried to run the script again and I made sure the D in default was upper case because linux is case sensitive. It still fails in the same way as before. [cid:c5758639-8ce0-46d1-ad0b-900af9cc138e] ________________________________ From: Luca 'remix_tj' Lorenzetto <lorenzetto.luca(a)gmail.com> Sent: Saturday, March 30, 2019 3:34 AM To: Jeremy Tourville Subject: Re: [ovirt-users] Vagrant Plugin Il ven 29 mar 2019, 19:12 Jeremy Tourville <Jeremy_Tourville(a)hotmail.com<mailto:Jeremy_Tourville@hotmail.com>> ha scritto: I am having some trouble getting the Ovirt Vagrant plugin working. I was able to get Vagrant installed and could even run the example scenario listed in the blog. https://www.ovirt.org/blog/2017/02/using-oVirt-vagrant.html My real issue is getting a vm generated by the SecGen project https://github.com/SecGen/SecGen to come up. If I use the VirtualBox provider everything works as expected and I can launch the vm with vagrant up. If I try to run using Ovirt provider it fails. I had originally posted this over in Google groups / Vagrant forums and it was suggested to take it to Ovirt. Hopefully, somebody here has some insights. The process fails quickly with the following output. Can anyone give some suggestions on how to fix the issue? I have also included a copy of my vagrantfile below. Thanks in advance for your assistance! ***Output*** Bringing machine 'escalation' up with 'ovirt4' provider... ==> escalation: Creating VM with the following settings... ==> escalation: -- Name: SecGen-default-scenario-escalation ==> escalation: -- Cluster: default ==> escalation: -- Template: debian_stretch_server_291118 ==> escalation: -- Console Type: spice ==> escalation: -- Memory: ==> escalation: ---- Memory: 512 MB ==> escalation: ---- Maximum: 512 MB ==> escalation: ---- Guaranteed: 512 MB ==> escalation: -- Cpu: ==> escalation: ---- Cores: 1 ==> escalation: ---- Sockets: 1 ==> escalation: ---- Threads: 1 ==> escalation: -- Cloud-Init: false ==> escalation: An error occured. Recovering.. ==> escalation: VM is not created. Please run `vagrant up` first. /home/secgenadmin/.vagrant.d/gems/2.4.4/gems/ovirt-engine-sdk-4.0.12/lib/ovirtsdk4/service.rb:52:in `raise_error': Fault reason is "Operation Failed". Fault detail is "Entity not found: Cluster: name=default". HTTP response code is 404. Hello Jeremy, Looks like you have no cluster called default in your setup. Edit your vagrant file accordingly to your setup. Luca

2 2

Re: Bug 1666795 - Related? - VM's don't start after shutdown on FCP
by Nardus Geldenhuys 10 Apr '19

10 Apr '19

attaching ovirt engine.log

1 1

virt-v2v from Fedora 29 to oVirt 4.3 and ovirtsdk4
by Gianluca Cecchi 10 Apr '19

10 Apr '19

Hello, I'm trying to migrate a VM from a Fedora 29 system to oVirt 4.3.2. I'm trying to use the "-o rhv-upload" option that should be faster. virt-v2v -o rhv-upload -oc https://my_engine/ovirt-engine/api -os my_sd_domain -op /tmp/ovirt-admin-password -of raw -oo rhv-cafile=/tmp/ca.pem -oo rhv-direct --bridge nat:ovn193 my_vm But I get " Traceback (most recent call last): File "<string>", line 1, in <module> ModuleNotFoundError: No module named 'ovirtsdk4' virt-v2v: error: the Python module ‘ovirtsdk4’ could not be loaded, is it installed? See previous messages for problems. If reporting bugs, run virt-v2v with debugging enabled and include the complete output: virt-v2v -v -x [...] " I see on Fedora 29 repos thease are the only relevant available packages: [root@ope46 ~]# dnf search ovirt ... ovirt-engine-cli.noarch : oVirt Engine Command Line Interface ... ovirt-engine-sdk-java-javadoc.noarch : Javadocs for ovirt-engine-sdk-java ... ovirt-engine-sdk-java.noarch : oVirt Engine Software Development Kit (Java) ... python2-ovirt-engine-sdk.noarch : oVirt Engine Software Development Kit (Python) ... and python2-ovirt-engine-sdk.noarch is related to source ovirt-engine-sdk-python-3.6.9.1-7.fc29.src.rpm so only sdk3 On oVirt repos I see here only for F28: https://resources.ovirt.org/pub/ovirt-4.3/rpm/fc28/x86_64/ trying to install # dnf install https://resources.ovirt.org/pub/ovirt-4.3/rpm/fc28/x86_64/python3-ovirt-eng… gives: Error: Problem: conflicting requests - nothing provides python(abi) = 3.6 needed by python3-ovirt-engine-sdk4-4.3.0-1.fc28.x86_64 (try to add '--skip-broken' to skip uninstallable packages) How can I get correct rpm packages to interact with v4 api of 4.3? Thanks, Gianluca

2 2

Different credentials ovirt_vm module
by Florian Rädler 09 Apr '19

09 Apr '19

Hi, how can i use other credentials (run once) in the ansible playbook for Sysprep domain join? My playbook: [cid:image001.png@01D4EF22.B6352610] User_name and root_password does not sound like it's the right option. How can I realize that? 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

Cannot get IPMI fencing to work on CIMC
by Alan G 09 Apr '19

09 Apr '19

Hi, I have some Cisco C-220M4 servers with CIMC (not connected to UCS fabric). I can get the fencing to work on the command line like this fence_ipmilan -a XXX -l YYY -p ZZZ --hexadecimal-kg=ABC -o status -P But when I try to configure & test in the Engine UI I get, "Test failed: Internal JSON-RPC error". Obviously the wrong parameters are being passed to the script, but I cannot find a log anywhere which will show me the parameters being used. Anyone else got IPMI working on CIMC? Thanks, Alan

2 1

Re: oVirt 4.3.2 Disk extended broken (UI)
by Strahil 09 Apr '19

09 Apr '19

I guess nobody has experienced such behaviour. I'm pretty sure that initial size of the disk was 100GB and after setting increase by 40 , I see size of 140GB - but my Linux and qemu-img see it as 180GB. Anyone able to guide me through ? Maybe an update to 4.3.3 will solve it? Maybe I should open a bug, but what module is affecting me? Best Regards, Strahil NikolovOn Apr 6, 2019 04:54, Strahil Nikolov <hunter86_bg(a)yahoo.com> wrote: > > Hi, > > I have just extended the disk of one of my openSuSE VMs and I have noticed that despite the disk is only 140GiB (in UI), the VM sees it as 180GiB. > > I think that this should not happen at all. > > [root@ovirt1 ee8b1dce-c498-47ef-907f-8f1a6fe4e9be]# qemu-img info c525f67d-92ac-4f36-a0ef-f8db501102fa > image: c525f67d-92ac-4f36-a0ef-f8db501102fa > file format: raw > virtual size: 180G (193273528320 bytes) > disk size: 71G > > Attaching some UI screen shots. > > Note: I have extended the disk via the UI by selecting 40GB (old value in UI -> 100GB). > > Best Regards, > Strahil Nikolov >

1 0

[ANN] oVirt 4.3.3 Third Release Candidate is now available
by Sandro Bonazzola 09 Apr '19

09 Apr '19

The oVirt Project is pleased to announce the availability of the oVirt 4.3.3 Third Release Candidate, as of April 9th, 2019. This update is a release candidate of the third 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.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] 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-pre/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

genev_sys_6081 left/entered promiscuous mode
by Arif Ali 09 Apr '19

09 Apr '19

Hi all, I was wondering if anyone seen the messages below in the syslog. I see this set every second, and I am not sure why this is the case, and it's filling the logs quite a lot Mar 22 23:08:08 <snip> kernel: device genev_sys_6081 left promiscuous mode Mar 22 23:08:08 <snip> kernel: i40e 0000:3d:00.0 eno3: port 6081 already offloaded Mar 22 23:08:08 <snip> kernel: i40e 0000:3d:00.1 eno4: port 6081 already offloaded Mar 22 23:08:08 <snip> kernel: i40e 0000:3d:00.2 eno5: port 6081 already offloaded Mar 22 23:08:08 <snip> kernel: i40e 0000:3d:00.3 eno6: port 6081 already offloaded Mar 22 23:08:08 <snip> kernel: device genev_sys_6081 entered promiscuous mode Mar 22 23:08:09 <snip> kernel: i40e 0000:3d:00.0 eno3: UDP port 6081 was not found, not deleting Mar 22 23:08:09 <snip> kernel: i40e 0000:3d:00.1 eno4: UDP port 6081 was not found, not deleting Mar 22 23:08:09 <snip> kernel: i40e 0000:3d:00.2 eno5: UDP port 6081 was not found, not deleting Mar 22 23:08:09 <snip> kernel: i40e 0000:3d:00.3 eno6: UDP port 6081 was not found, not deleting Mar 22 23:08:09 <snip> kernel: device genev_sys_6081 left promiscuous mode -- regards, Arif Ali

2 2

Hosted-engine inaccessible
by tau＠sanren.ac.za 09 Apr '19

09 Apr '19

Hi, I am currently experiencing a problem with my Hosted-engine. Hosted-engine disconnected after increasing / partition. The increase went well but after some time the hosted-enigine VM disconnected and has since been giving alerts such as re-initializingFSM. Though VMs underneth are running, Hosted-engine --vm-status: "reason": "failed liveliness check", "health": "bad", "vm": "up", "detail" There is no backup to restore at the moment. I am looking for a way to bring it up without redeploying the hosted engine. Thanks in advance for your help. Kind regards, Tau

1 0