juju 1.17.5 RC cannot deploy to precise
Bug #1290890 reported by
Curtis Hovey
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
Critical
|
Wayne Witzel III |
Bug Description
juju RC cannot deploy to precise on aws, hp, azure, local, manual. It can deploy to trusty. I can upgrade from stable to RC. The current revision is broken. The last successful revision was r2398. There isn't anything meaningful in the logs.
1.17.4 only tried to install mongodb-server from cloud-tools. The rc tried to install git from cloud tools. The new behaviour was introduced by r2403.
Related branches
lp:~wwitzel3/juju-core/lp-1290890-revert-2403
- Juju Engineering: Pending requested
-
Diff: 198 lines (+44/-50)5 files modifiedcloudinit/cloudinit_test.go (+15/-8)
cloudinit/options.go (+12/-10)
environs/cloudinit/cloudinit.go (+15/-21)
environs/cloudinit/cloudinit_test.go (+0/-8)
provider/ec2/local_test.go (+2/-3)
Changed in juju-core: | |
assignee: | nobody → Wayne Witzel III (wwitzel3) |
status: | Triaged → In Progress |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
This is the log from my Hp bootstrap attempt. The meaningful part is
Running apt-get upgrade update/ cloud-tools' 'git' common bootstrap.go:123 bootstrap failed: rc: 1
Installing package: --target-release 'precise-
2014-03-11 15:10:21 ERROR juju.provider.
Stopping instance...
Maybe we have a cloud tools issue? This does explain why the trusty deploys succeeded.