Bug 1141945
Summary: | Rubygem-Staypuft: in UI under the "Network Configuration" page: the roles that don't need to be under the default network, should appear under "Available Network Traffic Types". | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Alexander Chuzhoy <sasha> |
Component: | rubygem-staypuft | Assignee: | Scott Seago <sseago> |
Status: | CLOSED ERRATA | QA Contact: | Omri Hochman <ohochman> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5.0 (RHEL 7) | CC: | mburns, mlopes, yeylon |
Target Milestone: | z2 | ||
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: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-11-04 17:02:26 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
Alexander Chuzhoy
2014-09-15 20:23:31 UTC
Hmm. I think the title of this bug is misleading. In reality, *none* of the networks types need to be on the default network. I think the intent here is to remove those network types that *must not* be on the default network. Also, to clarify, at this point is that only the tenant and external networks? API networks, storage, etc. can all be on the default? Resolved by https://github.com/theforeman/staypuft/pull/333 Verified: openstack-foreman-installer-2.0.30-1.el6ost.noarch ruby193-rubygem-staypuft-0.4.6-1.el6ost.noarch rhel-osp-installer-0.4.5-1.el6ost.noarch openstack-puppet-modules-2014.1-24.el6ost.noarch ruby193-rubygem-foreman_openstack_simplify-0.0.6-8.el6ost.noarch Bearing in mind comment #1: verified that roles tenant and external in fact appear under the "Available Network Traffic Types" field. doc text covered by another bz. 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 |