Bug 1151616
Summary: | vip mac address conflicts when more than 1 HA deployment | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Balaji <bjayavel> |
Component: | ruby193-rubygem-staypuft | Assignee: | Scott Seago <sseago> |
Status: | CLOSED ERRATA | QA Contact: | Ofer Blaut <oblaut> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 5.0 (RHEL 7) | CC: | ajeain, dnavale, mburns, rhos-maint, sseago, yeylon |
Target Milestone: | z2 | Keywords: | ZStream |
Target Release: | Installer | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | ruby193-rubygem-staypuft-0.4.5-1.el6ost | Doc Type: | Bug Fix |
Doc Text: |
Previously, when deploying an High Availability (HA) environment, VIP interfaces were created with pre-defined MAC addresses. As a result, when a second HA environment was defined, the MAC addresses already existed causing an error.
With this update, the pre-defined MAC addresses are generated differently to prevent conflicts. As a result, multiple HA environments are now available.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2014-11-04 17:03:28 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: |
Description
Balaji
2014-10-10 19:41:49 UTC
The issue is that for the (fake) interfaces we have to create internally to foreman to facilitate IP address reservation, we were just setting the mac addr to 00:00:00:00:00:xx" where the 'xx' corresponds to the VIP number (sequentially from 01). I've modified this to include deployment ID in the scheme. https://github.com/theforeman/staypuft/pull/349 Issue is not seen on rhel-osp-installer-0.4.5-2.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. https://rhn.redhat.com/errata/RHBA-2014-1800.html |