Bug #8708
closed
staypuft default kickstart template: CentOS 7 host is left without default route after provisioning
Description
Using staypuft Openstack Deployment the provisioned CentOS 7 host (to be openstack controller) ends up with no default route configured, so no internet access -> the after-install configuration by puppet/staypuft fails.
from install.post.log on the provisioned el7 host:
found provisioning interface = eth0
found interface with default gateway = eth0
setting DEFROUTE=yes on eth0
setting PEERDNS=no on eth1
found provisioning interface = eth0
setting DEFROUTE=no on eth0
- cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE="eth0"
HWADDR="mac1"
BOOTPROTO="dhcp"
ONBOOT=yes
DEFROUTE=no
- cat /etc/sysconfig/network-scripts/ifcfg-eth1
BOOTPROTO="dhcp"
DEVICE="eth1"
HWADDR="mac2"
ONBOOT=yes
PEERROUTES=no
NM_CONTROLLED=no
DEFROUTE=no
PEERDNS=no
-> The provisioned CentOS 7 host is left with no default route, so it doesn't have internet access, and installing extra packages by puppet/staypuft fails.
Updated by Pasi Karkkainen over 9 years ago
Pasi Karkkainen wrote:
Using staypuft Openstack Deployment the provisioned CentOS 7 host (to be openstack controller) ends up with no default route configured, so no internet access -> the after-install configuration by puppet/staypuft fails.
And I forgot to mention software versions.. Foreman/staypuft server is CentOS 6.6 running Foreman 1.8 nightly:
- rpm -qa | grep -i staypuft
ruby193-rubygem-staypuft-0.5.4-1.el6.noarch
foreman-installer-staypuft-client-0.5.2-1.el6.noarch
foreman-installer-staypuft-0.5.2-1.el6.noarch
- rpm -qa | grep -i foreman-release-1
foreman-release-1.8.0-0.develop.201412111740git287d974.el6.noarch
And the stayuft provisioned host is CentOS 7.
Updated by Dominic Cleal over 9 years ago
- Status changed from New to Rejected
Thanks for the bug report, but the Staypuft project track their bugs in Bugzilla, not here. Please see the README for their plugin for details: https://github.com/theforeman/staypuft#contributing