Re: Possible bug in kickstart

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



Sorry, just a follow up to see if anyone has similar experiences with the method of kickstarting bridges on CentOS 7.1.  According to the docs things are correct for 7.1 and I just want to make sure I'm not doing something incorrectly before filing a bug with Red Hat

----- Original Message -----
| Hello All,
| 
| I seem to have run into a bug with the new --bridgeslaves=<INTERFACE> option.
| It would seem that if I tell the bridge device to use a virtual interface
| (like bond0) rather than a physical interface (em1/em2) that kickstart
| completely barfs on it.  I have provided my network section below which
| works fine as long as i don't enable all the bridge content.
| 
| When the installation starts off the creation of bond0 and all VLANs on bond0
| go without issue.  Jumping into TTY2 I can type 'ip a' and see all the bond0
| device and bond0.VLANID devices no problem.
| 
| When I enable bridge content with --bridgeslaves=bond0 or
| --bridgeslaves=bond0.VLANID anaconda barfs
| 
| When I enable bridge content with --bridgeslaves=em1 or --bridgeslaves=em2
| anaconda doesn't have an issue.
| 
| Is this expected behaviour?  I really don't want to have to manually
| manipulate the ifcfg-bond* interfaces and create the ifcfg-BRIDGE*
| interfaces manually so I'd like this to work.
| 
| 
| 
| 
| # Configure a bond over the slaves in failover mode
| network --device=bond0 --noipv6 --bootproto=dhcp --onboot=yes
| --bondslaves=em1,em2 --bondopts=mode=active-backup;primary=em1 --activate
| 
| # Configure VLANs
| network --device=bond0 --vlanid=11 --noipv6 --onboot=yes --bootproto=dhcp
| --activate
| network --device=bond0 --vlanid=100 --noipv6 --onboot=yes --bootproto=dhcp
| --activate
| network --device=bond0 --vlanid=302 --noipv6 --onboot=yes --bootproto=dhcp
| --activate
| network --device=bond0 --vlanid=303 --noipv6 --onboot=yes --bootproto=dhcp
| --activate
| network --device=bond0 --vlanid=304 --noipv6 --onboot=yes --bootproto=dhcp
| --activate
| network --device=bond0 --vlanid=306 --noipv6 --onboot=yes --bootproto=dhcp
| --activate
| 
| # Create a bridge on the bonded VLAN interfaces
| network --device=FASNET --bridgeslaves=bond0
| network --device=GLUSTER --bridgeslaves=bond0.11
| network --device=EXPERIMENTAL --bridgeslaves=bond0.302
| network --device=NAT --bridgeslaves=bond0.303
| network --device=DMZ2 --bridgeslaves=bond0.304
| network --device=NETM --bridgeslaves=bond0.306
| 
| --
| James A. Peltier
| IT Services - Research Computing Group
| Simon Fraser University - Burnaby Campus
| Phone   : 604-365-6432
| Fax     : 778-782-3045
| E-Mail  : jpeltier@xxxxxx
| Website : http://www.sfu.ca/itservices
| Twitter : @sfu_rcg
| Powering Engagement Through Technology
| _______________________________________________
| CentOS mailing list
| CentOS@xxxxxxxxxx
| http://lists.centos.org/mailman/listinfo/centos
| 

-- 
James A. Peltier
IT Services - Research Computing Group
Simon Fraser University - Burnaby Campus
Phone   : 604-365-6432
Fax     : 778-782-3045
E-Mail  : jpeltier@xxxxxx
Website : http://www.sfu.ca/itservices
Twitter : @sfu_rcg
Powering Engagement Through Technology
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos



[Index of Archives]     [CentOS]     [CentOS Announce]     [CentOS Development]     [CentOS ARM Devel]     [CentOS Docs]     [CentOS Virtualization]     [Carrier Grade Linux]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Linux USB]
  Powered by Linux