enable-os-refresh-update config option causes bootstrap to take significantly longer than without it.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Expired
|
High
|
Unassigned |
Bug Description
Use of the "enable-
In a bit of irony, I started using this option for faster machine provisioning as indicated is possible in the docs:
https:/
With, and without the config option specified, the controller machine instance is ready and accessible within 2 minutes. In the case where the config option is set true, there is nothing bound to tcp socket 17070 until the final moments of bootstrap success, confirmed by watching `sudo netstat -taupn` on the controller instance.
## Reproducer:
#### Without the option
time juju bootstrap --bootstrap-
#### With the option
time juju bootstrap --bootstrap-
## Reproducer Output:
#### Without the option (2 min)
ubuntu@
Creating Juju controller "beisner-
Looking for packaged Juju agent version 2.1.2 for amd64
Launching controller instance(s) on serverstack/
- 85f4404f-
Fetching Juju GUI 2.5.2
Waiting for address
Attempting to connect to 10.5.0.9:22
Warning: Permanently added '10.5.0.9' (ECDSA) to the list of known hosts.
sudo: unable to resolve host juju-ab1b24-
Logging to /var/log/
Running apt-get update
Running apt-get upgrade
Installing curl, cpu-checker, bridge-utils, cloud-utils, tmux
Fetching Juju agent version 2.1.2 for amd64
Installing Juju machine agent
Starting Juju machine agent (service jujud-machine-0)
Bootstrap agent now started
Contacting Juju controller at 10.5.0.9 to verify accessibility...
Bootstrap complete, "beisner-
Controller machines are in the "controller" model.
Initial model "default" added.
real 2m0.794s
user 0m1.256s
sys 0m0.080s
## Reproducer Output:
#### With the option (21 min)
130 ubuntu@
Creating Juju controller "beisner-
Looking for packaged Juju agent version 2.1.2 for amd64
Launching controller instance(s) on serverstack/
- 2fb722cf-
Fetching Juju GUI 2.5.2
Waiting for address
Attempting to connect to 10.5.0.13:22
Warning: Permanently added '10.5.0.13' (ECDSA) to the list of known hosts.
sudo: unable to resolve host juju-8873d0-
Logging to /var/log/
Running apt-get upgrade
Installing curl, cpu-checker, bridge-utils, cloud-utils, tmux
Fetching Juju agent version 2.1.2 for amd64
Installing Juju machine agent
Starting Juju machine agent (service jujud-machine-0)
Bootstrap agent now started
Contacting Juju controller at 10.5.0.13 to verify accessibility...
Bootstrap complete, "beisner-
Controller machines are in the "controller" model.
Initial model "default" added.
real 21m43.145s
user 0m1.780s
sys 0m0.132s
Changed in juju: | |
milestone: | 2.2-beta4 → none |
It would be very useful to see the cloud-init.log and cloud-init- output. log files from both scenarios. This will tell us exactly what apt related update settings got passed through to cloud-init, and how cloud-init reacted to those. Both of these should be available in /var/log/cloud-init