Public bug reported: The current-manual-provider test passes everywhere, which relies on setting up a state server in place in the same test vm. However, on armhf only the future-manual-provider variant, which first munges the machine series to emulate the next development release, fails.
<http://autopkgtest.ubuntu.com/packages/j/juju-core/> <https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-xenial/xenial/armhf/j/juju-core/20160415_091616@/log.gz> 357bb2f3e2cfa9d7c28aff2ac22beb403ddb5bf2d249522016014df25584db3b /var/lib/juju/tools/2.0-beta4.1-yenial-armhf/tools.tar.gz 2016-04-15 09:15:57 INFO juju.cmd supercommand.go:60 running jujud [2.0-beta4.1 gc go1.6.1] 2016-04-15 09:15:57 DEBUG juju.agent agent.go:524 read agent config, format "1.18" 2016-04-15 09:15:57 INFO juju.network network.go:351 setting prefer-ipv6 to false 2016-04-15 09:16:01 INFO juju.agent identity.go:22 writing system identity file 2016-04-15 09:16:01 DEBUG juju.cmd.jujud bootstrap.go:322 starting mongo 2016-04-15 09:16:01 DEBUG juju.cmd.jujud bootstrap.go:347 calling ensureMongoServer 2016-04-15 09:16:01 INFO juju.mongo mongo.go:394 Ensuring mongo server is running; data directory /var/lib/juju; port 37017 2016-04-15 09:16:01 INFO juju.mongo mongo.go:559 installing [juju-mongodb3.2] 2016-04-15 09:16:01 INFO juju.utils.packaging.manager utils.go:57 Running: apt-get --option=Dpkg::Options::=--force-confold --option=Dpkg::options::=--force-unsafe-io --assume-yes --quiet install juju-mongodb3.2 2016-04-15 09:16:02 ERROR juju.utils.packaging.manager utils.go:103 packaging command failed: encountered fatal error: unable to locate package; cmd: "apt-get --option=Dpkg::Options::=--force-confold --option=Dpkg::options::=--force-unsafe-io --assume-yes --quiet install juju-mongodb3.2"; output: Reading package lists... Building dependency tree... Reading state information... E: Unable to locate package juju-mongodb3.2 E: Couldn't find any package by glob 'juju-mongodb3.2' E: Couldn't find any package by regex 'juju-mongodb3.2' This is a product of two deliberate choices. Firstly, per bug 1557852 we don't build juju-mongodb3.2 on 32 bit arches. Secondly, juju will only try to install the latest mongodb in post-xenial series. This is the given logic in github.com/juju/juju/mongo/mongo.go packagesForSeries: func packagesForSeries(series string) ([]string, []string) { switch series { case "precise", "quantal", "raring", "saucy", "centos7": return []string{"mongodb-server"}, []string{} case "trusty", "wily", "xenial": return []string{JujuMongoPackage}, []string{"juju-mongodb"} default: // y and onwards return []string{JujuMongoPackage}, []string{} } } The test should either be skipped on armhf or we need a way to access another arch to setup a state server for the armhf client to talk to. ** Affects: juju-core (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1571072 Title: autopkgtest future-manual-provider fails on armhf for 2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1571072/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
