Stuck at Waiting for VM to get an IP address... #120
Comments
|
I am experiencing the same issue when using either my mgmt or vm network. I did have this SecGen project working in the past on oVirt 4.3. I can't say that is the issue though. I have also recently rebuilt my system to oVirt 4.4 on a single node so our situation is very similar. |
|
I tried a couple of things to test this: #2 Just like you, I do get the red exclamation if Vagrant is building the VM. I think my tests prove that my oVirt environment and template are running correctly. I even tried running the SecGen project by building a project folder first. |
|
@jeremytourville When vagrant brings up the vm, it has a red exclamation mark because the vm is running in "Run Once" mode, not because the guest additions are not working. Even when I up a box with vagrant, I see the ip address being displayed in the ovirt-engine and the guest additions are working properly when I ssh into the vm.
I wonder if the api has changed. I'm not a ruby programmer, so excuse me if the following is not "right." It seems to work. I pulled down the code and put in some code to display the variables in Sure enough the ip_addr never gets populated. I'm still trying to work out why. |
|
@GervaisdeM Thanks for reminding me about run once mode expected behavior. I had forgotten about that as I rarely if ever run VMs in that manner for most of the work I do. You said>>>"I wonder if the api has changed?" I'm not sure but I do know this was working for me previously in oVirt 4.3. I'm going to ask a few programmer friends and see if we can hunt down the issue. Let's keep this thread updated with findings as we are both having the same issue. |
|
@jeremytourville You get any further? I was off on other things for a few days. It seems that this is the line that is failing to work: Not sure if this is correct, but I changed this line so that it falls to multiple lines and put in a couple more Output looks like this: I continue to get nowhere... Still not a ruby programmer 😀 |
|
I haven't forgotten. I had mistakenly thought that some of the developers I know could program in Ruby. I guess not. I'll continue to check with my network. Surely somebody can give us a hand! |
|
@myoung34 Any ideas what is going on here? |
|
I hard coded the IP address by commenting out the line: https://github.com/myoung34/vagrant-ovirt4/blob/master/lib/vagrant-ovirt4/action/wait_till_up.rb#L60 and replacing it with
☝️ The guest additions are enabled and the IP is showing in the ovirt-engine gui. I can ssh to the box as the vagrant user.
|
|
I can look around, but unfortunately I no longer run ovirt so I dont have access to much of the debugging ability. |
|
as for the debugging:
My gut feeling here is that there's something related to the network or guest agent causing this and even if i got it up it would work with my set up. The only thing I can think of is to try to get the VM to sleep as long as possible and try to inspect it at the hardware level (see if it's getting an IP off DHCP, etc) or try to use the same settings youre using if you launch manually to get it to work with the vagrant plugin |
|
Hi, I did a bit of debugging with pry and came up with a fix #121 |
|
I just tried this after the merge request was committed. I downloaded the zip file again and installed. I presume that should update the code on my machine with the newest fix. I didn't have any luck I am still getting waiting for IP address. I am running oVirt 4.4.x on CentOS 8.2 or 8.3 My VM that has the ovirt4 extension is Ubuntu 18.04 LTS. |
|
Have you double checked that the new code from the zip file is actually used? E.g. just rename to If vagrant uses the fixed version from the merge request, it should now print out |
|
I checked to find out where the yml file is located. Which one do I need to edit? (see below) Presently, I am still getting the Waiting for VM to get an IP address... message when I run vagrant up from within my SecGen projects folder. I even deleted all my SecGen projects and recreated one after I had installed the fix from #123 $sudo find / -name en.yml |
|
Which folder contains the freshly pulled zip-file from this project? Either way, if you renamed one as How did you install the patched version? |
|
@daFritz84 🎉 @jeremytourville since you have pulled the source code, you should be able to run the code from that dir like I did. Do a Then run |
|
@myoung34 I'm going to do a bunch of testing and can report back if "everything" is working now with oVirt 4.4.4.5-1.el8 (what I am running) and can report back here before you push a new release of the plugin. |
|
@myoung34 I ran through testing all the Supported Commands (tested). Below are my results. Many of the issues don't really matter to me. I really just need my development team to be able to up and destroy boxes. Any chance that the ruby gem can get pushed (even as a beta) so that I can update my Vagrantfile (we have a very custom setup) and others in my group can @daFritz84 Any interest in seeing if you can sort out some of the issues? Adding support for vagrant snapshot restore would make those snapshot features much more usable, IMO. We don't have that support in our vSphere setup now, so it would give us added functionality (nice to have, but not import for our use case). Testing results vagrant destroy vagrant ssh [-c '#command'] vagrant ssh-config vagrant halt vagrant reload vagrant status vagrant suspend vagrant resume vagrant snapshot list vagrant snapshot delete [id] vagrant snapshot save [description] |
|
@GervaisdeM I will have a look and see what I can do 😄 If you don't mind, I prefer to split up each bug into its own little github issue with a backreference to this issue. As far as I'm concerned, the original cause of this issue has been resolved. |
|
The original issue that was reported on here has been resolved. |
I can't get my boxes to come up. They get stuck at
Waiting for VM to get an IP address...The box does come up though and does display properly in the ovirt-engine web interface.
Hitting control-c shuts down the vm and removes it as expected. Can someone help me debug what might be the issue?
Note:
Also:
The text was updated successfully, but these errors were encountered: