Hide Forgot
Description of problem: During deployment, the first controller node has external subnet missing. After host assignment, when the subnets are assigned to the NICs (as part of the "configure Network" for the hosts)the external subnet goes missing on the host that was assigned first(This is the node with all the VIPs assigned). All other hosts see all the subnets. Version-Release number of selected component (if applicable): Rhel-osp-installer A1 release. How reproducible: Steps to Reproduce: 1.Deploy an HA environment 2. 3. Actual results: External subnet goes missing in the host that was assigned first to the controller node. Expected results: All network subnets should be available to be assigned appropriately. Additional info: Workaround: After three hosts have been assigned to controller host group, go to the configure network section, assign the subnets to NICs on the other two nodes. Unassign the node that has "external" missing. Reassign the host to the controller again. You should see all the network subnets now. Complete network assignments on this host. (Initially the VIPs would have been assigned to this host. During "unassignment", all the VIPs are transferred to one of the other two hosts and are intact).
So one question here: What network traffic types are assigned to which subnets?
External and Public API are assigned to external subnet (this is the one missing on the first node) Tenant is assigned to tenant subnet. All the rest are assigned to default subnet.
I think this is already fixed on A2. Looking at the A1 and A2 code diffs, it looks like A1 does indeed have code that would lead to this, but A2 seems to resolve it, as a side effect of the bonding support changes.
Moving this to ON_QA and TestOnly based on Comment 5
Verified: openstack-foreman-installer-2.0.30-1.el6ost.noarch rhel-osp-installer-0.4.4-1.el6ost.noarch openstack-puppet-modules-2014.1-24.el6ost.noarch ruby193-rubygem-foreman_openstack_simplify-0.0.6-8.el6ost.noarch The reported issue doesn't reproduce. See all the configured NICs on the firstly added controller.
Reproduced: Environment: openstack-foreman-installer-2.0.30-1.el6ost.noarch rhel-osp-installer-0.4.4-1.el6ost.noarch openstack-puppet-modules-2014.1-24.el6ost.noarch ruby193-rubygem-foreman_openstack_simplify-0.0.6-8.el6ost.noarch How to reproduce: 1. After assigning hosts to deployment: Go to: Hosts -> Assigned -> Select a host -> click on "Configure Network", the subnet including the "public api" role isn't available for assigning on one controller out of 3 - the one with vips on it.
This is related to 3 roles: public api, admin api, management. Not just public api.
I can fairly reliably reproduce this by: create HA deployment put public-api, management and/or admin-api on a subnet that is *not* default/provisioning assign 1 host to controller role configure nics on the controller host the subnet with admin/management/pulbic-api will not appear. workaround: choose multiple hosts to assign at the same time.
PR available: https://github.com/theforeman/staypuft/pull/353
Merged.
Verified: Environment: openstack-puppet-modules-2014.1-24.el6ost.noarch rhel-osp-installer-0.4.5-1.el6ost.noarch ruby193-rubygem-foreman_openstack_simplify-0.0.6-8.el6ost.noarch openstack-foreman-installer-2.0.30-1.el6ost.noarch ruby193-rubygem-staypuft-0.4.8-1.el6ost.noarch The reported issue doesn't reproduce. All the configured subnets are available for assignment.
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