Hello!
Please remember that the node allowance is dynamic. Here’s an example:
- NP sets the node allowance to 5.
- NP onboards 3 nodes.
- Node allowance dynamically reduces to 2.
- NP onboards 2 more.
- Node allowance dynamically becomes 0.
- One node has an issue and is removed from the registry.
- Node allowance dynamically increases to 1.
- NP tries to onboard it, but something goes wrong. The node is in the registry (has a principal on the dashboard), but has an issue still. Node allowance is back to 0.
- NP fixes the issue and needs to reonboard again to reinstall the OS.
Here’s where it gets tricky…
- If the BMC hasn’t changed and the IPv6 hasn’t changed, then the NP should be able to onboard without doing anything else. The registry should recognize the IPv6, know that it’s the same server, and allow the new registration to replace the old one.
- But if something has changed the BMC or the IPv6, then the registry will not know it’s the same server. It will refuse to allow the node to register because the node allowance is 0. In this case, the NP can maually use DFX to remove the registry entry, which will result in the node allowance becoming 1 again.
So this is why the node allowance is back to 0, because all 3 are in the registry.