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

[Martin Packman]

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 occurred.

The sequence of events was:
* Start instance
* Create volume
* Wait till instance was listed as ACTIVE
* Attach volume
* SSH to instance... fails, instance not yet booted enough
* Wait more
* SSH to instance
* dmesg contains nothing about volume

The suggestion is the attach happened to soon in the boot process.

To recover, did:
* Reboot instance
* Wait till instance is listed as ACTIVE and can SSH to it
* Volume is now back to being available
* Attach volume
* dmesg contains information about the new volume

** Affects: nova (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: canonistack

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1000710

Title:
  Attaching volume during instance boot doesn't work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1000710/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

** 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 change occurred.
  
  The sequence of events was:
- * Start instance
+ * Start instance (using ubuntu-precise-12.04-i386-server-20120424 image)
  * Create volume
- * Wait till instance was listed as ACTIVE
+ * Wait till instance was listed as ACTIVE (volume was also available at this 
point)
  * Attach volume
  * SSH to instance... fails, instance not yet booted enough
- * Wait more
+ * Wait more (took quite a long time)
  * SSH to instance
  * dmesg contains nothing about volume
  
  The suggestion is the attach happened to soon in the boot process.
  
  To recover, did:
  * Reboot instance
  * Wait till instance is listed as ACTIVE and can SSH to it
  * Volume is now back to being available
  * Attach volume
  * dmesg contains information about the new volume

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1000710

Title:
  Attaching volume during instance boot doesn't work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1000710/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

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 writing

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1012854/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

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 xenial. This FFE is intended to cover the
  acceptance of the updated juju-core package, as well as the new package
  juju-core-1.25, which is a new version of the existing juju-core package
  allowing the existing juju1 binary to be installed.
  
  User-Facing Features / Changes
  --
  * New Terminology
  * Command Name Changes
  * New Juju home directory
  * Multi-Model Support Active by Default
  * New Bootstrap and Cloud Management Experience
  * Native Support for Charm Bundles
  * Multi Series Charms
  * Improved Local Charm Deployment
  * LXC Local Provider No Longer Available
  * LXD Provider
  * LXD Containers
  * Microsoft Azure Resource Manager Provider
  * Bootstrap Constraints, Series
  * Juju Logging Improvements
  * Unit Agent Improvements
  * API Login with Macaroons
  * MAAS Spaces
  * Resources
  * Juju Status Improvements
  * Relation Get and Set Compatibility
  * Support for new AWS M4 Instance Types
  * Support for win10 and win2016
  
  The full list of changes can be found here: 
https://lists.ubuntu.com/archives/juju/2016-March/006922.html
  and in the final release notes.
  
  Timeline
  
  We have released 2 alphas, and 3 betas for juju2 so far, in addition 3 alpha 
builds of 1.26 which became 2.0.  All targeted 2.0 features are now 
implemented, and we anticipate releasing one release candidate before a final 
stable build. Juju missed uploading any versions of 2.0 to the archive itself,  
as well as the initial projected date of having beta1 in xenial before feature 
freeze. However, juju has been released regularly during the development cycle 
inside the juju ppa. You can see the details on the delivered features and 
milestones on https://launchpad.net/juju-core/2.0. The final stable build will 
be ready in time for the xenial release.
  
  Upgrades
  
- Users upgrading from trusty will find their juju2 version updated. The 
current juju-core package will become juju-core1. Users upgrading from wily and 
trusty will get juju2 as part of the upgrade. Update-alternatives will provide 
support for toggling /usr/bin/juju between juju1 and juju2 binaries.
+ Users upgrading from trusty will find their juju version updated. The current 
juju-core package will be provided as juju-1.25. Update-alternatives will 
provide support for toggling /usr/bin/juju between juju-1.25 and juju-2.0 
binaries.
  
  We have tested to ensure the intended behavior occurs for the following
- scenarios;
+ scenarios:
  
- Trusty
- No juju -> install juju on xenial, juju-core is installed.
- Juju-core -> juju-core-1.25 and juju-core installed, update-alternatives 
toggles
+ New Xenial:
+ No juju, apt-get install juju, juju version will be 2.0.
+ Example using ppa: 
  
- Wily
- No juju -> install juju on xenial, juju-core is installed.
- Juju-core -> juju-core-1.25 and juju-core installed, update-alternatives 
toggles
+ Upgrading Trusty/Wily/old Xenial:
+ Already installed juju 1.X, upgraded to latest 1.25.4, 2.0 also installed and 
is the default juju, update-alternatives used to switch between the two.
+ Example using ppa: 
+ 
  
  Risks
  -
  Although juju itself is now feature complete for 2.0, the MAAS 2.0 support 
will require additional work to be fully supported. MAAS 2.0 is currently under 
development as well, and is an alpha3 at the time of this writing. Juju will 
need to add support for the final version of MAAS 2.0, and this is a risk of 
occurring after xenial is released. If so, we expect to release an sru for 
juju-core soon after xenial releases to provide this support.
  
  Quality / Testing
  -
  As this version breaks API with 1.0, testing for features regressions as well 
as fixing old bugs and avoiding new bugs has been important. The juju team and 
the greater juju community has been testing 2.0 to ensure it’s stable and ready 
to support all of the 1.0 workloads in addition to making use of the new 2.0 
features.
  
  In comparison to juju-1.25:
  
  * Tests improvements including
  * MAAS testing improved
  * Container networking
  * 9 non-voting tests are now voting
  * New tests for all 2.0 features
  * Powerpc toolchain is vastly improved
  * No test regressions!
  * S390 builds reliably, is fully tested and is treated the same as other 
supported architectures
  * 114 bugs has been fixed
  
  Juju practices continuous integration and testing of the juju source
  tree. All voting tests must pass for ubuntu before release. For example,
  for beta3, you can see all tests are passing on ubuntu. The full details
  are here: http://reports.vapour.ws/releases/3815.
 

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

[Martin Packman]

** 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 the new package
  juju-core-1.25, which is a new version of the existing juju-core package
  allowing the existing juju1 binary to be installed.
  
  Related FFes
  
  
  Required for Juju 2.0:
  
  juju-mongodb3.2: bug 1557852
  juju-mongodb2.6: bug 1557830
  juju-mongo-tools3.2: bug 1558336
+ 
+ (see note below about mongodb for details)
  
  Required consumers:
  
  conjure: bug 1561037
  bigdata: bug 1561043
  openstack: Already in universe, dep wait on conjure -> juju 2.0
  charm-tools: bug 1546776
  
  User-Facing Features / Changes
  --
  * New Terminology
  * Command Name Changes
  * New Juju home directory
  * Multi-Model Support Active by Default
  * New Bootstrap and Cloud Management Experience
  * Native Support for Charm Bundles
  * Multi Series Charms
  * Improved Local Charm Deployment
  * LXC Local Provider No Longer Available
  * LXD Provider
  * LXD Containers
  * Microsoft Azure Resource Manager Provider
  * Bootstrap Constraints, Series
  * Juju Logging Improvements
  * Unit Agent Improvements
  * API Login with Macaroons
  * MAAS Spaces
  * Resources
  * Juju Status Improvements
  * Relation Get and Set Compatibility
  * Support for new AWS M4 Instance Types
  * Support for win10 and win2016
  
  The full list of changes can be found here: 
https://lists.ubuntu.com/archives/juju/2016-March/006922.html
  and in the final release notes.
  
  Timeline
  
  We have released 2 alphas, and 3 betas for juju2 so far, in addition 3 alpha 
builds of 1.26 which became 2.0.  All targeted 2.0 features are now 
implemented, and we anticipate releasing one release candidate before a final 
stable build. Juju missed uploading any versions of 2.0 to the archive itself,  
as well as the initial projected date of having beta1 in xenial before feature 
freeze. However, juju has been released regularly during the development cycle 
inside the juju ppa. You can see the details on the delivered features and 
milestones on https://launchpad.net/juju-core/2.0. The final stable build will 
be ready in time for the xenial release.
  
  Upgrades
  
  Users upgrading from trusty will find their juju version updated. The current 
juju-core package will be provided as juju-1.25. Update-alternatives will 
provide support for toggling /usr/bin/juju between juju-1.25 and juju-2.0 
binaries.
  
  We have tested to ensure the intended behavior occurs for the following
  scenarios:
  
  New Xenial:
  No juju, apt-get install juju, juju version will be 2.0.
  Example using ppa: 
  
  Upgrading Trusty/Wily/old Xenial:
  Already installed juju 1.X, upgraded to latest 1.25.4, 2.0 also installed and 
is the default juju, update-alternatives used to switch between the two.
  Example using ppa: 
  
  Risks
  -
  Although juju itself is now feature complete for 2.0, the MAAS 2.0 support 
will require additional work to be fully supported. MAAS 2.0 is currently under 
development as well, and is an alpha3 at the time of this writing. Juju will 
need to add support for the final version of MAAS 2.0, and this is a risk of 
occurring after xenial is released. If so, we expect to release an sru for 
juju-core soon after xenial releases to provide this support.
  
  Quality / Testing
  -
  As this version breaks API with 1.0, testing for features regressions as well 
as fixing old bugs and avoiding new bugs has been important. The juju team and 
the greater juju community has been testing 2.0 to ensure it’s stable and ready 
to support all of the 1.0 workloads in addition to making use of the new 2.0 
features.
  
  In comparison to juju-1.25:
  
  * Tests improvements including
  * MAAS testing improved
  * Container networking
  * 9 non-voting tests are now voting
  * New tests for all 2.0 features
  * Powerpc toolchain is vastly improved
  * No test regressions!
  * S390 builds reliably, is fully tested and is treated the same as other 
supported architectures
  * 114 bugs has been fixed
  
  Juju practices continuous integration and testing of the juju source
  tree. All voting tests must pass for ubuntu before release. For example,
  for beta3, you can see all tests are passing on ubuntu. The full details
  are here: http://reports.vapour.ws/releases/3815.
  
  The community has also been actively involved with testing, providing
  feedback, and adopting 2.0 throughout the development cycle.
  
  * 250 bugs and wishlist items filed
  * 4 bugs fixed by community members
  * ~100-125 downloads for each ppa release
  
  Community Adoption
  --
  The community has already begun adopt

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

[Martin Packman]

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 because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1545913

Title:
  [FFe] juju-core 2.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

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 on all architectures, including exercising the
reflect code.

See irc log for more background:



** Affects: juju-core (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/1564662

Title:
  Juju binaries should be stripped

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1564662/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

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 Juju 2
configuration for the first time, something along the lines of:

$ sudo apt-get update
$ juju status
WARNING Creating new juju 2 configuration.
Use `update-alternatives --config juju` to switch for 1.X environments.
$ juju status
ERROR Unable to connect to model "".
Please check your credentials or use 'juju bootstrap' to create a new model.

There has been some concern that this is still too confusing and 1.X
should remain the default juju without explicit user intervention.

** Affects: juju-core (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/1564670

Title:
  After upgrade Juju 1.X should still be the default

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1564670/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

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 ~adconrad

-- 
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/1545913

Title:
  [FFe] juju-core 2.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1054096] Re: Openstack folsom compatibility

[Martin Packman]

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 about this bug go to:
https://bugs.launchpad.net/juju/+bug/1054096/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

** 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 provider interacts poorly with arch constraints

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

** 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 tag using
  maas-tags to deploy with juju

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 966617] Re: supply high level design documents

[Martin Packman]

** 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 juju in Ubuntu.
https://bugs.launchpad.net/bugs/966617

Title:
  supply high level design documents

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

** 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 juju in Ubuntu.
https://bugs.launchpad.net/bugs/802117

Title:
  juju ssh/scp commands cause spurious key errors, should use a
  different known_hosts file

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 966617] Re: supply high level design documents

