Why does bonding not created properly if VLAN is created on top of it during kickstart installation of Red Hat Enterprise Linux 7?

Issue

• Kickstart installation is supposed to create VLAN device on top of bond.
• The installation goes well, but the bond device is not created properly.
• Using the following network configurations in kickstart, the bonding is not created properly.

network  --bootproto=static --device=bond0 --ip=192.168.0.100 --netmask=255.255.255.0 --noipv6 --activate --bondslaves=eth0,eth4 --bondopts=mode=balance-alb --gateway=192.168.0.1
network  --bootproto=static --device=bond1 --ip=192.168.0.101 --netmask=255.255.255.0 --noipv6 --bondslaves=eth1,eth5 --bondopts=mode=active-backup,miimon=100 --gateway=192.168.0.1
network  --bootproto=static --device=bond2 --ip=192.168.0.102 --netmask=255.255.255.0 --noipv6 --bondslaves=eth2,eth6 --bondopts=mode=active-backup,miimon=100 --gateway=192.168.0.1
network  --bootproto=static --device=bond3 --gateway=192.168.0.1 --ip=192.168.0.105 --netmask=255.255.255.0 --noipv6 --bondslaves=eth3,eth7 --bondopts=mode=active-backup,miimon=100 --vlanid 223

• The bonds are created are as follows.

[root@newrhel7 ~]# ip addr  | grep ": bond" -A 2
10: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN 
    link/ether 52:54:00:36:48:0f brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.100/24 brd 192.168.0.255 scope global bond0
--
11: bond1: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN 
    link/ether 52:54:00:3c:63:8e brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.101/24 brd 192.168.0.255 scope global bond1
--
12: bond2: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN 
    link/ether 52:54:00:e8:b0:48 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.102/24 brd 192.168.0.255 scope global bond2
--
13: bond3.223: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN 
    link/ether 52:54:00:9a:10:f9 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.105/24 brd 192.168.0.255 scope global bond3.223

• Even there is no bond3 file in /etc/sysconfig/network-scripts/

[root@newrhel7 ~]# ls -l /etc/sysconfig/network-scripts/ifcfg-bond*
-rw-r--r--. 1 root root 298 Jun 23 07:19 /etc/sysconfig/network-scripts/ifcfg-bond0
-rw-r--r--. 1 root root 186 Jun 23 07:19 /etc/sysconfig/network-scripts/ifcfg-bond0_slave_1
-rw-r--r--. 1 root root 186 Jun 23 07:19 /etc/sysconfig/network-scripts/ifcfg-bond0_slave_2
-rw-r--r--. 1 root root 289 Jun 23 07:19 /etc/sysconfig/network-scripts/ifcfg-bond1
-rw-r--r--. 1 root root 263 Jun 23 07:19 /etc/sysconfig/network-scripts/ifcfg-bond1-1
-rw-r--r--. 1 root root 289 Jun 23 07:19 /etc/sysconfig/network-scripts/ifcfg-bond2
-rw-r--r--. 1 root root 263 Jun 23 07:19 /etc/sysconfig/network-scripts/ifcfg-bond2-1
-rw-r--r--. 1 root root 332 Jun 23 07:19 /etc/sysconfig/network-scripts/ifcfg-bond3.223
-rw-r--r--. 1 root root 271 Jun 23 07:19 /etc/sysconfig/network-scripts/ifcfg-bond3.223-1