group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1629376@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package juju-core - 2.0.0-0ubuntu0.16.04.2

---------------
juju-core (2.0.0-0ubuntu0.16.04.2) xenial; urgency=medium

  * DPKG_MAINTSCRIPT_ARCH doesn't work in .config, use dpkg check (LP:
#1614969)

 -- Nicholas Skaggs <nicholas.skaggs@xxxxxxxxxxxxx>  Mon, 31 Oct 2016
15:55:49 -0400

** Changed in: juju-core (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1629376

Title:
  Juju should use bundled jujud if not matching agents found in streams

Status in juju:
  Invalid
Status in juju-core package in Ubuntu:
  Fix Released
Status in juju-core source package in Xenial:
  Fix Released

Bug description:
  Since --upload-tools is now no longer needed, juju needs to fallback
  to using bundled jujud in the case where no matching agents are found
  in streams. For example,

  6:38:07 INFO  juju.environs.manual init.go:120 series: zakkety, characteristics: arch=amd64 cpu-cores=1 mem=3855M
  ..
  16:38:07 INFO  cmd cmd.go:129 Looking for packaged Juju agent version 2.0-beta18 for amd64
  ...
  16:38:08 INFO  juju.environs.bootstrap tools.go:74 found 15 packaged agent binaries
  ..
  16:38:08 ERROR cmd supercommand.go:458 failed to bootstrap model: no matching tools available
  16:38:08 DEBUG cmd supercommand.go:459 (error details: [{github.com/juju/juju/cmd/juju/commands/bootstrap.go:738: failed to bootstrap model} {github.com/juju/juju/tools/list.go:19: no matching tools available}])

  In this example, beta18 is a released version, and 15 agents are
  found. However, none of them match my crazy series. Juju should still
  use the bundled agent automatically. Note, passing --build-agent
  requires me to rebuild an agent in this case; not something I
  can/should need to do on a client machine.

  [SRU Information]

  [Impact]
  The autopkgtest for future-manual-provider ensuring juju works with the next release before a juju update will be disabled per the bug.

  [Verification]
  The autopkgtest future-manual-provider should now be skipped with
  SKIP: Juju won't bootstrap unknown without published agent (LP:1629376)

  [Regression Potential]
  None. The package won't make it out of proposed, as the test will currently fail as-is.

  [Other]
  This should have no impact on end users of the package; the verification can be done by viewing the test results under http://autopkgtest.ubuntu.com/packages/j/juju-core/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/1629376/+subscriptions