[Bug 1545913] Re: [FFe] juju-core 2.0

The proposed packaging updates are now available in Adam's PPA: This includes: * Switch from golang-go.net-dev to golang-x-net-dev as mentioned by ~jdstrand * Use of Suggests to keep Juju 1.X tools around through upgrade from

[Bug 1564670] [NEW] After upgrade Juju 1.X should still be the default

Public bug reported: When upgrading to Xenial the new default Juju version is going to be 2.0. Because 2.0 clients are not compatible with 1.X environments, this means existing environments will be inaccessible unless the 1.X client is switched to. The plan is to give a warning when creating

[Bug 1564662] [NEW] Juju binaries should be stripped

Public bug reported: Previously the juju team has been asked to strip the go binaries in the distro packaging. Per bug 1265970 that was not possible as with go 1.2 it introduced bugs such as bug 1200255. With go 1.6 in xenial, it may now be safe to strip the juju binaries, but this needs testing

[Bug 1545913] Re: [FFe] juju-core 2.0

I've edited the bug the clarify the juju-mongodb situation. There's a change to both tweak the version of mongodb and make the unit tests more reliable, which was held from landing for beta3 waiting on the package in ubuntu. It will be included in the rc. -- You received this bug notification

[Bug 1545913] Re: [FFe] juju-core 2.0

** Description changed: The juju team is requesting an FFE for juju-core. Juju2 represents API changes and new features and bugfixes for juju. We are NOT requesting a place on any image for xenial. This FFE is intended to cover the acceptance of the updated juju-core package, as well as

[Bug 1545913] Re: [FFe] juju-core 2.0

Updated the description with the example upgrade testing using the test packages in the ppa. ** Description changed: The juju team is requesting an FFE for juju-core. Juju2 represents API changes and new features and bugfixes for juju. We are NOT requesting a place on any image for

[Bug 1560315] Re: [needs packaging] juju2 beta is not in xenial

Hm, looks like the adventures with reworking the packaging yesterday (which I didn't follow the reasoning behind, but ended up basing the beta2 packaging branch on an existing xnox branch) lost the Build- Depends we had on archive golang packages. What we had:

[Bug 1557830] Re: [needs-packaging] juju-mongodb2.6 in xenial, wily, and trusty

> Ubuntu mongodb 1:2.6.10-0ubuntu1 introduced --use-system-v8, but you haven't > carried this forward. Is this expected (not described in changelog)? Perhaps > it > is because of --disable-scripting but I'm not sure. Indeed. We have always built juju-mongodb without the javascript engine because

[Bug 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo, golang

"Are you saying you want to use the embedded code copy? Has anyone looked at the testsuite issue to fix it? Embedded code copies should be avoided at all costs per MIR guidelines -- we are making huge concessions for the juju and lxd teams already, can someone take a look at this ftbfs and report

[Bug 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo, golang

> * golang-go.crypto > - needs a bug subscriber Looks like it's ~ubuntu-server now. > * golang-gocheck > - can be dropped when bug #1504821 is fixed (comment #82) > * golang-goyaml > - can be dropped when bug #1504821 is fixed (comment #82) To clarify, I am making these changes on master.

[Bug 1500981] Re: juju-db segfault while syncing with replicas

This package hasn't changed in trusty in more than a year.

[Bug 1330504] Re: strongSwan 5.1.3

** Project changed: strongswan = obsolete-junk ** No longer affects: obsolete-junk -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to strongswan in Ubuntu. https://bugs.launchpad.net/bugs/1330504 Title: strongSwan 5.1.3 To manage

[Bug 1393825] [NEW] Juju testsuite fails in random ways

Public bug reported: Two parts of the juju-core test suite panic or segfault when run with -compiler gccgo on amd64. Some examples, in provider/openstack: ubuntu@go:~/go/src/github.com/juju/juju$ (cd provider/openstack/ go test ./... -compiler gccgo -gocheck.v -v) 3 === RUN Test ... PASS:

[Bug 1381671] Re: reboot tests fail to build on gccgo

Status: Triaged = In Progress ** Changed in: juju-core Assignee: (unassigned) = Martin Packman (gz) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to gccgo-go in Ubuntu. https://bugs.launchpad.net/bugs/1381671 Title

[Bug 1381671] Re: reboot tests fail to build on gccgo

** Changed in: juju-core Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to gccgo-go in Ubuntu. https://bugs.launchpad.net/bugs/1381671 Title: reboot tests fail to build on gccgo To manage

[Bug 1248283] Re: juju userdata should not restart networking

** Changed in: juju-core Milestone: 1.20.0 = 1.18.0 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1248283 Title: juju userdata should not restart networking To manage

[Bug 1268913] Re: Loading state on bootstrap ignores ssl-hostname-verification setting

Now merged in Curtis, thanks. ** Changed in: juju-core Status: In Progress = Fix Committed ** Changed in: juju-core Milestone: 1.18.0 = 1.17.4 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu.

[Bug 1261628] Re: remove-* aliases for destroy-service and destroy-machine

** Changed in: juju-core Status: In Progress = Fix Committed ** Changed in: juju-core Milestone: 1.18.0 = 1.17.4 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1261628

[Bug 1267913] Re: juju relation-list doesn't report full units list when unit is down

** Changed in: juju-core Milestone: 1.17.1 = 1.18.0 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1267913 Title: juju relation-list doesn't report full units list when unit

[Bug 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails

** Changed in: juju-core Milestone: 1.17.1 = 1.18.0 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1248283 Title: Juju deploy of Charm in MAAS fails because dbus fails To

[Bug 1250007] Re: Bootstrapping azure causes memory to fill

** Changed in: juju-core Milestone: 1.17.1 = 1.18.0 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1250007 Title: Bootstrapping azure causes memory to fill To manage

[Bug 1129720] Re: juju instances not including the default security group

I'm not sure adding the default group is the right fix for wanting ad- hoc per environment rules. I'd prefer if juju started tolerating external tampering with the environment-specific juju group it adds to all machines it creates. We could potentially report via status any addition ports opened.

[Bug 1243861] Re: juju should add the cloud-archive repository differently

Milestone: None = 1.17.0 ** Changed in: juju-core Assignee: (unassigned) = Martin Packman (gz) ** Branch linked: lp:~gz/juju-core/1.16_cloud_archive_key ** Branch linked: lp:~gz/juju-core/cloud_archive_key ** Changed in: juju-core/1.16 Importance: Undecided = High ** Changed in: juju

[Bug 1243861] Re: juju should add the cloud-archive repository differently

** Changed in: juju-core/1.16 Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1243861 Title: juju should add the cloud-archive

[Bug 1182898] Re: Please support `juju --version`

** Changed in: juju-core Milestone: None = 1.11.1 ** Changed in: juju-core Assignee: (unassigned) = John A Meinel (jameinel) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu.

[Bug 1197745] [NEW] Rackspace authentication no longer supported

Public bug reported: I have my rackspace credentials sourced in my local environment, and nova can no longer authenticate against the rackspace cloud. $ nova --debug list DEBUG (shell:768) 'NoneType' object has no attribute 'authenticate' Traceback (most recent call last): File

[Bug 1178506] Re: Cannot switch between juju-0.7 and juju-core

You need to install juju-core from the archive, the 1.10 release in raring is what we introduced the update-alternatives parts on. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu.

[Blueprint servercloud-s-juju-contributor-onramp] Juju Contributor Onramp

Blueprint changed by Martin Packman: Work items changed: Work items for ubuntu-13.04-month-6: [jorge] Contribute to this charm! link in the charm store.: BLOCKED [jorge] Tell people they can help. There's no mention of how to help on jujucharms.com. That sucks. Not make something and get

[Bug 1167921] Re: Feature freeze exception for python juju 0.7 in raring

Updated with changes from further review by Iain Lane and Stéphane Graber. ** Patch added: debdiff juju_0.6-1ubuntu1.dsc juju_0.7-0ubuntu1.dsc https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1167921/+attachment/3650489/+files/juju-0.7.debdiff -- You received this bug notification

[Bug 1167921] [NEW] Feature freeze exception for python juju 0.7 in raring

Public bug reported: The new upstream 0.7 release of juju should be included in raring. This is required for: * A number of bug fixes, and features serialisation of hook execution and UUIDs for environments * Packaging changes to make the go juju port coinstallable * Fix to regression in lxc

[Bug 1167921] Re: Feature freeze exception for python juju 0.7 in raring

As this is a new major version, seemed worth playing it safe. The main changes are new features, with potential compatibility concerns, and for instance the orchestra provider was removed entirely in this release. There is a review in progress on the packaging updates, once all the points are

[Bug 1167921] Re: Feature freeze exception for python juju 0.7 in raring

** Patch added: debdiff juju_0.6-1ubuntu2.dsc juju_0.7-0ubuntu1.dsc https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1167921/+attachment/3640697/+files/juju_0.6_to_0.7.diff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in

[Bug 1167921] Re: Feature freeze exception for python juju 0.7 in raring

Apologies, the last version I had of the packaging had not been propagated to raring. See new diff for current raring package to the proposed. ** Patch added: debdiff juju_0.6-1ubuntu1.dsc juju_0.7-0ubuntu1.dsc

[Bug 1130809] Re: lxc scripts break when user has PYTHONPATH set

** Changed in: juju (Ubuntu) Status: Triaged = In Progress ** Changed in: juju (Ubuntu) Assignee: (unassigned) = Martin Packman (gz) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net

[Bug 1130809] Re: lxc scripts break when user has PYTHONPATH

** Summary changed: - lxc-ls crashed with SIGABRT in Py_FatalError() + lxc scripts break when user has PYTHONPATH ** Summary changed: - lxc scripts break when user has PYTHONPATH + lxc scripts break when user has PYTHONPATH set ** Description changed: - Occurred when deploying the juju mysql

[Bug 1130809] Re: lxc scripts break when user has PYTHONPATH set

I'm unconvinced this is a problem with the use of lxc in juju as opposed to a general issue with the lxc scripts. ** Changed in: juju Status: New = Incomplete ** Also affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are

[Bug 1061678] Re: OpenStack provider should fall back to local-ipv4 if public-ipv4 is not found

** Changed in: juju/0.5 Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1061678 Title: OpenStack provider should fall back to local-ipv4 if

[Bug 1068566] Re: Juju 0.6 incompatible with MAAS in precise

** Changed in: juju/0.6 Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1068566 Title: Juju 0.6 incompatible with MAAS in precise To manage

[Bug 1064734] Re: ERROR Invalid 'tags' constraint 'set(['test-tag'])': No such tag using maas-tags to deploy with juju

** Changed in: juju/0.6 Status: Fix Committed = Fix Released ** Changed in: juju Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu.

[Bug 1061678] Re: OpenStack provider should fall back to local-ipv4 if public-ipv4 is not found

** Changed in: juju/0.5 Status: Triaged = Fix Committed ** Changed in: juju/0.5 Assignee: (unassigned) = Martin Packman (gz) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs

[Bug 1154803] Re: Constraints prevents the allocation of nodes if they are equal to the HW.

Are you certain this is related to the cpu constraint, rather than any of the others you had set? The logic there with respect to floats and gte is correct, there are tests in the codebase for that aspect. Please try the following: 1) `juju destroy-environment` 2) `juju bootstrap` 3) `juju

[Bug 1064734] Re: ERROR Invalid 'tags' constraint 'set(['test-tag'])': No such tag using maas-tags to deploy with juju

** Changed in: juju/0.6 Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1064734 Title: ERROR Invalid 'tags' constraint 'set(['test-tag'])':

[Bug 1068566] Re: Juju 0.6 incompatible with MAAS in precise

** Changed in: juju/0.6 Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1068566 Title: Juju 0.6 incompatible with MAAS in precise To manage

[Bug 1044503] Re: kernel command line is not easily customizable

With the landing of the rollup branch, all the parts needed for this should now be on trunk: https://code.launchpad.net/~jameinel/maas/land-kernel-opts-in-trunk/+merge/133434 ** Changed in: maas Status: Triaged = Fix Committed -- You received this bug notification because you are a

[Bug 1064638] Re: Commissioning is failing to set node memory attribute

** Also affects: maas Importance: Undecided Status: New ** Changed in: maas Status: New = Fix Released ** Changed in: maas Importance: Undecided = Critical ** Changed in: maas Assignee: (unassigned) = Jelmer Vernooij (jelmer) -- You received this bug notification

[Bug 1068566] Re: Juju 0.6 incompatible with MAAS in precise

** Changed in: juju/0.6 Status: Confirmed = In Progress ** Changed in: juju/0.6 Assignee: (unassigned) = Martin Packman (gz) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs

[Bug 1068566] Re: Juju 0.6 incompatible with MAAS in precise

** Changed in: juju Status: Confirmed = Fix Committed ** Changed in: juju Milestone: None = 0.7 ** Changed in: juju Assignee: (unassigned) = Martin Packman (gz) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju

[Bug 966617] Re: supply high level design documents

** Also affects: juju-core Importance: Undecided Status: New ** Changed in: juju-core Importance: Undecided = High ** Changed in: juju-core Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to

[Bug 802117] Re: juju ssh/scp commands cause spurious key errors, should use a different known_hosts file

** Also affects: juju-core Importance: Undecided Status: New ** Changed in: juju-core Importance: Undecided = Medium ** Changed in: juju-core Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to

[Bug 966617] Re: supply high level design documents

** No longer affects: juju-core -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/966617 Title: supply high level design documents To manage notifications about this bug go to:

[Bug 1068566] Re: Juju 0.6 incompatible with MAAS in precise

** Also affects: juju/0.6 Importance: Undecided Status: New ** Changed in: juju/0.6 Importance: Undecided = Critical ** Changed in: juju/0.6 Status: New = Confirmed ** Changed in: juju/0.6 Milestone: None = 0.6.1 ** Changed in: juju Status: New = Confirmed --

[Bug 1064734] Re: ERROR Invalid 'tags' constraint 'set(['test-tag'])': No such tag using maas-tags to deploy with juju

** Changed in: juju Status: Triaged = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1064734 Title: ERROR Invalid 'tags' constraint 'set(['test-tag'])': No such

[Bug 1062340] Re: juju provider interacts poorly with arch constraints

** Also affects: maas (Ubuntu) Importance: Undecided Status: New ** No longer affects: maas (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1062340 Title: juju

[Bug 1054096] Re: Openstack folsom compatibility

So, what specifically is broken so I can update the api usage? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1054096 Title: Openstack folsom compatibility To manage notifications

[Bug 1012854] Re: cloud-config should support simple file writing

Looks pretty good Josh, are you going to propose that branch for merging? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1012854 Title: cloud-config should support simple file

[Bug 1000710] [NEW] Attaching volume during instance boot doesn't work

Public bug reported: Using the newly enabled volume support on canonistack, it arrived at a state where the volume believed it was in-use by the instance, but the instance had not registered it. The volume then refused to be detached from the instance, the command succeeded but no change

[Bug 1000710] Re: Attaching volume during instance boot doesn't work

** Description changed: Using the newly enabled volume support on canonistack, it arrived at a state where the volume believed it was in-use by the instance, but the instance had not registered it. The volume then refused to be detached from the instance, the command succeeded but no