rhel-osp-director: UI: unable to change the public interface under service configuration. Environment: Steps to reproduce: 1. Deploy undercloud on bare metal. 2. Go to the "service configuration" tab, select "global", and click on the "Simplified configuration" button. 3. Try to change the "Public interface" value. Result: The public interface for BM is limited to em2. Unable to change it to another interface: 1. "Simplified configuration" allows to select between em2(bare metal) and eth0(virtual) 2. "Advanced configuration" allows to set the "Neutron Public Interface" field to any nic name, but after clicking on "Save" and checking the value again - it goes back to em2. Expected result: Should be able to specify any NIC.
Brad, can you verify that we can't set the value to anything but eth0 or em2 so that we can assess whether this needs to be a 0 day fix?
The problem lies in the advanced configuration. The simple configuration does indeed only allow eth0 or em2, but a user *should* be able to specify something different in the advanced configuration. There is a problem where the code for the advanced configuration syncs the params across role types. Therefore, it was setting it to whatever is in one of the roles. The current proposed fix just disables that syncing. There should be a future enhancement to perhaps use a white or blacklist for syncing.
Environment: openstack-tuskar-ui-0.3.0-15.el7ost.noarch instack-undercloud-2.1.2-23.el7ost.noarch Using the "Simplified configuration" it still lets only select between eth0 and em2. Using the "Advanced configuration", the NIC set in the "Neutron Public Interface" field is saved now (i.e. not lost), after clicking on "Save Configuration".
Verified: It's possible to set the Neutron Public Interface via "Advanced Configuration". Environment: python-tuskarclient-0.1.18-3.el7ost.noarch openstack-tuskar-ui-extras-0.0.4-1.el7ost.noarch instack-undercloud-2.1.2-23.el7ost.noarch openstack-tuskar-0.4.18-3.el7ost.noarch openstack-tuskar-ui-0.3.0-15.el7ost.noarch Filed this non-blocker for the "Simplified Configuraton" instead: https://bugzilla.redhat.com/show_bug.cgi?id=1252553 Thanks.
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://access.redhat.com/errata/RHBA-2015:1624