Comment 1 for bug 1856617

When a subcloud is managed, this results in the certificates being propagated down to that subcloud. This in turn triggers force-applying the runtime manifest, which will generate hieradata for all nodes, even if the nodes have not been inventoried (by sysinv-agent) yet. This hieradata will have an incomplete interface configuration, with only the loopback interface present.

When those nodes (that were previously not inventoried) finish installing and come up the first time, they will check for the existence of the hieradata, and because it exists, try applying it. This will update the network config with only the loopback interface present, resulting in the node going offline and losing all network connectivity.