Bug 1134220
| Summary: | rhel-osp failed to install netwoker because of interface down - br-ex | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Ofer Blaut <oblaut> | ||||
| Component: | openstack-puppet-modules | Assignee: | Ivan Chavero <ichavero> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Ofer Blaut <oblaut> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | urgent | ||||||
| Version: | Foreman (RHEL 6) | CC: | aberezin, gdubreui, ichavero, lars, mburns, morazi, nyechiel, oblaut, rhos-maint, yeylon | ||||
| Target Milestone: | z1 | Keywords: | Triaged | ||||
| Target Release: | Installer | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | openstack-puppet-modules-2014.1-21.8.el7ost | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-10-02 12:56:31 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
If you reboot the system, does enp4s0f1 come up correctly? Or does it always require a manual "ifup"? Looking at the network controller, I see that /etc/sysconfig/network-scripts/br-ex looks like this:
ONBOOT=yes
PEERDNS=no
NM_CONTROLLED=no
NOZEROCONF=yes
DEVICE=br-ex
DEVICETYPE=ovs
OVSBOOTPROTO=dhcp
TYPE=OVSBridge
With OVSBOOTPROTO=dhcp and no OVSDHCPINTERFACES set, this interface will never come up. Running either "ifup br-ex" or "ifup enp4s0f1" (the slave interface) results in:
# ip link show br-ex
17: br-ex: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT
link/ether 80:c1:6e:07:d2:4c brd ff:ff:ff:ff:ff:ff
Whereas adding:
OVSDHCPINTERFACES=enp4s0f1
Results in:
# ifup enp4s0f1
Determining IP information for br-ex...failed.
# ip link show br-ex
17: br-ex: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN mode DEFAULT
link/ether 80:c1:6e:07:d2:4c brd ff:ff:ff:ff:ff:ff
There are several things going on here:
(1) It looks like br-ex was set up incorrectly. This is probably a bug in puppet-vswitch.
(2) It looks like there is no dhcp service available over interface enp4s0f1. But that's okay, because
(3) br-ex *does not require an ip address*, but only gets one if the underlying interface (in this case, enp4s0f1) had an address at the time it was added.
So you could work around this by setting OVSBOOTPROTO=none, but we probably need to fix puppet-vswitch, so I am retargeting this bug to openstack-puppet-modules.
I've tested this problem on bare metal using packstack and couldn't reproduce it. Is it a staypuft problem?? This seems to be related to the puppet-vswitch provider issue on rhel6. The workaround seems to effectively indicate that the bridge interface didn't start initially but This has been addressed with upstream patch 20. This seems to be going in circles a bit. Ofer, can you confirm whether this is still a problem with the latest A1 builds? Moving out of POST since the referenced patch is only applicable to RHEL 6 and not RHEL 7. This problem has been fixed in the latest openstack puppet modules version: openstack-puppet-modules-2014.1-21.8.el6ost Verified openstack-puppet-modules-2014.1-21.8.el6ost.noarch Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-1350.html |
Created attachment 931303 [details] Logs Description of problem: rhel-osp-installer failed to install networker because of interface down attached logs workaround 1. ifconfig enp4s0f1 up 2. puppet agent -tvd Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.install rhel-osp on bare metal 2.check status of networker stuck in 60% 3. Actual results: Expected results: Additional info: