CI hates juju, maybe the feelings are mutual

[John Meinel]

Well you used to be able to request a downgrade, but it never actually
worked... :)
And with the new upgrade steps, we explicitly don't implement the 'back out
these changes' logic, which is why things were breaking some-of-the-time on
upgrade. I'm not sure what I broke, but it is possible I changed it from
"some-of-the-time" to "all-of-the-time" by some perverse logic. I'm pretty
sure I tested it locally.

I did try to upgrade a WP+MySQL environment from 1.16.6 to
lp:juju-core/1.18 (2266). And it failed but because of the WP charm
config-changed hook. This was the error:
2014-04-10 09:37:13 INFO config-changed E: Could not get lock
/var/lib/dpkg/lock - open (11: Resource temporarily unavailable)
2014-04-10 09:37:13 INFO config-changed E: Unable to lock the
administration directory (/var/lib/dpkg/), is another process using it?
2014-04-10 09:37:13 ERROR juju.worker.uniter uniter.go:475 hook failed:
exit status 100

After doing "juju resolved --retry wordpress/0" everything was happy.

I wonder if there is something in 1.18 that is causing apt commands to run
after upgrade, and that ends up racing with running the config-changed hook.

Are we careful to take out the FSLock when doing Apt commands from upgrade?

John
=:->




On Thu, Apr 10, 2014 at 8:16 AM, Curtis Hovey-Canonical <
curtis at canonical.com> wrote:

> I am exhausted, so I am sending out the barest summary of the Juju-CI
> problems I see.
>
> http://ec2-54-84-137-170.compute-1.amazonaws.com:8080/
> ^ In  general, if the test doesn't end in -devel or start with walk-,
> we require the test to pass.
>
> lp:juju-core/trunk r2593 could not upgrade because of an exception.
> Note that this rev precedes the rev that makes it impossible to
> downgrade. I see new revisions queue, may trunk will pass while I
> sleep
>
> lp:juju-core/1.18 r2264 and subsequent revscould not upgrade hp,
> joyent, azure, or aws. some of the agents failed to update. This
> results for the different CPC are consistent. I see the change relates
> to not permitting downgrades. Damn, I just submitted pull request
> documenting that you can downgrade.
>
> --
> Curtis Hovey
> Canonical Cloud Development and Operations
> http://launchpad.net/~sinzui
>
> --
> Juju-dev mailing list
> Juju-dev at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20140410/0709d02c/attachment-0001.html>