Comment 2 for bug 1666227

Steven Hardy (shardy) wrote :

> During minor update always calls os-net-config unconditionally and sometimes fails on empty config.json file.

Can you expand on the situation where this will happen?

All deployments should specify some config I think, so although we can fix this so os-net-config treats an empty file as a no-op, I just want to ensure we're not working around some underlying issue in the deployment workflow or ordering?