Juju requires outbound network on first run, packaging has recoverable errors

[Curtis Hovey]

As seen at
    http://reports.vapour.ws/releases/issue/57e1469d749a56354cda100a

HOME=debian/home /workspace/juju-core-2.0-rc1/src/github.com/juju/juju/scripts/generate-docs.py man -o juju.1
Since Juju 2 is being run for the first time, downloading latest cloud information.
Fetching latest public cloud list...
error: not found
error: not found

^ A successful creation of the man page will fetch the new clouds and show what it found. This failed because of a Juju/network hiccup. Ubuntu does not permit outbound network to build a package. Juju could have recognised that it was in a non-interactive session or it needs an option to STFU and JFDI.

[Nicholas Skaggs (nskaggs)]

We should include a test to ensure a launchpad build will work (offline, etc)

[Curtis Hovey (sinzui)]

This is not blocker for releases. We can see that Juju *is* trying to go outbound, it fails, we still get a man page. Juju should not be trying to do this, or the package rules need a change to to ensure juju stays offline during the build

HOME=debian/home /«PKGBUILDDIR»/src/github.com/juju/juju/scripts/generate-docs.py man -o juju.1
Since Juju 2 is being run for the first time, downloading latest cloud information.
Fetching latest public cloud list...
error: Get https://streams.canonical.com/juju/public-clouds.syaml: dial tcp 91.189.88.141:443: getsockopt: connection timed out
...
dh_link -pjuju-2.0 usr/lib/juju-2.0/bin/juju usr/bin/juju
dh_link -pjuju-2.0 usr/lib/juju-2.0/bin/jujud usr/bin/jujud
dh_link -pjuju-2.0 usr/lib/juju-2.0/bin/juju-metadata usr/bin/juju-metadata
dh_link -pjuju-2.0 usr/lib/juju-2.0/bin/juju-upgrade-mongo usr/bin/juju-upgrade-mongo
dh_link -pjuju-2.0 usr/lib/juju-2.0/man/man1/juju.1.gz usr/share/man/man1/juju.1.gz
dh_link -pjuju-2.0 usr/lib/juju-2.0/man/man1/juju.1.gz usr/share/man/man1/juju-2.0.1.gz

[Torsten Baumann (torbaumann)]

workaround in place

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 5 years, so we're marking it Expired. If you believe this is incorrect, please update the status.