[2.0] bootstrapping with a controller name containing a : character fails with no error message

Bug #1616922 reported by Larry Michel
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Expired
Medium
Unassigned

Bug Description

I tried to bootstrap with a controller name that had : and the bootstrap failed with no error message. It just destroyed the controller after bootstrap was completed. It's obviously a user error to attempt this name, but I think it should be handled with a descriptive error.

This is easily recreatable.

ii juju 2.0-beta15-0ubuntu1~14.04.1~juju1 all next generation service orchestration system
ii juju-2.0 2.0-beta15-0ubuntu1~14.04.1~juju1 amd64 Juju is devops distilled - client

juju bootstrap controller:vmware larry --config default-series=trusty --to varaha.oil
Creating Juju controller "controller:vmware" on larry
Bootstrapping model "controller"
Starting new instance for initial controller
Launching instance
 - 4y3kk3
Installing Juju agent on bootstrap instance
Preparing for Juju GUI 2.1.8 release installation
Waiting for address
Attempting to connect to 10.245.0.173:22
Warning: Permanently added '10.245.0.173' (ECDSA) to the list of known hosts.
Logging to /var/log/cloud-init-output.log on remote host
Running apt-get update
Running apt-get upgrade
Installing package: curl
Installing package: cpu-checker
Installing package: bridge-utils
Installing package: cloud-utils
Installing package: tmux
Fetching tools: curl -sSfw 'tools from %{url_effective} downloaded: HTTP %{http_code}; time %{time_total}s; size %{size_download} bytes; speed %{speed_download} bytes/s ' --retry 10 -o $bin/tools.tar.gz <[https://streams.canonical.com/juju/tools/agent/2.0-beta15/juju-2.0-beta15-trusty-amd64.tgz]>
Bootstrapping Juju machine agent
Starting Juju machine agent (jujud-machine-0)
Bootstrap agent installed
ERROR controller controller not found

Even with --debug there was no error message.

/var/lib/juju/nonce.txt does not exist
2016-08-23 17:42:37 DEBUG juju.provider.common bootstrap.go:330 connection attempt for 10.245.0.242 failed: Warning: Permanently added '10.245.0.242' (ECDSA) to the list of known hosts.
/var/lib/juju/nonce.txt does not exist
2016-08-23 17:42:42 DEBUG juju.provider.common bootstrap.go:330 connection attempt for 10.245.0.242 failed: Warning: Permanently added '10.245.0.242' (ECDSA) to the list of known hosts.
/var/lib/juju/nonce.txt does not exist
2016-08-23 17:42:47 DEBUG juju.provider.common bootstrap.go:330 connection attempt for 10.245.0.242 failed: Warning: Permanently added '10.245.0.242' (ECDSA) to the list of known hosts.
/var/lib/juju/nonce.txt does not exist
2016-08-23 17:42:52 DEBUG juju.provider.common bootstrap.go:330 connection attempt for 10.245.0.242 failed: Warning: Permanently added '10.245.0.242' (ECDSA) to the list of known hosts.
/var/lib/juju/nonce.txt does not exist
2016-08-23 17:42:58 DEBUG juju.provider.common bootstrap.go:330 connection attempt for 10.245.0.242 failed: Warning: Permanently added '10.245.0.242' (ECDSA) to the list of known hosts.
/var/lib/juju/nonce.txt does not exist
2016-08-23 17:43:03 DEBUG juju.utils.ssh ssh.go:292 using OpenSSH ssh client
Warning: Permanently added '10.245.0.242' (ECDSA) to the list of known hosts.
Logging to /var/log/cloud-init-output.log on remote host
Running apt-get update
Running apt-get upgrade
Installing package: curl
Installing package: cpu-checker
Installing package: bridge-utils
Installing package: cloud-utils
Installing package: tmux
Fetching tools: curl -sSfw 'tools from %{url_effective} downloaded: HTTP %{http_code}; time %{time_total}s; size %{size_download} bytes; speed %{speed_download} bytes/s ' --retry 10 -o $bin/tools.tar.gz <[https://streams.canonical.com/juju/tools/agent/2.0-beta15/juju-2.0-beta15-trusty-amd64.tgz]>
Bootstrapping Juju machine agent
Starting Juju machine agent (jujud-machine-0)
2016-08-23 17:44:29 INFO cmd cmd.go:129 Bootstrap agent installed
2016-08-23 17:44:29 INFO juju.cmd.juju.commands bootstrap.go:600 bootstrap failed but --keep-broken was specified so model is not being destroyed.
When you are finished diagnosing the problem, remember to run juju destroy-model --force
to clean up the model.
2016-08-23 17:44:29 ERROR cmd supercommand.go:458 controller mycontroller not found
2016-08-23 17:44:29 DEBUG cmd supercommand.go:459 (error details: [{github.com/juju/juju/cmd/juju/commands/bootstrap.go:713: } {github.com/juju/juju/cmd/modelcmd/modelcommand.go:144: } {github.com/juju/juju/jujuclient/file.go:108: controller mycontroller not found}])

Larry Michel (lmic)
summary: [2.0] bootstrapping with a controller name containing a : character
- fails
+ fails with no error message
Changed in juju:
status: New → Triaged
importance: Undecided → Medium
milestone: none → 2.0.1
tags: added: usability
Curtis Hovey (sinzui)
Changed in juju:
milestone: 2.0.1 → none
Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

This bug has not been updated in 5 years, so we're marking it Expired. If you believe this is incorrect, please update the status.

Changed in juju:
status: Triaged → Expired
tags: added: expirebugs-bot
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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