Juju instances fail to boot when installing packages with debconf questions
Bug #937889 reported by
Benji York
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| pyjuju |
Fix Released
|
Critical
|
Clint Byrum | ||
Bug Description
Using a config like this:
type: ec2
default-series: precise
juju-origin: ppa
I run "juju bootstrap" and get a positive outcome. I then wait a bit and run "juju status" and get the SSH prompt to verify the fingerprint and after typing "yes" nothing happens.
Using oneiric, it works fine.
Related branches
lp:~clint-fewbar/pyjuju/use-packages-yaml
- Kapil Thangavelu (community): Approve
-
Diff: 173 lines (+23/-23)11 files modifiedjuju/providers/common/cloudinit.py (+3/-3)
juju/providers/common/tests/data/cloud_init_bootstrap (+2/-2)
juju/providers/common/tests/data/cloud_init_bootstrap_zookeepers (+2/-2)
juju/providers/common/tests/data/cloud_init_distro (+2/-2)
juju/providers/common/tests/data/cloud_init_normal (+2/-2)
juju/providers/common/tests/data/cloud_init_ppa (+2/-2)
juju/providers/ec2/tests/data/bootstrap_cloud_init (+2/-2)
juju/providers/ec2/tests/data/launch_cloud_init (+2/-2)
juju/providers/ec2/tests/data/launch_cloud_init_ppa (+2/-2)
juju/providers/orchestra/tests/data/bootstrap_user_data (+2/-2)
juju/providers/orchestra/tests/data/launch_user_data (+2/-2)
| Changed in juju: | |
| status: | New → Confirmed |
| importance: | Undecided → Critical |
Revision history for this message
| Clint Byrum (clint-fewbar) wrote | #1 |
| summary: |
- Hang on "juju status" with EC2 and Precise + Juju instances fail to boot when installing packages with debconf + questions |
| Changed in juju: | |
| status: | Confirmed → Triaged |
| milestone: | none → florence |
| Changed in juju: | |
| assignee: | nobody → Clint Byrum (clint-fewbar) |
| status: | Triaged → In Progress |
| Changed in juju: | |
| status: | In Progress → Fix Committed |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| Patrick Hetu (patrick-hetu) wrote | #2 |
To post a comment you must log in.
The original problem of juju failing on precise was caused because libc6 is upgraded during the apt-get -y install juju. The libc6 debconf questions caused a hang.
The appropriate solution is for juju to stop using runcmd to install itself, but instead use the appropriate yaml to designate packages and PPA's to utilize.