This bug is still tugging at the back of my brain. I tried breaking my dns, both by shutting down my serverstack dns helper, and by simply choosing a canonical name that wasn't mapped in my bastion. In both cases, apache started, and the files were written correctly to disk. "Correctly" means that they were labelled and referenced by the canonical name that I set in the config.
I also tried reverting a minor patch that I had made to context.py, and that did not make any difference, either.
It would make me feel better to have a repro case, because my theory about it being due to broken dns is looking increasingly unlikely. It doesn't look like this is trivial to repro in my environment, however.
This bug is still tugging at the back of my brain. I tried breaking my dns, both by shutting down my serverstack dns helper, and by simply choosing a canonical name that wasn't mapped in my bastion. In both cases, apache started, and the files were written correctly to disk. "Correctly" means that they were labelled and referenced by the canonical name that I set in the config.
I also tried reverting a minor patch that I had made to context.py, and that did not make any difference, either.
It would make me feel better to have a repro case, because my theory about it being due to broken dns is looking increasingly unlikely. It doesn't look like this is trivial to repro in my environment, however.