I was able to recreate the bug using a MAAS installation, but upon further investigation it appears that it is caused by the network splits and not MAAS environment specifically.
In this case, there are no os-xxx-networks defined and there are only single units deployed of each service. This result is a configuration which has an invalid https configuration.
I was able to recreate the bug using a MAAS installation, but upon further investigation it appears that it is caused by the network splits and not MAAS environment specifically.
In this case, there are no os-xxx-networks defined and there are only single units deployed of each service. This result is a configuration which has an invalid https configuration.