Canonical Juju

Public-hostname not recorded in controllers.yaml for a bootstrapped controller

Bug #2027550 reported by @les
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
Medium
Jack Shaw

Bug Description

When i bootstrap a new controller with the following configuration value `--config public-dns-address=$DNS:44` the public-hostname value is not recorded in `~/.local/share/juju/controller.yaml`.

However if i do `juju login <controller's dns>` that value is recorded.

Steps to reproduce:
1) bootstrap a controller: `juju bootstrap --config public-dns-address=$DNS:443 $CLOUD/$REGION $NAME`
2) check `~/.local/share/juju/controller.yaml` and note that the public-hostname value is not recorded for the new controller

I believe `environs/bootstrap/prepare.go` around line 255 is missing something like `details.PublicDNSName = args.ControllerConfig.PublicDNSAddress()`.

Best regards,
   Ales

Revision history for this message
Joseph Phillips (manadart) wrote :

Check 2.9 for this. If the bug is present there, that's where to fix and roll forward.

Update the milestone once presence in the version is verified.

Changed in juju:
status: New → Triaged
importance: Undecided → High
importance: High → Medium
assignee: nobody → Jack Shaw (jack-shaw)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.