Bug 1190831 - Running instack-virt-setup results in an error during network setup
Summary: Running instack-virt-setup results in an error during network setup
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: instack-undercloud
Version: 6.0 (Juno)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 7.0 (Kilo)
Assignee: James Slagle
QA Contact: Ami Jeain
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-09 17:14 UTC by Tzu-Mainn Chen
Modified: 2015-06-04 22:07 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-10 14:31:38 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Tzu-Mainn Chen 2015-02-09 17:14:03 UTC
Description of problem:

Running instack-virt-setup using the latest poodle results in the following error:

+ virsh net-start brbm
Network brbm started

++ sudo virsh net-list --all --persistent
++ grep default
++ awk 'BEGIN{OFS=":";} {print $2,$3}'
+ default_net=inactive:yes
+ state=inactive
+ autostart=yes
+ '[' inactive '!=' active ']'
+ virsh net-start default
error: Failed to start network default
error: Unable to create bridge virbr0: File exists


Version-Release number of selected component (if applicable):

instack-undercloud-1.0.40-1.el7ost.noarch

How reproducible:

Run instack-virt-setup

Steps to Reproduce:
1.
2.
3.

Actual results:

Command errors out

Expected results:

Command completes to success.

Additional info:

Comment 3 James Slagle 2015-02-09 21:26:23 UTC
i'm not able to reproduce this issue on a freshly provisioned RHEL 7.1 host.

One thing that came to mind as a possible cause is if LIBVIRT_DEFAULT_URI wasn't defined. Did you do this step prior to running instack-virt-setup:

  echo 'export LIBVIRT_DEFAULT_URI="qemu:///system"' >> ~/.bashrc

You have to login to a new shell for that change to take effect, but that is usually handled automatically when you run newgrp to pick up the new libvirtd group addition:

  newgrp libvirtd
  newgrp

Did you do all of the above?

Assuming you did, what did you do to get RHEL 7.1 installed?

Comment 4 Tzu-Mainn Chen 2015-02-09 22:00:25 UTC
Thanks for looking into this.  I did do those above steps; perhaps I'm provisioning the wrong version of RHEL 7.1?  I'm using beaker, selecting RedHatEnterpriseLinux7 with no tag and the RHEL-7.1-20150206.2 distro.  What options are you selecting?

Comment 5 Tzu-Mainn Chen 2015-02-10 14:31:38 UTC
Hm, I can't duplicate anymore, wonder if I did something silly.  Closing.


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