Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1156641

Summary: Staypuft is not configuring VLAN interfaces on bare metal
Product: Red Hat OpenStack Reporter: Dan Sneddon <dsneddon>
Component: rubygem-staypuftAssignee: Mike Burns <mburns>
Status: CLOSED NOTABUG QA Contact: Omri Hochman <ohochman>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: Foreman (RHEL 6)CC: mburns, yeylon
Target Milestone: ---   
Target Release: 6.0 (Juno)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-24 22:07: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:
Attachments:
Description Flags
List of configured subnets
none
Traffic type subnet assignments none

Description Dan Sneddon 2014-10-24 21:46:10 UTC
Created attachment 950511 [details]
List of configured subnets

Description of problem:
When multiple subnets are configured in StayPuft with VLAN tags, the VLAN interfaces don't get configured in /etc/sysconfig/network-scripts

Version-Release number of selected component (if applicable):
rubygem-staypuft: 0.4.10
rhel-osp-installer from 2014-10-23.2 repo

How reproducible:
Always

Steps to Reproduce:
1. Configure multiple subnets in StayPuft
2. Assign network traffic types to the subnets
3. Deploy

Actual results:
The Ethernet interfaces are set up with ifcfg-eno1 and ifcfg-eno2, but no VLAN interfaces are created

Expected results:
Each configured subnet with a VLAN should have a corresponding VLAN interface, for instance /etc/sysconfig/network-scripts should have ifcfg-eno1.28 for VLAN 28, etc.

Additional info:
Since StayPuft gets confused about network addressing when the controller cluster traffic is put on a non-default subnet, Puppet fails. The exact error follows:
====
Could not retrieve catalog from remote server: Error 400 on SERVER: Invalid db connection mysql://keystone:stackpass@/keystone at /etc/puppet/
environments/production/modules/keystone/manifests/init.pp:313 on node macb8ca3a66ddc8.example.com
====
The actual DB string should contain the IP address of the DB host. In this case it was an HA configuration, so the DB address should be the shared address configured for Pacemaker+Galera.

Comment 1 Dan Sneddon 2014-10-24 21:47:05 UTC
Created attachment 950512 [details]
Traffic type subnet assignments

Comment 3 Dan Sneddon 2014-10-24 22:05:46 UTC
Scratch this, I think the interface configuration is incorrect in the host record. I am going back and reconfiguring and will try to deploy again.