Description of problem: When creating a new VLAN interface for a host, StayPuft does not save the interface when submitted if the MAC address field is blank. Version-Release number of selected component (if applicable): rubygem-staypuft: 0.4.10 rhel-osp-installer from 2014-10-23.2 repo How reproducible: Happens every time Steps to Reproduce: 1. Discover host 2. Edit host, go to Network tab 3. Configure eno1.28 (in this case), leave MAC address blank 4. Hit Submit Actual results: The interface is not saved, no error is given, but the interface does not appear in the provisioning template, and does not appear if you edit the host again. Expected results: It should save the interface. MAC address is not required in the ifcfg-eno1.28 file, so it shouldn't be required to enter in the UI. At the very least, it should raise an error. Additional info:
Note this bug also seems to affect Bonding. I tried to create bond0 without a MAC and it wasn't saved. I then tried to create it with the MAC address of the first bond member, and got the attached error.
Created attachment 951166 [details] Bonding Error (happened when I tried to save a bond with the MAC address of one of the members)
Dan, Can you try going through the staypuft workflow for this? Create the subnets with vlans in the normal wizard (fill in the vlan field) Go to the Deployment Summary screen Click on the Hosts tab then the Assigned tab check the host(s) you want to configure click configure networks click the button on the far right of a nic and choose bond and the mode drag the vlan subnet onto the bonded interface Go back to the host details screen and review the nics I followed this and see: bond0 with attached devices: ens10 ens11 and no mac address bond0.28 with the correct subnet attached and no address b/c it was external dhcp bond0.38 with the correct subnet attached and an ip address b/c it's using Foreman's internal db
It does work if I use the Staypuft workflow.
Closing list of bugs for RHEL OSP Installer since its support cycle has already ended [0]. If there is some bug closed by mistake, feel free to re-open. For new deployments, please, use RHOSP director (starting with version 7). -- Jaromir Coufal -- Sr. Product Manager -- Red Hat OpenStack Platform [0] https://access.redhat.com/support/policy/updates/openstack/platform