Bug 1242203 - instack-virt-setup - instack never got an IP address from the libvirt default network.
Summary: instack-virt-setup - instack never got an IP address from the libvirt default...
Keywords:
Status: CLOSED DUPLICATE of bug 1272509
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director
Version: Director
Hardware: Unspecified
OS: Linux
medium
high
Target Milestone: y2
: 7.0 (Kilo)
Assignee: James Slagle
QA Contact: yeylon@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-12 08:55 UTC by Ola Pavlenko
Modified: 2016-04-18 06:55 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-25 14:51:51 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ola Pavlenko 2015-07-12 08:55:09 UTC
Description of problem:
---------------------------
While running instack-virt-setup getting this message non-stop :

cat: /var/lib/libvirt/dnsmasq/default.leases: No such file or directory
instack never got an IP address from the libvirt default network.


Version-Release number of selected component (if applicable):
------------------------------
latest puddle 2015-07-10.1

How reproducible:
------------------------------

Steps to Reproduce:
1. Following the guide http://10.35.7.52/mburns/latest-docs/environments/virtual.html
2. export NODE_COUNT=7
3. without exporting TESTENV_ARGS
4. run instack-virt-setup

Actual results:
------------------------
getting non-stop messages:
cat: /var/lib/libvirt/dnsmasq/default.leases: No such file or directory
instack never got an IP address from the libvirt default network.


Expected results:
------------------------
vms were successfully created


Additional info:
--------------------------
these messages appeared to run in a loop.
I'll won't interrupt it, will let it run for a while , if nothing changes in 20 mins will terminate .

env: lynx16.qa.lab.tlv.redhat.com / qum10net

Comment 3 Ola Pavlenko 2015-07-12 09:39:44 UTC
it is stil running  with this error.
Terminating the job and raising Severity to Urgent

Comment 4 Ola Pavlenko 2015-07-13 14:05:59 UTC
Happened to me once

Comment 5 Mike Burns 2015-07-13 14:11:43 UTC
instack-virt-setup is not a blocker and this does not appear reproducible

Comment 7 Jay Dobies 2015-07-13 17:16:47 UTC
Do you happen to have another VM matching the name *instack* on your host? I ran into it in the past where the call to retrieve the IP returns all matching *instack* and I had a backup VM called instack-backup that was confusing it.

Comment 8 Ola Pavlenko 2015-07-14 14:00:09 UTC
(In reply to Jay Dobies from comment #7)
> Do you happen to have another VM matching the name *instack* on your host? I
> ran into it in the past where the call to retrieve the IP returns all
> matching *instack* and I had a backup VM called instack-backup that was
> confusing it.

No, only 1.

Comment 10 Udi Kalifon 2015-11-24 07:05:10 UTC
It appears that this is related to RHEL 7.2 (or could be just the libvirt version). There is also supposed to be a patch upstream for instack-virt-install, though I don't have the link to it. To work around the issue, patch the script with this line:

IP=$(ip n | grep $(tripleo get-vm-mac $UNDERCLOUD_VM_NAME) | awk '{print $1;}')

Comment 11 Mike Burns 2015-11-25 14:51:51 UTC
if that's the case, then this is resolved as part of bug 1272509

*** This bug has been marked as a duplicate of bug 1272509 ***


Note You need to log in before you can comment on or make changes to this bug.