MAAS

  1. Bug #2011853
  2. Comment #0

Comment 0 for bug 2011853

Revision history for this message
jjqq (jjqq) wrote : subnet fabric

There is a use case:
- MAAS's DHCP is disabled, and an external DHCP sever is used for PXE boot.
- MAAS has 2 nics, named nic1, nic2. The nic2 is actually the one used for provisioning.
- MAAS based on the nic name order, created fabric-0, fabric-1 for them respectively. The fabric-1 is actually the one used for provisioning, while default fabric is fabric-0 which is almost usless.
- Commission a node, the node get an ip, the node UI shows its IP as "Auto assigned".
- MAAS detected the ip is bound coming from nic2 so it set the node's fabric=1 (more precisely, set vlan_id = id of untagged vlan of fabric-1)
- MAAS found the ip is not belonging to any existing subnets, so it automatically create a subnet, but it always create the subnet on fabric-0. This is the begining of all wrong things later.
- Deploy the node, also succeeded, when finished, it is node UI shows ip correctly
- Release the node, then the node status shows "Node must be attached to a network", this is because it could not find a proper subnet in fabric-1.
- The node become unavailable for Deploying unless Commission again.

I have confirmed this issue in 2.5.1 and fixed it successfully in https://github.com/maas/maas/pull/20/files, but could not create PR in launchpad (I have forked in lanchpad, git+ssh://<email address hidden>/~jjqq/maas, my branch name is james-create-discovered-subnet-in-correct-fabric).