"Emergency Network Reset" interferes with network-init when trying to fix VLAN specification

[ydirson]

This starts with a user error at install time (forget to specify VLAN on mgmt interface).

As isn't surprising, the network-init script does not succeed on first boot (gencert.ml: cannot get management ip address! seems to be expected, with "no vlan" => "no dhcp" => "no mgmt ip address").

After using the "Emergency Network Reset" through xsconsole to set the VLAN and rebooting, the mgmt interface does come up.

However, we can see the network-init firstboot service still not succeeding. Digging a bit we can see the script is confused to have several PIF on the same NIC, which is possibly a consequence of first running with the bad configuration:

# xe pif-list host-uuid=22771d74-f61f-4e66-9f68-5d8cc619ba49 device=eth0 params=uuid --minimal
...
+ /opt/xensource/bin/xe pif-scan host-uuid=22771d74-f61f-4e66-9f68-5d8cc619ba49
+ '[' -e /etc/firstboot.d/data/management.conf ']'
+ source /etc/firstboot.d/data/management.conf
++ LABEL=eth0
++ MODE=dhcp
++ VLAN=11
+ '[' -n '' ']'
++ /opt/xensource/bin/xe pif-list host-uuid=22771d74-f61f-4e66-9f68-5d8cc619ba49 device=eth0 params=uuid --minimal
+ PIF=7579afc5-134b-f2d3-e531-3752891bb6a4,2f56b313-12e5-61db-b562-63d222112ad9
+ '[' -n 7579afc5-134b-f2d3-e531-3752891bb6a4,2f56b313-12e5-61db-b562-63d222112ad9 ']'
+ '[' -n 11 ']'
++ /opt/xensource/bin/xe network-create 'name-label=Pool-wide network associated with eth0 on VLAN11'
+ VLAN_NETWORK=a8620ab8-8ed3-4c9a-b55a-4bb6209739ca
++ /opt/xensource/bin/xe vlan-create pif-uuid=7579afc5-134b-f2d3-e531-3752891bb6a4,2f56b313-12e5-61db-b562-63d222112ad9 network-uuid=a8620ab8-8ed3-4c9a-b55a-4bb6209739ca vlan=11
The uuid you supplied was invalid.
type: PIF
uuid: 7579afc5-134b-f2d3-e531-3752891bb6a4,2f56b313-12e5-61db-b562-63d222112ad9
+ VLAN_PIF=
#