On Jul 28, uosci was able to deploy Wily @ Juju 1.24.2. Granted, that was with older Wily images and perhaps older systemd, so it may or may not be helpful information at this point.
Here is that successful amulet test output from the trusty/ubuntu charm, which exercises all currently-supported Ubuntu releases (+ current dev Ubuntu release): charm_amulet_test/5429: http://paste.ubuntu.com/12193551/ I think it may be of interest to begin cycling the trusty/ubuntu charm's amulet test in Juju CI as an easy way to do a really basic and quick functional check. ie. grab lp:charms/trusty/ubuntu, then make functional_test. The tests are maintained and validated as Ubuntu releases come and go. Note that tests are only added and enabled for Ubuntu dev versions after confirming that they pass for that version. http://bazaar.launchpad.net/~charmers/charms/trusty/ubuntu/trunk/files/head:/tests/ The Ubuntu charm is, and is intended to be, a minimal hookless nothing. That makes it attractive for inexpensive general validation of test automation, environments, tooling and such (which is uosci's specific interest in it). That could also make it attractive for testing Ubuntu releases vs. Juju releases. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1480310 Title: systemctl link request failed for service FOO: Unit name FOO is not valid. Status in juju-core: Triaged Status in systemd package in Ubuntu: Fix Released Bug description: As seen in http://reports.vapour.ws/releases/2936/job/local-deploy-wily-amd64/attempt/136 Juju cannot bootstrap on wily because ERROR juju.service.systemd service.go:149 dbus link request failed for service "juju-db-jenkins-local-deploy-wily-amd64": Unit name /var/lib/juju/init/juju-db-jenkins-local-deploy-wily-amd64/juju-db-jenkins-local-deploy-wily-amd64.service is not valid. This error first occurred after the wily-slave got package updates. The released jujus get the same errors as the jujus under test. This issue is probably an Ubuntu packaging break. I am making the test non-voting since we can see table 1.24.3 no longer works. To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1480310/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
