Unable to re-expose the controller charm after unexposing it
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3
- Forks
- 19
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 8
Description
Hey team,
In my controller model, my controller charm was exposed by default. When I did juju status, I could see yes under column Exposed.
I was following the expose and unexpose docs.
After successfully "unexposing" my controller, I wanted to expose it again. I ran juju expose controller, which gave me the following error:
ERROR cannot expose a container application without a "juju-external-hostname" value set, run
juju config controller juju-external-hostname=<value>
However, my controller config nevere had juju-external-hostname set to begin with. If I run juju config juju-external-hostname, I don't see it there.
My questions are:
- How was the controller charm exposed in the first place without a
juju-external-hostname? - If this value was never set and yet exposing the controller worked before, how come I'm not able to re-expose the controller again with an empty value?
- If I set the value to some made up value e.g. "foo", the exposition works. Why?
- Also, can I ask why it's necessary for the controller to be exposed by default.
Thank you!
Related issues:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the expose and unexpose documentation linked in the issue, then trace the behavior of juju expose controller and juju config controller juju-external-hostname. Compare the controller's initial exposed state with its state after unexposing, including the empty configuration case. Done means the cause and expected behavior are established and the issue is corrected or documented clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100