[Martin Packman]

** 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:
https://bugs.launchpad.net/juju/+bug/966617/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

** 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

-- 
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 notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/1068566/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

** 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1068566

Title:
  Juju 0.6 incompatible with MAAS in precise

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

** 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 because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1064638

Title:
  Commissioning is failing to set node memory attribute

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

** 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/1068566

Title:
  Juju 0.6 incompatible with MAAS in precise

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

With the landing of the rollup branch, all the parts needed for this should now 
be on trunk:


** Changed in: maas
   Status: Triaged => Fix Committed

-- 
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/1044503

Title:
  kernel command line is not easily customizable

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

** 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'])': No such tag using
  maas-tags to deploy with juju

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

** 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 notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/1068566/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

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 set-constraints cpu=1.0`
4) `juju deploy `

I suspect the issue was with the maas-name constraint you have set
there, once you have the bootstrap node on that machine, all further
attempts to allocate a machine will fail as it's already in use.

** Changed in: maas
   Status: Triaged => Incomplete

-- 
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/1154803

Title:
  Constraints prevents the allocation of nodes if they are equal to the
  HW.

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

** 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/1061678

Title:
  OpenStack provider should fall back to local-ipv4 if public-ipv4 is
  not found

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

** 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 public-ipv4 is
  not found

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

** 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 notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/1068566/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

** 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.
https://bugs.launchpad.net/bugs/1064734

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

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

** 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 charm locally
+ The various lxc scripts installed in /usr/bin are Python 3 only. If the
+ user has PYTHONPATH or other similar environment variables set, these
+ scripts can incorrectly inherit details from the user's Python 2 setup
+ when run.
  
- ProblemType: Crash
- DistroRelease: Ubuntu 13.04
- Package: lxc 0.9.0~alpha3-0ubuntu2
- ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7
- Uname: Linux 3.8.0-6-generic i686
- ApportVersion: 2.8-0ubuntu4
- Architecture: i386
- Date: Wed Feb 20 17:37:31 2013
- ExecutablePath: /usr/bin/lxc-ls
- InstallationDate: Installed on 2012-12-19 (63 days ago)
- InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
- InterpreterPath: /usr/bin/python3.3
- MarkForUpload: True
- ProcCmdline: BOOT_IMAGE=/vmlinuz-3.8.0-6-generic root=/dev/mapper/ubuntu-root 
ro vesafb.invalid=1
- ProcEnviron:
-  PATH=(custom, user)
-  SHELL=/bin/bash
-  TERM=unknown
-  LANG=en_GB.UTF-8
-  LANGUAGE=en_GB:en
- Signal: 6
- SourcePackage: lxc
- StacktraceTop:
-  raise () from /lib/i386-linux-gnu/libc.so.6
-  abort () from /lib/i386-linux-gnu/libc.so.6
-  Py_FatalError ()
-  ?? ()
-  _Py_InitializeEx_Private ()
- Title: lxc-ls crashed with SIGABRT in raise()
- UpgradeStatus: Upgraded to raring on 2013-01-13 (37 days ago)
- UserGroups:
+ This can result in either a crash as per the initial report, or a
+ traceback over syntax differences such as the following in juju:
+ 
+ Traceback (most recent call last):
+File "/usr/lib/python2.7/dist-packages/juju/agents/machine.py", line 97, 
in watch_service_units
+  yield self.unit_deployer.start_service_unit(unit_name)
+File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 
1069, in _inlineCallbacks
+  result = result.throwExceptionIntoGenerator(g)
+File "/usr/lib/python2.7/dist-packages/twisted/python/failure.py", line 
389, in throwExceptionIntoGenerator
+  return g.throw(self.type, self.value, self.tb)
+File "/usr/lib/python2.7/dist-packages/juju/unit/deploy.py", line 91, in 
start_service_unit
+  running = yield deployment.is_running()
+File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 
1069, in _inlineCallbacks
+  result = result.throwExceptionIntoGenerator(g)
+File "/usr/lib/python2.7/dist-packages/twisted/python/failure.py", line 
389, in throwExceptionIntoGenerator
+  return g.throw(self.type, self.value, self.tb)
+File "/usr/lib/python2.7/dist-packages/juju/machine/unit.py", line 301, in 
is_running
+  prefix=self.container.container_name)
+File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 
1069, in _inlineCallbacks
+  result = result.throwExceptionIntoGenerator(g)
+File "/usr/lib/python2.7/dist-packages/twisted/python/failure.py", line 
389, in throwExceptionIntoGenerator
+  return g.throw(self.type, self.value, self.tb)
+File "/usr/lib/python2.7/dist-packages/juju/lib/lxc/__init__.py", line 
147, in get_containers
+  _, output = yield deferToThread(_cmd, ["lxc-ls"])
+File "/usr/lib/python2.7/dist-packages/twisted/python/threadpool.py", line 
172, in _worker
+  result = context.call(ctx, function, *args, **kwargs)
+File "/usr/lib/python2.7/dist-packages/twisted/python/context.py", line 
118, in callWithContext
+  return self.currentContext().callWithContext(ctx, func, *args, **kw)
+File "/usr/lib/python2.7/dist-packages/twisted/python/context.py", line 
81, in callWithContext
+  return func(*args,**kw)
+File "/usr/lib/python2.7/dist-packages/juju/lib/lxc/__init__.py", line 48, 
in _cmd
+  raise LXCError(stdout_data)
+  LXCError: Fatal Python error: Py_Initialize: Unable to get the locale 
encoding
+File "/usr/lib/python2.7/encodings/__init__.py", line 123
+  raise CodecRegistryError,\
+  ^
+  SyntaxError: invalid syntax
  
  
  WORKAROUND:
  Add "-Es" to /usr/bin/lxc-ls (after /usr/bin/python3 ) so that those 
environment variables are ignored.

-- 
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/1130809

Title:
  lxc scripts break when user has PYTHONPATH set

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

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 a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1130809

Title:
  lxc scripts break when user has PYTHONPATH set

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

** 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/bugs/1130809

Title:
  lxc scripts break when user has PYTHONPATH set

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

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 scripts in bug 1130809

The risks associated are low:
* Users commonly install from PPA so this version has had testing throughout 
the cycle
* No major changes between 0.6 and 0.7

See the upstream changelog on the release page:


** Affects: juju (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/1167921

Title:
  Feature freeze exception for python juju 0.7 in raring

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

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 addressed there I shall upload a useful debdiff to this bug.



-- 
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/1167921

Title:
  Feature freeze exception for python juju 0.7 in raring

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

** 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 Ubuntu.
https://bugs.launchpad.net/bugs/1167921

Title:
  Feature freeze exception for python juju 0.7 in raring

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

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"
   
https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1167921/+attachment/3640940/+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 Ubuntu.
https://bugs.launchpad.net/bugs/1167921

Title:
  Feature freeze exception for python juju 0.7 in raring

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

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 because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1167921

Title:
  Feature freeze exception for python juju 0.7 in raring

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

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 a prize", make it "make 
something you are going to use and get a prize.": BLOCKED
  [jorge] charm-tools, we need to talk about it more, make a "Best practices 
for charms" should be in "write a charm", integrate the mythical best practices 
page with write a charm.: TODO
  [mark-mims] Investigate making charm documentation testable: TODO
  [evilnick] Investigate making charm documentation testable: TODO
- [gz] #1069883 Fix bug where defaulting to smallest instance type.: INPROGRESS
+ [gz] #1069883 Fix bug where defaulting to smallest instance type.: DONE
  [jjo] "Case Studies" from webops: TODO
  [mthaddon] "Case Studies" from webops: TODO
  [timrchavez] "Case Studies" from PES: TODO
  [jorge] README Review, prioritized based on charm popularity: TODO
  [jorge] Announce README fixups on the mailing list with maintainers: TODO
  [jorge] Codify for ~charmers to encourage people to fix readmes on submission 
of other fixes: [jorge] Provider discounts for charmers?: INPROGRESS
  [jorge] Update /events page on juju.ubuntu.com to show where we are 
attending.: DONE
  [jorge] Investigate long running contests on juju.ubuntu.com: TODO
  [niemeyer] Post instructions on how to use other "code hosting" options, and 
juju publish usage.: TODO
  [jorge] Ensure that the juju gui can run on the local provider: TODO
  [jorge] Investigate Openstack's use of github/launchpad workflow: INPROGRESS
  [jorge] fix dead link: https://wiki.ubuntu.com/ServerTeam/MAAS/Juju from 
https://juju.ubuntu.com/get-started/maas/: TODO
  
  Work items:
  [jorge] File bugs on charms that don't meet quality guidelines. "it would be 
great if this charm did multimaster!!" and so on, so people know that they can 
fix it. "needs-scaleout" tag?: BLOCKED
  [jorge] Way to go, we have over 100 people who contributed charms and you 
told no one.  Nice work.: TODO
  jorge] "Pimp my charm" contest. or Xprize? "Scale out HA x service to blah 
blah with integrated backups: TODO

-- 
Juju Contributor Onramp
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

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.
https://bugs.launchpad.net/bugs/1178506

Title:
  Cannot switch between juju-0.7 and juju-core

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1178506/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

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 "/usr/lib/python2.7/dist-packages/novaclient/shell.py", line 765, in main
OpenStackComputeShell().main(map(strutils.safe_decode, sys.argv[1:]))
  File "/usr/lib/python2.7/dist-packages/novaclient/shell.py", line 695, in main
self.cs.authenticate()
  File "/usr/lib/python2.7/dist-packages/novaclient/v1_1/client.py", line 169, 
in authenticate
self.client.authenticate()
  File "/usr/lib/python2.7/dist-packages/novaclient/client.py", line 332, in 
authenticate
auth_url = self._plugin_auth(auth_url)
  File "/usr/lib/python2.7/dist-packages/novaclient/client.py", line 392, in 
_plugin_auth
self.auth_plugin.authenticate(self, auth_url)
AttributeError: 'NoneType' object has no attribute 'authenticate'
ERROR: 'NoneType' object has no attribute 'authenticate'

There is a new plugin infrastructure for authenticating against non-
standard openstack clouds, but the rackspace compat code is gone from
the main python-novaclient codebase and the 'pyrax' project seems not to
be packaged for ubuntu.



ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: python-novaclient 1:2.13.0-0ubuntu1
Uname: Linux 3.4.0-5-chromebook armv7l
ApportVersion: 2.9.2-0ubuntu8.1
Architecture: armhf
Date: Thu Jul  4 11:15:45 2013
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: python-novaclient
UpgradeStatus: Upgraded to raring on 2013-01-26 (158 days ago)

** Affects: python-novaclient (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug armhf raring

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-novaclient in Ubuntu.
https://bugs.launchpad.net/bugs/1197745

Title:
  Rackspace authentication no longer supported

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-novaclient/+bug/1197745/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

** 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.
https://bugs.launchpad.net/bugs/1182898

Title:
  Please support `juju --version`

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

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

 Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1500981

Title:
  juju-db segfault while syncing with replicas

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

> * 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. Backporting the code
changes required to change the dependency for 1.24 carries considerable
risk to application-level api compatibility, as yaml.v2 changes some
serialisation behaviour. I would prefer if for 1.24 we relied on the
bundled yaml.v1 package that been consistently used in testing through
this cycle.

> * golang-x-text
>  - ftbfs (comment 115)
>  - needs a bug subscriber

This package is not a dependency of juju. It's used by
golang.org/x/net/html/charset only, so is just pulled in as a side
effect of taking the debian package. My preference would be to drop the
juju packaging dependency on golang-go.net-dev for 1.24 instead.

> * juju-core
>  - what is the status of
>
> https://code.launchpad.net/~james-page/ubuntu/wily/juju-core/mir-fixes/+merge/274052
>  ? jamespage said it is 'pending testing by the juju qa team'.

We have manually tested the packaging change, but it is not yet included
in our automated testing and release process. We have work in progress
to break out our series-independent packaging branch. That said, the
merge should not be considered blocked on our verification.

> * dep8 question (comments 86, 93, 99, 100, 101, 117)
>  - pitti's comment in #99 needs to be done. It could be done as an SRU. If 
> that is the approach, please file a bug on this and comment here

I would appreciate if someone who has a clear understanding for the work
pitti is requesting (such as pitti himself) could file the bug and
subscribe me. We'll happily update our packaging to use any such new
mechanism if it's provided.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to golang-github-bmizerany-pat in
Ubuntu.
https://bugs.launchpad.net/bugs/1267393

Title:
  [MIR] juju-core, juju-mongodb, gccgo, golang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dh-golang/+bug/1267393/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

"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 back?"

Short version, these extended-standard library packages are in practice
pretty closely tied to the golang minor version.

Debian currently has go 1.4 and the go-x-text package is from May,
before the go 1.5 release:



In go 1.5 the unicode package, which includes generation of various data
tables, was updated to use Unicode 8.0.0 - which amongst other changes
introduces the Ahom script:



This means the test in golang.org/x/text which uses the data from the
standard library unicode package now finds its own data out of sync with
the system golang on wily. Specifically, the new character U+11730 AHOM
DIGIT ZERO should be numerically equal to 0, but is not. Obviously there
are other failures as well.

There's an easy fix for wily, which is just update the package to use a
current revision of golang.org/x/text for go 1.5 compatibility. I've
proposed a debian/experimental branch that does that:



(Minor wrinkle, still a test failure even with the latest code, I
patched it in the packaging but presumably needs resolving upstream.)

Anyway, where this gets really fun is when we start considering
backports of latest juju. None of these packages existed when trusty was
released, and their current versions will generally be incompatible with
go 1.2.1. We could pick out the revisions that worked for specific
backport packaging, but won't have support upstream for security fixes
to random older checkouts so won't really gain anything.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to golang-github-bmizerany-pat in
Ubuntu.
https://bugs.launchpad.net/bugs/1267393

Title:
  [MIR] juju-core, juju-mongodb, gccgo, golang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dh-golang/+bug/1267393/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

> 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 the security team had concerns and we didn't need it anyway.
Note in 3.2 V8 has gone, and they're back to spidermonkey:



-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1557830

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-mongodb/+bug/1557830/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

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:



Missing here:



So, they should be added back in.

That said, the juju qa team hasn't spent any time this cycle on
adventures with golang packaging. What time we have had on distro tasks
has been sucked up basically packaging mongo 3 (and mongo 2.6 for
migration purposes).

-- 
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/1560315

Title:
  [needs packaging] juju2 beta is not in xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1560315/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1330504] Re: strongSwan 5.1.3

[Martin Packman]

** 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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1330504/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

** 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 notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1248283/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

** Also affects: juju-core
   Importance: Undecided
   Status: New

** Also affects: juju-core/1.16
   Importance: Undecided
   Status: New

** Changed in: juju-core
   Importance: Undecided => High

** Changed in: juju-core
   Status: New => Fix Committed

** Changed in: juju-core
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-core/1.16
   Status: New => In Progress

** Changed in: juju-core/1.16
Milestone: None => 1.16.1

** Changed in: juju-core/1.16
 Assignee: (unassigned) => Martin Packman (gz)

-- 
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 repository differently

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

** 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 repository differently

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

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.

There are arguments in all directions depending on the exact use-case
though. In cases where you have more than one environment on the same
cloud account (for instance, a staging and a live deployment), the fact
the default group applies to both could cause issues, would be
impossible to monitor/alter one without affecting the other. If the
account is also used for non-juju work, sharing rules via the default
group could be either a convenience or a hole.

-- 
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/1129720

Title:
  juju instances not including the "default" security group

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

** 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 is down

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

** 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 manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1248283/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

** 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 notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1250007/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

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.
https://bugs.launchpad.net/bugs/1268913

Title:
  Loading state on bootstrap ignores ssl-hostname-verification setting

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

** 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

Title:
  remove-* aliases for destroy-service and destroy-machine

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

As this is blocking developers landing code, I am going ahead and
working around this by not building the problem test file. There is
almost certainly a ppc64/gccgo bug in need of fixing here.

** Also affects: gccgo-go (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: juju-core
   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:
  reboot tests fail to build on gccgo

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

** 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 notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1381671/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[Martin Packman]

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: local_test.go:1207: 
com_juju_juju_provider_openstack_test.TestFetchFromToolsMetadataSources.pN66_github.com_juju_juju_provider_openstack_test.localHTTPSServerSuite
   0.243s
munmap of stack space failed: errno 22
Aborted
...

ubuntu@go:~/go/src/github.com/juju/juju$ (cd provider/openstack/&& go test 
./... -compiler gccgo -gocheck.v -v)
3
=== RUN Test
...
PASS: local_test.go:1207: 
com_juju_juju_provider_openstack_test.TestFetchFromToolsMetadataSources.pN66_github.com_juju_juju_provider_openstack_test.localHTTPSServerSuite
   0.295s
signal: segmentation fault (core dumped)
FAILgithub.com/juju/juju/provider/openstack 12.746s

And in environs/simplestreams:

ubuntu@go:~/go/src/github.com/juju/juju$ (cd environs/simplestreams&& go test 
./... -compiler gccgo -gocheck.v -v)
=== RUN Test
...
PASS: datasource_test.go:79: 
com_juju_juju_environs_simplestreams_test.TestNonVerifyingClientSucceeds.pN69_github.com_juju_juju_environs_simplestreams_test.datasourceHTTPSSuite
0.014s
unexpected fault address 0x7f330011
fatal error: fault
[signal 0xb code=0x1 addr=0x7f330011]
...

This one looks a bit like bug 1381671 but the same run can just pass:

$ (cd environs/simplestreams&& go test ./... -compiler gccgo -gocheck.v -v)
=== RUN Test
...
OK: 46 passed
--- PASS: Test (0.27 seconds)
PASS


Some investigations from IRC:


** Affects: gccgo-go (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/1393825

Title:
  Juju testsuite fails in random ways

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gccgo-go/+bug/1393825/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs