juju 1.17.5 RC cannot deploy to precise

[Curtis Hovey]

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.

[Curtis Hovey (sinzui)]

This is the log from my Hp bootstrap attempt. The meaningful part is

Running apt-get upgrade
Installing package: --target-release 'precise-update/cloud-tools' 'git'
2014-03-11 15:10:21 ERROR juju.provider.common bootstrap.go:123 bootstrap failed: rc: 1
Stopping instance...

Maybe we have a cloud tools issue? This does explain why the trusty deploys succeeded.

[Curtis Hovey (sinzui)]

I should be clear that this issue was observed by CI and as myself. I don't think CI's restrictive user setup is a factor.

[Curtis Hovey (sinzui)]

I don't see git in the archive:
    http://ubuntu-cloud.archive.canonical.com/ubuntu/pool/main/g/

This might be a case were juju assumes precise needs to get all its packages from the cloud tools archive

[Curtis Hovey (sinzui)]

A bootstrap of 1.17.4 of a precise instance only installs mongodb-server from cloud-tools

Running apt-get upgrade
Installing package: git
Installing package: cpu-checker
Installing package: bridge-utils
Installing package: rsyslog-gnutls
Installing package: --target-release 'precise-updates/cloud-tools' 'mongodb-server'

[Curtis Hovey (sinzui)]

Aaron ran r2402 though CI. It passed. The bad revision is r2403 (Cloudinit: Fixed target-release issue precise/maas).

[John A Meinel (jameinel)]

I thought that when I tested the "apt-get install" even if you gave a preferred archive, it didn't *require* the package to come from that archive. (it would pull it from another archive if it wasn't present in the cloud-archive).

Maybe this is an apt in precise vs trusty difference?

[John A Meinel (jameinel)]

Just to be clear, not all the packages are in cloud-tools today, but the goal was that if we ever did add one, it means we want to install that specific version, without having to recompile jujud to notice the new tool. (because we add the cloud tools archive at lower priority so it doesn't affect workloads, but anything *juju* installs should prefer the cloud tools archive.)

[John A Meinel (jameinel)]

Just to be clear, not all the packages are in cloud-tools today, but the goal was that if we ever did add one, it means we want to install that specific version, without having to recompile jujud to notice the new tool. (because we add the cloud tools archive at lower priority so it doesn't affect workloads, but anything *juju* installs should prefer the cloud tools archive.)

I just tried it again and it was happy:

juju deploy ubuntu
juju ssh 1
sudo apt-get install --target-release 'precise-updates/cloud-tools' bzr --target-release 'precise-updates/cloud-tools' mercurial
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  mercurial-common python-bzrlib
Suggested packages:
  bzr-doc bzr-gtk bzr-svn python-bzrlib.tests bzrtools qct wish kdiff3 tkdiff
  meld xxdiff python-mysqldb python-pygments python-kerberos python-gpgme
  python-bzrlib-dbg xdg-utils
The following NEW packages will be installed:
  bzr mercurial mercurial-common python-bzrlib
0 upgraded, 4 newly installed, 0 to remove and 7 not upgraded.
Need to get 3,777 kB of archives.
After this operation, 15.2 MB of additional disk space will be used.
Do you want to continue [Y/n]?

I'm sure those files are not in the cloud-tools archive, but it lets me say that I still prefer to install things from there if they are available.