Unable to re-expose the controller charm after unexposing it
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- python
- Domain
- infrastructure
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.
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:
- Dominant language
- Python
- Stars
- 3
- Forks
- 21
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from juju/juju-controller
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
juju/juju-controller#155 ·
-
metrics-endpoint-relation-created hook fails with ValueError on k8s when bind_address returns service FQDNMay be free again @gfouillet claimed this 89 days ago, and no pull request is open. Open
juju/juju-controller#130 · 1 assignee ·
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
juju/juju-controller#112 · 10 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 40/100
juju/juju-controller#96 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
juju/juju-controller#93 ·
All issues in juju/juju-controller
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
snap-stanford/Biomni#380 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
microsoft/playwright-python#3361 ·
Maintainers usually reply within 1 day
-
documentation priority: low size: S status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
cubrid-lab/sqlalchemy-cubrid#1397 ·
Maintainers usually reply within 1 day
-
documentation priority: low size: S status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
cubrid-lab/pycubrid#1307 ·
Maintainers usually reply within 1 day
-
[Bug]: Installer hides SSL certificate errors as bare URLError, and the suggested fix can't workOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
ShaftHQ/chaosengine-harness#143 ·
Maintainers usually reply within 1 day