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

[Adam Stokes]

** 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
  
  Required consumers:
  
  conjure: bug 1561037
  bigdata: bug 1561043
- openstack: ?TBC
+ 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 adopting 2.0, and is dependent 

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

[Adam Stokes]

xnox, there is this bug: https://bugs.launchpad.net/juju-
core/+bug/1547665

-- 
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 1560315] Re: [needs packaging] juju2 beta is not in xenial

[Adam Stokes]

We are using juju-core package name now so there is no need for this
packaging request :)

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

-- 
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 1545913] Re: [FFe] juju-core 2.0

[Adam Stokes]

** Tags added: conjure

-- 
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 1545913] Re: [FFe] juju-core 2.0

[Adam Stokes]

Also want to mention the openstack package as well.

-- 
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 1560315] Re: [needs packaging] juju2 beta is not in xenial

[Adam Stokes]

** Changed in: juju-core (Ubuntu)
   Status: Triaged => 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/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 1560315] Re: [needs packaging] juju2 beta is not in xenial

[Adam Stokes]

** Description changed:

  Juju 2.0 will be in xenial. We want to place juju 2.0-beta2 (or possibly
  beta3) in xenial for Ubuntu users to test.
  
  This branch introduces the juju2 package.
  
  lp:~juju-qa/ubuntu/xenial/juju2/xenial-2.0-beta2
  
  The juju team propose a new juju2 packages that is co-installable with
  the juju-core package. This allows users to have juju 2.x and 1.x
  installed on the xenial host. Users can maintain their 1.x envs
  while creating new Juju 2.x deployments.
  
  This branch is based on
  lp:~sinzui/ubuntu/xenial/juju-core/xenial-1.25.4
  Which is stalled. We are waiting for a 1.25.5 released. We want to
  use this as the base because it minimises the changes in the debian
  dir.
  
    * New upstream release (Lp: 1560315).
    * d/control:
  - Renamed the package juju-core to juju2.
  - Dropped unneeded juju-local* and juju packages.
    * d/rules:
  - Renamed the package to juju2.
  - Updated rules to 2.x.
  - Additional path/name changes to support co-installability with
    the 1.x juju-core package.
    * d/copyright: Updated per changes to embedded dependencies.
    * d/tests/*
  - Updated tests to use juju2 command line.
  - Replaced local-provider tests with lxd tests.
  
  [Devel Fix]
  
  [sinzui] Prepare source package and diffs: DONE
  [stokachu] Review package: DONE
- [stokachu] Upload to the development release (xenial-proposed): TODO
+ [stokachu] Upload to the development release (xenial-proposed): DONE
  
  [sinzui] Upstream QA test against xenial: TODO
  [sinzui] Test streams with xenial-proposed: TODO

-- 
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 1560315] Re: [needs packaging] juju2 beta is not in xenial

[Adam Stokes]

** Description changed:

  Juju 2.0 will be in xenial. We want to place juju 2.0-beta2 (or possibly
  beta3) in xenial for Ubuntu users to test.
  
  This branch introduces the juju2 package.
  
  lp:~juju-qa/ubuntu/xenial/juju2/xenial-2.0-beta2
  
  The juju team propose a new juju2 packages that is co-installable with
  the juju-core package. This allows users to have juju 2.x and 1.x
  installed on the xenial host. Users can maintain their 1.x envs
  while creating new Juju 2.x deployments.
  
  This branch is based on
  lp:~sinzui/ubuntu/xenial/juju-core/xenial-1.25.4
  Which is stalled. We are waiting for a 1.25.5 released. We want to
  use this as the base because it minimises the changes in the debian
  dir.
  
    * New upstream release (Lp: 1560315).
    * d/control:
  - Renamed the package juju-core to juju2.
  - Dropped unneeded juju-local* and juju packages.
    * d/rules:
  - Renamed the package to juju2.
  - Updated rules to 2.x.
  - Additional path/name changes to support co-installability with
    the 1.x juju-core package.
    * d/copyright: Updated per changes to embedded dependencies.
    * d/tests/*
  - Updated tests to use juju2 command line.
  - Replaced local-provider tests with lxd tests.
  
  [Devel Fix]
  
  [sinzui] Prepare source package and diffs: DONE
- [stokachu] Review package: TODO
+ [stokachu] Review package: DONE
  [stokachu] Upload to the development release (xenial-proposed): TODO
  
  [sinzui] Upstream QA test against xenial: TODO
  [sinzui] Test streams with xenial-proposed: TODO

-- 
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 1560315] Re: [needs packaging] juju2 beta is not in xenial

[Adam Stokes]

Ok I've gotten it down to some minor packaging issues:

I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju ang and
N: 
N:Lintian found a spelling error in the given binary. Lintian has a list
N:of common misspellings that it looks for. It does not have a dictionary
N:like a spelling checker does.
N:
N:If the string containing the spelling error is translated with the help
N:of gettext or a similar tool, please fix the error in the translations
N:as well as the English text to avoid making the translations fuzzy. With
N:gettext, for example, this means you should also fix the spelling
N:mistake in the corresponding msgids in the *.po files.
N:
N:You can often find the word in the source code by running:
N:
N: grep -rw  
N:
N:This tag may produce false positives for words that contain non-ASCII
N:characters due to limitations in strings.
N:
N:Severity: minor, Certainty: wild-guess
N:
N:Check: binaries, Type: binary, udeb
N: 
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju Succesfully 
Successfully
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju enviroment 
environment
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju specifed 
specified
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju transfered 
transferred
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju reenabled 
re-enabled
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju intial 
initial
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju reenable 
re-enable
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju ommitted 
omitted
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju precendence 
precedence
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju allows to 
allows one to
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju-metadata ang 
and
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju-metadata 
enviroment environment
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju-metadata 
specifed specified
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju-metadata 
arbitary arbitrary
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju-metadata 
precendence precedence
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju-restore ang 
and
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju-restore 
specifed specified
I: juju2: spelling-error-in-binary 
usr/lib/juju-2.0-beta2/bin/juju-upgrade-mongo ang and
I: juju2: spelling-error-in-binary 
usr/lib/juju-2.0-beta2/bin/juju-upgrade-mongo specifed specified
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/jujud ang and
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/jujud Succesfully 
Successfully
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/jujud enviroment 
environment
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/jujud specifed 
specified
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/jujud addreses 
addresses
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/jujud overriden 
overridden
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/jujud precendence 
precedence


But i don't think this should hold up the upload.

-- 
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 1560315] Re: [needs packaging] juju2 beta is not in xenial

[Adam Stokes]

With my latest changes here is the lintian report:

I: juju2 source: wildcard-matches-nothing-in-dep5-copyright 
src/github.com/chai2010/gettext-go (paragraph at line 58)
N: 
N:The wildcard that was specified matches no file in the source tree. This
N:either indicates that you should fix the wildcard so that it matches the
N:intended file or that you can remove the wildcard. Notice that in
N:contrast to shell globs, the "*" (star or asterisk) matches slashes and
N:leading dots.
N:
N:Refer to
N:https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ for
N:details.
N:
N:Severity: minor, Certainty: possible
N:
N:Check: source-copyright, Type: source
N: 
I: juju2 source: wildcard-matches-nothing-in-dep5-copyright 
src/github.com/chai2010/gettext-go (paragraph at line 65)
I: juju2 source: wildcard-matches-nothing-in-dep5-copyright 
src/golang.org/x/net/html/charset/testdata/* (paragraph at line 455)
W: juju2 source: dep5-copyright-license-name-not-unique (paragraph at line 1328)
N: 
N:This paragraph defines an already defined license.
N:
N:According to the specification, short license names are required to be
N:unique within a single copyright file.
N:
N:Refer to
N:https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ for
N:details.
N:
N:Severity: normal, Certainty: possible
N:
N:Check: source-copyright, Type: source
N: 
W: juju2 source: dep5-copyright-license-name-not-unique (paragraph at line 1615)
W: juju2 source: file-without-copyright-information 
src/github.com/chai2010/gettext-go/LICENSE
N: 
N:The source tree contains a file which was not matched by any of the
N:Files paragraphs in debian/copyright. Either adjust existing wildcards
N:to match that file or add a new Files paragraph.
N:
N:Refer to
N:https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ for
N:details.
N:
N:Severity: normal, Certainty: possible
N:
N:Check: source-copyright, Type: source
N: 
W: juju2 source: file-without-copyright-information 
src/github.com/chai2010/gettext-go/README.md
W: juju2 source: file-without-copyright-information 
src/github.com/chai2010/gettext-go/examples/Makefile
W: juju2 source: file-without-copyright-information 
src/github.com/chai2010/gettext-go/examples/hello.go
W: juju2 source: file-without-copyright-information 
src/github.com/chai2010/gettext-go/examples/hi/hi.go
W: juju2 source: file-without-copyright-information 
src/github.com/chai2010/gettext-go/examples/local.zip
W: juju2 source: file-without-copyright-information 
src/github.com/chai2010/gettext-go/examples/local/default/LC_MESSAGES/hello.mo
W: juju2 source: file-without-copyright-information 
src/github.com/chai2010/gettext-go/examples/local/default/LC_MESSAGES/hello.po
W: juju2 source: file-without-copyright-information 
src/github.com/chai2010/gettext-go/examples/local/default/LC_RESOURCE/hello/favicon.ico
W: juju2 source: file-without-copyright-information 
src/github.com/chai2010/gettext-go/examples/local/default/LC_RESOURCE/hello/poems.txt
W: juju2 source: file-without-copyright-information 
src/github.com/chai2010/gettext-go/examples/local/zh_CN/LC_MESSAGES/hello.mo
W: juju2 source: file-without-copyright-information 
src/github.com/chai2010/gettext-go/examples/local/zh_CN/LC_MESSAGES/hello.po
W: juju2 source: file-without-copyright-information 
src/github.com/chai2010/gettext-go/examples/local/zh_CN/LC_RESOURCE/hello/poems.txt
W: juju2 source: file-without-copyright-information 
src/github.com/chai2010/gettext-go/examples/local/zh_TW/LC_MESSAGES/hello.mo
W: juju2 source: file-without-copyright-information 
src/github.com/chai2010/gettext-go/examples/local/zh_TW/LC_MESSAGES/hello.po
W: juju2 source: file-without-copyright-information 
src/github.com/chai2010/gettext-go/examples/local/zh_TW/LC_RESOURCE/hello/poems.txt
W: juju2 source: file-without-copyright-information 
src/github.com/chai2010/gettext-go/gettext/caller.go
W: juju2 source: file-without-copyright-information 
src/github.com/chai2010/gettext-go/gettext/caller_test.go
W: juju2 source: file-without-copyright-information 
src/github.com/chai2010/gettext-go/gettext/doc.go
W: juju2 source: file-without-copyright-information 
src/github.com/chai2010/gettext-go/gettext/domain.go
W: juju2 source: file-without-copyright-information 
src/github.com/chai2010/gettext-go/gettext/domain_helper.go
W: juju2 source: file-without-copyright-information 
src/github.com/chai2010/gettext-go/gettext/fs.go
W: juju2 source: file-without-copyright-information 
src/github.com/chai2010/gettext-go/gettext/gettext.go
W: juju2 source: file-without-copyright-information 
src/github.com/chai2010/gettext-go/gettext/gettext_test.go
W: juju2 source: file-without-copyright-information 
src/github.com/chai2010/gettext-go/gettext/hello.go
W: juju2 source: file-without-copyright-information 

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

[Adam Stokes]

For completeness this is the lintian output in all its glory:

E: juju2 changes: bad-distribution-in-changes-file xenial-amd64
N: 
N:You've specified an unknown target distribution for your upload in the
N:debian/changelog file. It is possible that you are uploading for a
N:different distribution than the one Lintian is checking for. In that
N:case, passing --profile $VENDOR may fix this warning.
N:
N:Note that the distributions non-free and contrib are no longer valid.
N:You'll have to use distribution unstable and Section: non-free/xxx or
N:Section: contrib/xxx instead.
N:
N:Refer to Debian Policy Manual section 5.6.14 (Distribution) for details.
N:
N:Severity: important, Certainty: certain
N:
N:Check: changes-file, Type: changes
N: 
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju ang and
N: 
N:Lintian found a spelling error in the given binary. Lintian has a list
N:of common misspellings that it looks for. It does not have a dictionary
N:like a spelling checker does.
N:
N:If the string containing the spelling error is translated with the help
N:of gettext or a similar tool, please fix the error in the translations
N:as well as the English text to avoid making the translations fuzzy. With
N:gettext, for example, this means you should also fix the spelling
N:mistake in the corresponding msgids in the *.po files.
N:
N:You can often find the word in the source code by running:
N:
N: grep -rw  
N:
N:This tag may produce false positives for words that contain non-ASCII
N:characters due to limitations in strings.
N:
N:Severity: minor, Certainty: wild-guess
N:
N:Check: binaries, Type: binary, udeb
N: 
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju Succesfully 
Successfully
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju enviroment 
environment
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju specifed 
specified
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju transfered 
transferred
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju reenabled 
re-enabled
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju intial 
initial
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju reenable 
re-enable
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju ommitted 
omitted
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju precendence 
precedence
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju allows to 
allows one to
E: juju2: embedded-library usr/lib/juju-2.0-beta2/bin/juju: libyaml
N: 
N:The given ELF object appears to have been statically linked to a
N:library. Doing this is strongly discouraged due to the extra work needed
N:by the security team to fix all the extra embedded copies or trigger the
N:package rebuilds, as appropriate.
N:
N:If the package uses a modified version of the given library it is highly
N:recommended to coordinate with the library's maintainer to include the
N:changes on the system version of the library.
N:
N:Refer to Debian Policy Manual section 4.13 (Convenience copies of code)
N:for details.
N:
N:Severity: serious, Certainty: possible
N:
N:Check: binaries, Type: binary, udeb
N: 
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju-metadata ang 
and
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju-metadata 
enviroment environment
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju-metadata 
specifed specified
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju-metadata 
arbitary arbitrary
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju-metadata 
precendence precedence
E: juju2: embedded-library usr/lib/juju-2.0-beta2/bin/juju-metadata: libyaml
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju-restore ang 
and
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju-restore 
specifed specified
E: juju2: embedded-library usr/lib/juju-2.0-beta2/bin/juju-restore: libyaml
W: juju2: hardening-no-relro usr/lib/juju-2.0-beta2/bin/juju-restore
N: 
N:This package provides an ELF binary that lacks the "read-only
N:relocation" link flag. This package was likely not built with the
N:default Debian compiler flags defined by dpkg-buildflags. If built using
N:dpkg-buildflags directly, be sure to import LDFLAGS.
N:
N:Refer to https://wiki.debian.org/Hardening for details.
N:
N:Severity: normal, Certainty: certain
N:
N:Check: binaries, Type: binary, udeb
N: 
I: juju2: spelling-error-in-binary 
usr/lib/juju-2.0-beta2/bin/juju-upgrade-mongo ang and
I: juju2: spelling-error-in-binary 
usr/lib/juju-2.0-beta2/bin/juju-upgrade-mongo specifed specified
E: juju2: unstripped-binary-or-object 

[Bug 1547640] Re: proxy tries ipv6 and gets 503 when no ipv6 routes

[Adam Stokes]

** Tags added: cloud-installer

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

Title:
  proxy tries ipv6 and gets 503 when no ipv6 routes

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1547640/+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 1509414] Re: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers

[Adam Stokes]

I've also tested manually and via our OpenStack installer and lxcbr0 is
assigned (10.0.4.1) and the network is able to reach out to the internet
as before.

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

Title:
  pre-installed lxc in cloud image produces broken lxc (and later lxd)
  containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1509414] Re: lxc postinst script checks available interfaces, can choose

[Adam Stokes]

** Tags added: cloud-installer

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

Title:
  lxc postinst script checks available interfaces, can choose

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1509414] Re: lxc postinst script checks available interfaces, can choose

[Adam Stokes]

** Changed in: lxc (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  lxc postinst script checks available interfaces, can choose

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1509414] Re: lxc postinst script checks available interfaces, can choose

[Adam Stokes]

** Description changed:

- The released wily image preinstalls lxc, which breaks the assumption
- that lxc's preinst packaging script makes:
+ [Problem]
+ The released wily image preinstalls lxc, which breaks the assumption that 
lxc's preinst packaging script makes:
  
  It inspects the network to try to pick a 10.0.N.0 network that isn't
  being used, with N starting at 3, so this appears to have picked
  10.0.3.0 when it was installed on whatever system was generating the
  image. This conflicts with the network that eth0 gets attached to when
  the image is brought up in a container, because it gets attached to the
  host's lxcbr0, which is using 10.0.3.x.
  
  This affects LXC, and should affect LXD but doesn't currently. (see #2)
  The easiest way to reproduce this is to use the ubuntu-cloud lxc template on 
a wily host:
  
+ [Test Case]
+ 
  sudo lxc-create -t ubuntu-cloud -n wily
  sudo lxc-start -n wily
  sudo lxc-attach -n wily
  # inside container, test connectivity, eg:
  apt-get update
+ 
+ [Regression Potentional]
+ Currently none as networking didn't work initially.

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

Title:
  lxc postinst script checks available interfaces, can choose

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1509414] Re: lxc postinst script checks available interfaces, can choose

[Adam Stokes]

** Description changed:

  [Problem]
  The released wily image preinstalls lxc, which breaks the assumption that 
lxc's preinst packaging script makes:
  
  It inspects the network to try to pick a 10.0.N.0 network that isn't
  being used, with N starting at 3, so this appears to have picked
  10.0.3.0 when it was installed on whatever system was generating the
  image. This conflicts with the network that eth0 gets attached to when
  the image is brought up in a container, because it gets attached to the
  host's lxcbr0, which is using 10.0.3.x.
  
- This affects LXC, and should affect LXD but doesn't currently. (see #2)
+ This affects LXC, and should affect LXD but doesn't currently, as the 
metadata used for lxd images is still pointing to a beta2 release.
  The easiest way to reproduce this is to use the ubuntu-cloud lxc template on 
a wily host:
  
  [Test Case]
  
  sudo lxc-create -t ubuntu-cloud -n wily
  sudo lxc-start -n wily
  sudo lxc-attach -n wily
  # inside container, test connectivity, eg:
  apt-get update
  
  [Regression Potentional]
  Currently none as networking didn't work initially.

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

Title:
  lxc postinst script checks available interfaces, can choose

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+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 1508744] Re: Upgrade to Ubuntu 15.10 Broken: lxc-net.service fails on upgrade

[Adam Stokes]

I hit this too, I actually just had to run:

/usr/lib/x86_64-linux-gnu/lxc/lxc-net stop

And it seemed to put itself back into a state that systemd could work
with

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

Title:
  Upgrade to Ubuntu 15.10 Broken: lxc-net.service fails on upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1508744/+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 1486296] [NEW] Unable to start VMs under a lxc container

[Adam Stokes]

Public bug reported:

Our installer attempts to load VM's within an lxc container. This worked
on trusty, however, with the latest releases from vivid and wily those
VM's are unable to start. This affects running juju-local within a
container as well.

We think it has something to do with cgmanager/cgproxy, however, we can
manually run and launch qemu just fine within the container. This could
potentially be an issue with libvirt attempt to set cgroup values for
the qemu processes.

The current workaround to get a VM to start within a vivid and wily
container running LXC 1.1.2+ is to disable cgroups in
/etc/libvirt/qemu.conf

I'm starting this bug and will ask Ryan Harper to provide a more in-
depth result of his debugging, but, wanted to have this on the radar.

Specs:

Host:
Vivid, kernel: 3.19.0-15-generic, lxc: 1.1.3+stable~20150815-0227-0ubuntu1~vivid

Container:
Vivid, kernel: 3.19.0-15-generic, lxc: 1.1.2-0ubuntu3.1, libvirt 
1.2.12-0ubuntu14.1

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

** Affects: libvirt (Ubuntu Vivid)
 Importance: Undecided
 Status: New

** Affects: libvirt (Ubuntu Wily)
 Importance: Undecided
 Status: New


** Tags: cloud-installer

** Also affects: libvirt (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: libvirt (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Tags added: cloud-installer

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

Title:
  Unable to start VMs under a lxc container

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1486296/+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 1481337] Re: please update keepalived to version 1.2.17 or higher

[Adam Stokes]

** Also affects: keepalived (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: keepalived (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: keepalived (Ubuntu Vivid)
   Importance: Undecided
   Status: New

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

Title:
  please update keepalived to version 1.2.17 or higher

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1481337/+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 1421375] Re: AttributeError when attempting to access _sys.maxint

[Adam Stokes]

Tested with python3-netaddr 0.7.10-1ubuntu1.1

code:
In[2]:from netaddr import IPSet

In [3]: ,.join(str(x) for x in list(IPSet(['10.0.4.0/24'])))
Out[3]: 
'10.0.4.0,10.0.4.1,10.0.4.2,10.0.4.3,10.0.4.4,10.0.4.5,10.0.4.6,10.0.4.7,10.0.4.8,10.0.4.9,10.0.4.10,10.0.4.11,10.0.4.12,10.0.4.13,10.0.4.14,10.0.4.15,10.0.4.16,10.0.4.17,10.0.4.18,10.0.4.19,10.0.4.20,10.0.4.21,10.0.4.22,10.0.4.23,10.0.4.24,10.0.4.25,10.0.4.26,10.0.4.27,10.0.4.28,10.0.4.29,10.0.4.30,10.0.4.31,10.0.4.32,10.0.4.33,10.0.4.34,10.0.4.35,10.0.4.36,10.0.4.37,10.0.4.38,10.0.4.39,10.0.4.40,10.0.4.41,10.0.4.42,10.0.4.43,10.0.4.44,10.0.4.45,10.0.4.46,10.0.4.47,10.0.4.48,10.0.4.49,10.0.4.50,10.0.4.51,10.0.4.52,10.0.4.53,10.0.4.54,10.0.4.55,10.0.4.56,10.0.4.57,10.0.4.58,10.0.4.59,10.0.4.60,10.0.4.61,10.0.4.62,10.0.4.63,10.0.4.64,10.0.4.65,10.0.4.66,10.0.4.67,10.0.4.68,10.0.4.69,10.0.4.70,10.0.4.71,10.0.4.72,10.0.4.73,10.0.4.74,10.0.4.75,10.0.4.76,10.0.4.77,10.0.4.78,10.0.4.79,10.0.4.80,10.0.4.81,10.0.4.82,10.0.4.83,10.0.4.84,10.0.4.85,10.0.4.86,10.0.4.87,10.0.4.88,10.0.4.89,10.0.4.90,10.0.4.91,10.0.4.92,10.0.4.93,10.0.4.94,10.0.4.95,10.0.4.96,10.0.4.97,10.0.4.98,10.0.4.99
 
,10.0.4.100,10.0.4.101,10.0.4.102,10.0.4.103,10.0.4.104,10.0.4.105,10.0.4.106,10.0.4.107,10.0.4.108,10.0.4.109,10.0.4.110,10.0.4.111,10.0.4.112,10.0.4.113,10.0.4.114,10.0.4.115,10.0.4.116,10.0.4.117,10.0.4.118,10.0.4.119,10.0.4.120,10.0.4.121,10.0.4.122,10.0.4.123,10.0.4.124,10.0.4.125,10.0.4.126,10.0.4.127,10.0.4.128,10.0.4.129,10.0.4.130,10.0.4.131,10.0.4.132,10.0.4.133,10.0.4.134,10.0.4.135,10.0.4.136,10.0.4.137,10.0.4.138,10.0.4.139,10.0.4.140,10.0.4.141,10.0.4.142,10.0.4.143,10.0.4.144,10.0.4.145,10.0.4.146,10.0.4.147,10.0.4.148,10.0.4.149,10.0.4.150,10.0.4.151,10.0.4.152,10.0.4.153,10.0.4.154,10.0.4.155,10.0.4.156,10.0.4.157,10.0.4.158,10.0.4.159,10.0.4.160,10.0.4.161,10.0.4.162,10.0.4.163,10.0.4.164,10.0.4.165,10.0.4.166,10.0.4.167,10.0.4.168,10.0.4.169,10.0.4.170,10.0.4.171,10.0.4.172,10.0.4.173,10.0.4.174,10.0.4.175,10.0.4.176,10.0.4.177,10.0.4.178,10.0.4.179,10.0.4.180,10.0.4.181,10.0.4.182,10.0.4.183,10.0.4.184,10.0.4.185,10.0.4.186,10.0.4.187,10.0.4.188,10.0.4.189,10.0.4
 
.190,10.0.4.191,10.0.4.192,10.0.4.193,10.0.4.194,10.0.4.195,10.0.4.196,10.0.4.197,10.0.4.198,10.0.4.199,10.0.4.200,10.0.4.201,10.0.4.202,10.0.4.203,10.0.4.204,10.0.4.205,10.0.4.206,10.0.4.207,10.0.4.208,10.0.4.209,10.0.4.210,10.0.4.211,10.0.4.212,10.0.4.213,10.0.4.214,10.0.4.215,10.0.4.216,10.0.4.217,10.0.4.218,10.0.4.219,10.0.4.220,10.0.4.221,10.0.4.222,10.0.4.223,10.0.4.224,10.0.4.225,10.0.4.226,10.0.4.227,10.0.4.228,10.0.4.229,10.0.4.230,10.0.4.231,10.0.4.232,10.0.4.233,10.0.4.234,10.0.4.235,10.0.4.236,10.0.4.237,10.0.4.238,10.0.4.239,10.0.4.240,10.0.4.241,10.0.4.242,10.0.4.243,10.0.4.244,10.0.4.245,10.0.4.246,10.0.4.247,10.0.4.248,10.0.4.249,10.0.4.250,10.0.4.251,10.0.4.252,10.0.4.253,10.0.4.254,10.0.4.255'


** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  AttributeError when attempting to access _sys.maxint

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-netaddr/+bug/1421375/+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 1421375] Re: AttributeError when attempting to access _sys.maxint

[Adam Stokes]

** Patch added: python-netaddr_0.7.10-1ubuntu14.04.2.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/python-netaddr/+bug/1421375/+attachment/4318202/+files/python-netaddr_0.7.10-1ubuntu14.04.2.debdiff

** Tags added: cloud-installer

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

Title:
  AttributeError when attempting to access _sys.maxint

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-netaddr/+bug/1421375/+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 1421375] [NEW] AttributeError when attempting to access _sys.maxint

[Adam Stokes]

Public bug reported:

[Impact]
Anyone on Trusty wishing to utilize IPSets for gathering ranges of IPs.

[Test Case]
Code to reproduce:
from netaddr import IPSet
def get_ip_set(cidr):
 Returns a list of ip's in cidr for use in juju's no-proxy setting

ips = list(IPSet([cidr]))
return ,.join(str(x) for x in ips)

get_ip_set('10.0.4.0/24')

[Regression Potentional]
None

[Other Info]
Traceback (most recent call last):
  File stdin, line 1, in module
  File /usr/share/openstack/cloudinstall/netutils.py, line 78, in get_ip_set
ips = list(IPSet([cidr]))
  File /usr/lib/python3/dist-packages/netaddr/ip/sets.py, line 518, in __len__
if size  _sys.maxint:
AttributeError: 'module' object has no attribute 'maxint'

** Affects: python-netaddr (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: python-netaddr (Ubuntu Trusty)
 Importance: High
 Status: New


** Tags: cloud-installer

** Patch added: python-netaddr_0.7.10-1ubuntu14.04.2.debdiff
   
https://bugs.launchpad.net/bugs/1421375/+attachment/4318195/+files/python-netaddr_0.7.10-1ubuntu14.04.2.debdiff

** Also affects: python-netaddr (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: python-netaddr (Ubuntu Trusty)
   Importance: Undecided = High

** Changed in: python-netaddr (Ubuntu Trusty)
Milestone: None = ubuntu-14.04.2

** Patch removed: python-netaddr_0.7.10-1ubuntu14.04.2.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/python-netaddr/+bug/1421375/+attachment/4318195/+files/python-netaddr_0.7.10-1ubuntu14.04.2.debdiff

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

Title:
  AttributeError when attempting to access _sys.maxint

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-netaddr/+bug/1421375/+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 1307733] Re: python3-netaddr 0.7.10 with poor python3 support

[Adam Stokes]

** Patch removed: python-netaddr_0.7.10-1ubuntu14.04.2.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/python-netaddr/+bug/1307733/+attachment/4318193/+files/python-netaddr_0.7.10-1ubuntu14.04.2.debdiff

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

Title:
  python3-netaddr 0.7.10 with poor python3 support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-netaddr/+bug/1307733/+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 1307733] Re: python3-netaddr 0.7.10 with poor python3 support

[Adam Stokes]

** Patch added: python-netaddr_0.7.10-1ubuntu14.04.2.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/python-netaddr/+bug/1307733/+attachment/4318193/+files/python-netaddr_0.7.10-1ubuntu14.04.2.debdiff

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

Title:
  python3-netaddr 0.7.10 with poor python3 support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-netaddr/+bug/1307733/+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 1307733] Re: python3-netaddr 0.7.10 with poor python3 support

[Adam Stokes]

James,

I looked into using this module in our cloud installer, one bug in
particular that exists in 0.7.10 but not in 0.7.13 is the use of
sys.maxint:


Traceback (most recent call last):
  File stdin, line 1, in module
  File /usr/share/openstack/cloudinstall/netutils.py, line 78, in get_ip_set
ips = list(IPSet([cidr]))
  File /usr/lib/python3/dist-packages/netaddr/ip/sets.py, line 518, in __len__
if size  _sys.maxint:
AttributeError: 'module' object has no attribute 'maxint'

Code to reproduce:
from netaddr import IPSet
def get_ip_set(cidr):
 Returns a list of ip's in cidr for use in juju's no-proxy setting

ips = list(IPSet([cidr]))
return ,.join(str(x) for x in ips)

get_ip_set('10.0.4.0/24')

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

Title:
  python3-netaddr 0.7.10 with poor python3 support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-netaddr/+bug/1307733/+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 1307733] Re: python3-netaddr 0.7.10 with poor python3 support

[Adam Stokes]

Looks like a small typo

if size  _sys.maxint should be if size  _sys_maxint

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

Title:
  python3-netaddr 0.7.10 with poor python3 support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-netaddr/+bug/1307733/+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 1382774] Re: Postgresql installation for MAAS fails on locales missing language packs

[Adam Stokes]

** Tags added: cloud-installer

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

Title:
  Postgresql installation for MAAS fails on locales missing language
  packs

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1382774/+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 1382774] Re: Postgresql installation for MAAS fails on locales missing language packs

[Adam Stokes]

We are experiencing this issue with the cloud installer. Specifically
when someone is ssh'ed into a remote machine to perform the
installation.

For reference: https://github.com/Ubuntu-Solutions-Engineering
/openstack-installer/issues/236

Our workaround is to make sure language-pack-en is installed.

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

Title:
  Postgresql installation for MAAS fails on locales missing language
  packs

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1382774/+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 1387881] Re: qemu fails to recognize full virtualization

[Adam Stokes]

I just added qemu-kvm as a dependency for the openstack installer. It is
probably correct in assuming that virtinst shouldn't depend on qemu-kvm
since you can do paravirtualized.

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

Title:
  qemu fails to recognize full virtualization

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1387881/+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 1387881] Re: qemu fails to recognize full virtualization

[Adam Stokes]

So adding qemu-kvm fixed the issue with running nested KVM. I think
though the problem still exists on a non nested environment.

I'll get with the user who encountered this and see if I can get some
more logs.

Thanks

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

Title:
  qemu fails to recognize full virtualization

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1387881/+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 1387881] Re: qemu fails to recognize full virtualization

[Adam Stokes]

David,

Could you attach the collection of:

apport-collect 1387881

Also the output of:

dpkg -l |grep qemu

On the affected NUCs if the problem still persists?

Thanks,
Adam

** Tags added: kernel-unable-to-test-upstream

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

Title:
  qemu fails to recognize full virtualization

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1387881/+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 1387002] Re: typo in maas-region-controller.postrm stops remove/purge from correctly calling dbconfig

[Adam Stokes]

** Changed in: maas (Ubuntu)
   Importance: Undecided = High

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

Title:
  typo in maas-region-controller.postrm stops remove/purge from
  correctly calling dbconfig

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1387002/+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 1346538] Re: maas-dns fails to install due to missing config file for bind9

[Adam Stokes]

Potentional fix attached as an MP along with reproducer steps. I've
bumped the importance to get further attention on this.

Thank you,
Adam

** Changed in: maas (Ubuntu)
   Importance: Undecided = High

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

Title:
  maas-dns fails to install due to missing config file for bind9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1346538/+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 1322302] Re: local provider is very slow to tranistion from agent-status: pending

[Adam Stokes]

Reproducer steps:

Create a trusty virtual machine using the defaults provided with uvt tool.
ssh into that virtual machine and setup juju environments.yaml to be a local 
provider with a container-type: kvm

juju bootstrap
juju add-machine

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

Title:
  local provider is very slow to tranistion from agent-status: pending

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1322302/+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 1322302] Re: local provider is very slow to tranistion from agent-status: pending

[Adam Stokes]

environments.yaml:

default: local

environments:
  local:
type: local
container: kvm
lxc-use-clone: true

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

Title:
  local provider is very slow to tranistion from agent-status: pending

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1322302/+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 1315216] Re: lxc nested within kvm machines do not use lxc-clone

[Adam Stokes]

Added Trusty so we can track SRU when filed

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

** Also affects: juju-core (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: juju-core (Ubuntu)
   Importance: Undecided = High

** Changed in: juju-core (Ubuntu Trusty)
   Importance: Undecided = High

** Changed in: juju-core (Ubuntu)
   Status: New = Confirmed

** Changed in: juju-core (Ubuntu Trusty)
   Status: New = Confirmed

** Changed in: juju-core (Ubuntu Trusty)
Milestone: None = ubuntu-14.04.1

** Description changed:

- When deploying services within an LXC nested in a KVM machine the lxc-
- clone support is not used.
+ [Impact]
+ Users wishing to use nested lxc containers will benefit from the additional 
speed that cloning provides.
+ 
+ [Test Case]
+ When deploying services within an LXC nested in a KVM machine the lxc-clone 
support is not used.
  
  status output:
  
  environment: local
  machines:
-   0:
- agent-state: started
- agent-version: 1.18.1.1
- dns-name: localhost
- instance-id: localhost
- series: trusty
-   1:
- agent-state: started
- agent-version: 1.18.1.1
- dns-name: 10.0.3.129
- instance-id: poe-local-machine-1
- series: trusty
- containers:
-   1/lxc/0:
- instance-id: pending
- series: precise
- hardware: arch=amd64 cpu-cores=1 mem=512M root-disk=8192M
+   0:
+ agent-state: started
+ agent-version: 1.18.1.1
+ dns-name: localhost
+ instance-id: localhost
+ series: trusty
+   1:
+ agent-state: started
+ agent-version: 1.18.1.1
+ dns-name: 10.0.3.129
+ instance-id: poe-local-machine-1
+ series: trusty
+ containers:
+   1/lxc/0:
+ instance-id: pending
+ series: precise
+ hardware: arch=amd64 cpu-cores=1 mem=512M root-disk=8192M
  services:
-   wordpress:
- charm: cs:precise/wordpress-21
- exposed: false
- relations:
-   loadbalancer:
-   - wordpress
- units:
-   wordpress/0:
- agent-state: pending
- machine: 1/lxc/0
+   wordpress:
+ charm: cs:precise/wordpress-21
+ exposed: false
+ relations:
+   loadbalancer:
+   - wordpress
+ units:
+   wordpress/0:
+ agent-state: pending
+ machine: 1/lxc/0
  
  lxc-ls output from the kvm machine
  
  ubuntu@ubuntu:~$ sudo lxc-ls --fancy
- NAME  STATE IPV4  I  PV6  
AUTOSTART  
+ NAME  STATE IPV4  I  PV6  
AUTOSTART
  -
  juju-machine-1-lxc-0  RUNNING  10.0.3.105 - NO
  
  No juju-trusty-template is ever defined for re-use.
  
+ [Regression Potentional]
+ This only applies to new bootstrapped environments with lxc-use-clone 
applied. Existing environments will continue unaffected.
+ 
+ 
  Thanks
  Adam

** Description changed:

  [Impact]
- Users wishing to use nested lxc containers will benefit from the additional 
speed that cloning provides.
+ When deploying services within an LXC nested in a KVM machine the lxc-clone 
support is not used.
  
  [Test Case]
- When deploying services within an LXC nested in a KVM machine the lxc-clone 
support is not used.
  
  status output:
  
  environment: local
  machines:
    0:
  agent-state: started
  agent-version: 1.18.1.1
  dns-name: localhost
  instance-id: localhost
  series: trusty
    1:
  agent-state: started
  agent-version: 1.18.1.1
  dns-name: 10.0.3.129
  instance-id: poe-local-machine-1
  series: trusty
  containers:
    1/lxc/0:
  instance-id: pending
  series: precise
  hardware: arch=amd64 cpu-cores=1 mem=512M root-disk=8192M
  services:
    wordpress:
  charm: cs:precise/wordpress-21
  exposed: false
  relations:
    loadbalancer:
    - wordpress
  units:
    wordpress/0:
  agent-state: pending
  machine: 1/lxc/0
  
  lxc-ls output from the kvm machine
  
  ubuntu@ubuntu:~$ sudo lxc-ls --fancy
  NAME  STATE IPV4  I  PV6  
AUTOSTART
  -
  juju-machine-1-lxc-0  RUNNING  10.0.3.105 - NO
  
  No juju-trusty-template is ever defined for re-use.
  
  [Regression Potentional]
  This only applies to new bootstrapped environments with lxc-use-clone 
applied. Existing environments will continue unaffected.
  
- 
  Thanks
  Adam

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

Title:
  lxc nested within kvm machines do not use lxc-clone

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

-- 
Ubuntu-server-bugs mailing list

[Bug 1317680] Re: can't juju add machine when multiple images with same arch/release exist

[Adam Stokes]

** Tags added: cloud-installer

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

Title:
  can't juju add machine when multiple images with same arch/release
  exist

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1317680/+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 1238390] Re: maas-region-controller debconf config has a non-existent 'dbc_go'

[Adam Stokes]

Fixed in later version of maas

** Changed in: cloud-archive
   Status: Triaged = Fix Released

** Changed in: maas (Ubuntu)
   Status: Triaged = Fix Released

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

Title:
  maas-region-controller debconf config has a non-existent 'dbc_go'

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1238390/+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 1299588] Re: LXC permission denied issue with 1.17.7

[Adam Stokes]

** Tags added: cloud-installer

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

Title:
  LXC permission denied issue with 1.17.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1299588/+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 1274443] Re: Retro-fit support for picking up package mirror settings onto Precise for Fastpath Installer

[Adam Stokes]

@Scott,

mind if i take this and work on a backport for Precise? AFAICT it
shouldn't be that invasive.

Thanks
Adam

** Also affects: curtin (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Changed in: curtin (Ubuntu)
 Assignee: (unassigned) = Adam Stokes (adam-stokes)

** Changed in: curtin (Ubuntu Precise)
 Assignee: (unassigned) = Adam Stokes (adam-stokes)

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

Title:
  Retro-fit support for picking up package mirror settings onto Precise
  for Fastpath Installer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1274443/+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 1238390] Re: maas-region-controller debconf config has a non-existent 'dbc_go'

[Adam Stokes]

Could we have this targetted to be fixed by 14.04?

Thanks
Adam

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

Title:
  maas-region-controller debconf config has a non-existent 'dbc_go'

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1238390/+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 1211876] Re: keepalived reload buggy due to improper ipv4 address comparison

[Adam Stokes]

500 http://nova.clouds.archive.ubuntu.com/ubuntu/ raring-proposed/main
amd64 -- maybe use the default archive to do your test instead of
nova.clouds?

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

Title:
  keepalived reload buggy due to improper ipv4 address comparison

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1211876/+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 1211876] Re: keepalived reload buggy due to improper ipv4 address comparison

[Adam Stokes]

** Changed in: keepalived (Ubuntu Quantal)
   Importance: Undecided = High

** Changed in: keepalived (Ubuntu Raring)
   Importance: Undecided = High

** Changed in: keepalived (Ubuntu Precise)
   Importance: Undecided = High

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

Title:
  keepalived reload buggy due to improper ipv4 address comparison

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1211876/+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 1211876] Re: keepalived reload buggy due to improper ipv4 address comparison

[Adam Stokes]

** Changed in: keepalived (Ubuntu)
   Status: Confirmed = Fix Released

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

Title:
  keepalived reload buggy due to improper ipv4 address comparison

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1211876/+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 1211876] Re: keepalived reload buggy

[Adam Stokes]

** Changed in: keepalived (Ubuntu Precise)
 Assignee: (unassigned) = Adam Stokes (adam-stokes)

** Changed in: keepalived (Ubuntu Quantal)
 Assignee: (unassigned) = Adam Stokes (adam-stokes)

** Changed in: keepalived (Ubuntu Raring)
 Assignee: (unassigned) = Adam Stokes (adam-stokes)

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

Title:
  keepalived reload buggy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1211876/+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 1211876] Re: keepalived reload buggy

[Adam Stokes]

** Description changed:

- There are at least 2 identified problems with keepalived on Precise when
- trying to reload the configuration (/etc/keepalived/keepalived.conf):
+ [Impact]
+ There are at least 2 identified problems with keepalived on Precise when 
trying to reload the configuration (/etc/keepalived/keepalived.conf):
  
  (a) The removal of a server from the cluster does not work when the port
  of that server is in use by another member server
  
  (b) The change of weight of a cluster member does not work
  
  Reload is done by either:
  
  1. sudo service keepalived reload
  2. sudo kill -HUP `pidof keepalived`
  
  The upstream devel list suggests that issue (a) [1] has been resolved in
  version 1.2.3 which is currently only in Debian unstable via version
  1.2.7.  I can't find the actual bug supposedly filed by 'Ronie Gilberto
  Henrich'.  I have not tested 1.2.7 as it is not easily available to me.
  
  The pertinent entry for (a) in the upstream changelog [2] I believe is
  here:
  
  {{{ * check : Fix IPv4 address comparison routine. }}}
  
  This bug is a request to have fixes for both issues ([3] for (a))
  introduced into Ubuntu 12.04.
  
  [1]: http://comments.gmane.org/gmane.linux.keepalived.devel/3708
  [2]: http://www.keepalived.org/changelog.html
  [3]: 
https://github.com/acassen/keepalived/commit/e7931c851ecd359379c6bbc5b39287e36cbfbf25
+ 
+ [Test Case]
+ (a) Stop keepalived
+ 
+ $ sudo service keepalived stop
+ 
+ (b) Begin with a simple configuration file (attached: keepalived.conf)
+ 
+ $ cat keepalived.conf | sudo tee /etc/keepalived/keepalived.conf
+ $ sudo service keepalived start
+ $ sudo ipvsadm -Ln
+ 
+ IP Virtual Server version 1.2.1 (size=4096)
+ Prot LocalAddress:Port Scheduler Flags
+   - RemoteAddress:Port Forward Weight ActiveConn InActConn
+ TCP 192.168.0.100:80 wrr
+   - 192.168.1.101:8080 Masq 1 0 0
+   - 192.168.1.102:8080 Masq 1 0 0
+ 
+ (c) Add a stanza to the configuration file (a server with a port that is
+ in use by another server)
+ 
+ --
+ real_server 192.168.1.103 8080 {
+ weight 1
+ inhibit_on_failure
+ }
+ --
+ 
+ (d) Reload the configuration
+ 
+ $ sudo service keepalived reload
+ $ sudo ipvsadm -Ln
+ 
+ --
+ IP Virtual Server version 1.2.1 (size=4096)
+ Prot LocalAddress:Port Scheduler Flags
+   - RemoteAddress:Port Forward Weight ActiveConn InActConn
+ TCP 192.168.0.100:80 wrr
+   - 192.168.1.101:8080 Masq 1 0 0
+   - 192.168.1.102:8080 Masq 1 0 0
+   - 192.168.1.103:8080 Masq 1 0 0
+ --
+ 
+ (e) Remove the .103 stanza
+ (f) Perform step (d) above
+ 
+ --
+ IP Virtual Server version 1.2.1 (size=4096)
+ Prot LocalAddress:Port Scheduler Flags
+   - RemoteAddress:Port Forward Weight ActiveConn InActConn
+ TCP 192.168.0.100:80 wrr
+   - 192.168.1.101:8080 Masq 1 0 0
+   - 192.168.1.102:8080 Masq 1 0 0
+   - 192.168.1.103:8080 Masq 1 0 0
+ --
+ 
+ Note the .103 server remains.
+ 
+ 4B. Steps to Reproduce issue #2:
+ 
+ (a) Perform steps (a) and (b) from 4A
+ (b) Edit a stanza in the configuration file (change weight from '1' to '0' in 
the .102 server)
+ 
+ --
+ real_server 192.168.1.102 8080 {
+ weight 0
+ inhibit_on_failure
+ }
+ --
+ 
+ (c) Perform step (d) from 4A
+ 
+ --
+ P Virtual Server version 1.2.1 (size=4096)
+ Prot LocalAddress:Port Scheduler Flags
+   - RemoteAddress:Port Forward Weight ActiveConn InActConn
+ TCP 192.168.0.100:80 wrr
+   - 192.168.1.101:8080 Masq 1 0 0
+   - 192.168.1.102:8080 Masq 1 0 0
+ --
+ 
+ Note the original weight of '1' for .102 server remains.
+ 
+ 4C. Steps to Counterprove issue #1:
+ 
+ (a) Perform steps (a) and (b) from 4A
+ (b) Add a stanza to the configuration file (a server with a port that is not 
in use by another server)
+ 
+ --
+ real_server 192.168.1.103 8081 {
+ weight 1
+ inhibit_on_failure
+ }
+ --
+ 
+ (c) Perform step (d) from 4A
+ 
+ --
+ IP Virtual Server version 1.2.1 (size=4096)
+ Prot LocalAddress:Port Scheduler Flags
+   - RemoteAddress:Port Forward Weight ActiveConn InActConn
+ TCP 192.168.0.100:80 wrr
+   - 192.168.1.101:8080 Masq 1 0 0
+   - 192.168.1.102:8080 Masq 1 0 0
+   - 192.168.1.103:8081 Masq 1 0 0
+ --
+ 
+ (d) Remove the .103 stanza from the configuration file
+ (e) Perform step (d) from 4A
+ 
+ --
+ IP Virtual Server version 1.2.1 (size=4096)
+ Prot LocalAddress:Port Scheduler Flags
+   - RemoteAddress:Port Forward Weight ActiveConn InActConn
+ TCP 192.168.0.100:80 wrr
+   - 192.168.1.101:8080 Masq 1 0 0
+   - 192.168.1.102:8080 Masq 1 0 0
+ --
+ 
+ Note the .103 server does not remain.
+ 
+ 5. Known Workaround:
+ 
+ - Restart the daemon:
+ 
+ $ sudo service keepalived restart
+ 
+ OR
+ 
+ - Manage the daemon with ipvsadm:
+ 
+ (a) Add a server
+ 
+ $ sudo ipvsadm -a -t 192.168.0.100:80 -r 192.168.1.103:8080 -m
+ 
+ 

[Bug 1211876] Re: keepalived reload buggy

[Adam Stokes]

** Patch added: keepalived_1.2.2-3ubuntu2.12.10.1.quantal.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1211876/+attachment/3845142/+files/keepalived_1.2.2-3ubuntu2.12.10.1.quantal.debdiff

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

Title:
  keepalived reload buggy due to improper ipv4 address comparison

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1211876/+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 1211876] Re: keepalived reload buggy

[Adam Stokes]

** Patch added: keepalived_1.2.2-3ubuntu2.13.04.1.raring.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1211876/+attachment/3845143/+files/keepalived_1.2.2-3ubuntu2.13.04.1.raring.debdiff

** Summary changed:

- keepalived reload buggy
+ keepalived reload buggy due to improper ipv4 address comparison

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

Title:
  keepalived reload buggy due to improper ipv4 address comparison

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1211876/+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 1211876] Re: keepalived reload buggy

[Adam Stokes]

Ill have the SRU ready by Friday (Sept 27th)

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

Title:
  keepalived reload buggy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1211876/+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 799623] Re: Incorrect generated logrotate file

[Adam Stokes]

** Also affects: clamav (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: clamav (Ubuntu Quantal)
   Importance: Undecided
   Status: New

** Also affects: clamav (Ubuntu Raring)
   Importance: Undecided
   Status: New

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

Title:
  Incorrect generated logrotate file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/799623/+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 995719] Re: process_name.rb removed in 2.7.11 but still provided by puppet-common

[Adam Stokes]

According to those posted bugs on puppetlabs they just removed the file
with the intention of added it back in a future release.  Since I dont
see any other modifications that directly relate to this bug I'm going
to package up a proposed fix and have you guys test.

Thanks for the report
Adam

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

Title:
  process_name.rb removed in 2.7.11 but still provided by puppet-common

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/995719/+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 995719] Re: process_name.rb removed in 2.7.11 but still provided by puppet-common

[Adam Stokes]

Here is the commit for reference

https://github.com/puppetlabs/puppet/commit/25bbecf

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

Title:
  process_name.rb removed in 2.7.11 but still provided by puppet-common

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/995719/+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 995719] Re: process_name.rb removed in 2.7.11 but still provided by puppet-common

[Adam Stokes]

** Patch added: puppet_2.7.11-1ubuntu2.5.precise.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/995719/+attachment/3838710/+files/puppet_2.7.11-1ubuntu2.5.precise.debdiff

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

Title:
  process_name.rb removed in 2.7.11 but still provided by puppet-common

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/995719/+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 995719] Re: process_name.rb removed in 2.7.11 but still provided by puppet-common

[Adam Stokes]

** Description changed:

- Hi,
- 
- This is related to
- https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/959597 where
- upstream has removed process_name.rb in 2.7.11 but it is still packaged
- and provided by puppet-common.
+ [Impact]
+ This is related to 
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/959597 where upstream has 
removed process_name.rb in 2.7.11 but it is still packaged and provided by 
puppet-common.
  
  [ This plugin frequently causes puppet to hang and requires manual
  sysadmin intervention to resolve. -- pjdc, 2012-05-10 ]
  
  Source tarball for 2.7.10 from puppetlabs:
  
  [hloeung@darkon puppet-2.7.10]$ find . -type f -name '*process_name*'
  ./spec/unit/util/instrumentation/listeners/process_name_spec.rb
  ./lib/puppet/util/instrumentation/listeners/process_name.rb
  [hloeung@darkon puppet-2.7.10]$
  
  Source tarball for 2.7.11 from puppetlabs:
  
  [hloeung@darkon puppet-2.7.11]$ find . -type f -name '*process_name*'
  [hloeung@darkon puppet-2.7.11]$
  
  [hloeung@darkon puppet-2.7.10]$ dpkg-query -S 
/usr/lib/ruby/1.8/puppet/util/instrumentation/listeners/process_name.rb
  puppet-common: 
/usr/lib/ruby/1.8/puppet/util/instrumentation/listeners/process_name.rb
  
  [hloeung@darkon puppet-2.7.10]$ dpkg -l puppet-common
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version
Description
  
+++-==-==-
  ii  puppet-common  2.7.11-1ubuntu2
Centralized configuration management
+ 
+ [Test Case]
+ Install puppet and puppet server from the Precise archives
+ Loop puppet apply against a manifest and note the timelines. The process 
takes considerably longer every 2-3 times every 10 puppet runs
+ 
+ [Regression]
+ Since this is a event listener and is only initialized if the listener exist 
there should be no regression as that functionality is limited within that 
particular listener code.

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

Title:
  process_name.rb removed in 2.7.11 but still provided by puppet-common

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/995719/+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 1207102] Re: Set PXE class lease expiration to 30 seconds

[Adam Stokes]

Ping, would like to an eta when this fix will be pushed to Precise

Thanks!
Adam

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

Title:
  Set PXE class lease expiration to 30 seconds

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1207102/+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 1207102] Re: Set PXE class lease expiration to 30 seconds

[Adam Stokes]

The precise version should contain this fix as well, could I get an eta
when the next maas releases are going to be done?

Thanks!
Adam

** Also affects: maas (Ubuntu Precise)
   Importance: Undecided
   Status: New

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

Title:
  Set PXE class lease expiration to 30 seconds

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1207102/+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 1211876] Re: keepalived reload buggy

[Adam Stokes]

** Changed in: keepalived (Ubuntu)
   Importance: Undecided = High

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

Title:
  keepalived reload buggy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1211876/+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 1211876] Re: keepalived reload buggy

[Adam Stokes]

** Summary changed:

- [Precise] keepalived reload buggy
+ keepalived reload buggy

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

Title:
  keepalived reload buggy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1211876/+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 1183300] Re: Please upgrade keepalived to the latest upstream version

[Adam Stokes]

Ah i was trying to research where those DEB* variables were used thanks
for clearing that up. I'll update the debdiffs today to fix the
indentation in the changelog

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

Title:
  Please upgrade keepalived to the latest upstream version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1183300/+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 1183300] Re: Please upgrade keepalived to the latest upstream version

[Adam Stokes]

Updated from suggestions in reviewer's comments

** Patch removed: keepalived_1.2.7-1_keepalived_1.2.7-1ubuntu1.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1183300/+attachment/3770114/+files/keepalived_1.2.7-1_keepalived_1.2.7-1ubuntu1.debdiff

** Patch removed: keepalived_1.2.7-1ubuntu1.merge.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1183300/+attachment/3770115/+files/keepalived_1.2.7-1ubuntu1.merge.debdiff

** Patch added: keepalived_1.2.7-1_keepalived_1.2.7-1ubuntu1.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1183300/+attachment/3771189/+files/keepalived_1.2.7-1_keepalived_1.2.7-1ubuntu1.debdiff

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

Title:
  Please upgrade keepalived to the latest upstream version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1183300/+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 1183300] Re: Please upgrade keepalived to the latest upstream version

[Adam Stokes]

Updated from suggestions in reviewer's comments

** Patch added: keepalived_1.2.7-1ubuntu1.merge.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1183300/+attachment/3771190/+files/keepalived_1.2.7-1ubuntu1.merge.debdiff

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

Title:
  Please upgrade keepalived to the latest upstream version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1183300/+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 1183300] Re: Please upgrade keepalived to the latest upstream version

[Adam Stokes]

** Patch added: keepalived_1.2.7-1_keepalived_1.2.7-1ubuntu1.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1183300/+attachment/3770114/+files/keepalived_1.2.7-1_keepalived_1.2.7-1ubuntu1.debdiff

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

Title:
  Please upgrade keepalived to the latest upstream version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1183300/+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 1183300] Re: Please upgrade keepalived to the latest upstream version

[Adam Stokes]

** Patch added: keepalived_1.2.7-1ubuntu1.merge.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1183300/+attachment/3770115/+files/keepalived_1.2.7-1ubuntu1.merge.debdiff

** Changed in: keepalived (Ubuntu)
   Status: Triaged = Confirmed

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

Title:
  Please upgrade keepalived to the latest upstream version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1183300/+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 1183300] Re: Please upgrade keepalived to the latest upstream version

[Adam Stokes]

** Changed in: keepalived (Ubuntu)
   Importance: Wishlist = Medium

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

Title:
  Please upgrade keepalived to the latest upstream version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1183300/+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 1199037] Re: backport eventlet exception context fix

[Adam Stokes]

Thanks Brian,

Ed this should be good to go now and in process of being reviewed by SRU
team.

Adam

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

Title:
  backport eventlet exception context fix

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-eventlet/+bug/1199037/+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 1207102] Re: Set PXE class lease expiration to 30 seconds

[Adam Stokes]

So the debdiff was uploaded and referenced bug 1069570 after I marked
that one invalid. So I guess we can dis-regard this one?

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

Title:
  Set PXE class lease expiration to 30 seconds

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1207102/+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 1069570] Re: 1 MAC Address, two IPs - DNS is out of sync with DHCP leases databases, I think...

[Adam Stokes]

Hmm, so I marked this bug invalid b/c I created a new bug 1207102 with
the same changes. This got uploaded anyway and referenced this bug.

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

Title:
  1 MAC Address, two IPs - DNS is out of sync with DHCP leases
  databases, I think...

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1069570/+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 1119248] Re: [SRU] nova does not set container_format when snapshotting instance with ref image deleted

[Adam Stokes]

** Changed in: nova (Ubuntu)
   Status: In Progress = Fix Released

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

Title:
  [SRU] nova does not set container_format when snapshotting instance
  with ref image deleted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1119248/+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 1199037] Re: backport eventlet exception context fix

[Adam Stokes]

** Changed in: python-eventlet (Ubuntu Raring)
   Status: In Progress = Fix Committed

** Changed in: python-eventlet (Ubuntu Raring)
   Status: Fix Committed = Confirmed

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

Title:
  backport eventlet exception context fix

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-eventlet/+bug/1199037/+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 1069570] Re: 1 MAC Address, two IPs - DNS is out of sync with DHCP leases databases, I think...

[Adam Stokes]

** Changed in: maas (Ubuntu)
   Status: Invalid = In Progress

** Changed in: maas (Ubuntu)
 Assignee: (unassigned) = Adam Stokes (adam-stokes)

** Changed in: maas (Ubuntu)
   Importance: Undecided = Medium

** Changed in: maas (Ubuntu)
   Importance: Medium = High

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

Title:
  1 MAC Address, two IPs - DNS is out of sync with DHCP leases
  databases, I think...

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1069570/+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 1069570] Re: 1 MAC Address, two IPs - DNS is out of sync with DHCP leases databases, I think...

[Adam Stokes]

** Changed in: maas (Ubuntu)
   Status: In Progress = Invalid

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

Title:
  1 MAC Address, two IPs - DNS is out of sync with DHCP leases
  databases, I think...

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1069570/+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 1069570] Re: 1 MAC Address, two IPs - DNS is out of sync with DHCP leases databases, I think...

[Adam Stokes]

** Patch added: maas_1.4+bzr1539+dfsg-0ubuntu2.saucy.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1069570/+attachment/3756388/+files/maas_1.4%2Bbzr1539%2Bdfsg-0ubuntu2.saucy.debdiff

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

Title:
  1 MAC Address, two IPs - DNS is out of sync with DHCP leases
  databases, I think...

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1069570/+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 1207102] Re: Set PXE class lease expiration to 30 seconds

[Adam Stokes]

** Patch added: maas_1.4+bzr1539+dfsg-0ubuntu2.saucy.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1207102/+attachment/3756460/+files/maas_1.4%2Bbzr1539%2Bdfsg-0ubuntu2.saucy.debdiff

** Description changed:

  [impact]
  
  MAAS is failing to add all enlisted machines to DNS.  There seems to be
  a sync issue between dhcp and dns during enlishting.
  
  [test case]
  + Have MaaS 1.3 running
  + Boot machines to be controlled by MaaS and get MaaS to enlist them.
  + Go on MaaS WebUI and change ipmi data and click 'accept and commission'
  
  [regression potential]
  This is not a code change but a configuration modification. It is a 
documented option within the dhcp manual so I assume it's been tested through 
the normal means.
+ 
+ [additional]
+ Expected results:
+ 
+ subnet 192.168.134.0 netmask 255.255.255.0 {
+filename pxelinux.0;
+option subnet-mask 255.255.255.0;
+option broadcast-address 192.168.134.255;
+option domain-name-servers 192.168.134.2;
+option routers 192.168.134.1;
+range dynamic-bootp 192.168.134.10 192.168.134.20;
+ 
+ class PXE {
+   match if substring (option vendor-class-identifier, 0, 3) = PXE;
+   default-lease-time 30;
+   max-lease-time 30;
+ }
+ 
+ }
+ 
+ May 3 15:18:30 maas2 dhcpd: DHCPDISCOVER from 52:54:00:f7:72:fe via eth0
+ May 3 15:18:31 maas2 dhcpd: DHCPOFFER on 192.168.134.11 to 52:54:00:f7:72:fe 
via eth0
+ May 3 15:18:33 maas2 dhcpd: Wrote 0 class decls to leases file.
+ May 3 15:18:33 maas2 dhcpd: Wrote 0 deleted host decls to leases file.
+ May 3 15:18:33 maas2 dhcpd: Wrote 0 new dynamic host decls to leases file.
+ May 3 15:18:33 maas2 dhcpd: Wrote 11 leases to leases file.
+ May 3 15:18:33 maas2 dhcpd: DHCPREQUEST for 192.168.134.11 (192.168.134.2) 
from 52:54:00:f7:72:fe via eth0
+ May 3 15:18:33 maas2 dhcpd: DHCPACK on 192.168.134.11 to 52:54:00:f7:72:fe 
via eth0
+ 
+ lease 192.168.134.11 {
+   starts 5 2013/05/03 19:18:33;
+   ends 5 2013/05/03 19:19:03;
+   tstp 5 2013/05/03 19:19:03;
+   cltt 5 2013/05/03 19:18:33;
+   binding state free;
+   hardware ethernet 52:54:00:f7:72:fe;
+   uid \001RT\000\367r\376;
+ }

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

Title:
  Set PXE class lease expiration to 30 seconds

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1207102/+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 1207102] [NEW] Set PXE class lease expiration to 30 seconds

[Adam Stokes]

Public bug reported:

[impact]

MAAS is failing to add all enlisted machines to DNS.  There seems to be
a sync issue between dhcp and dns during enlishting.

[test case]
+ Have MaaS 1.3 running
+ Boot machines to be controlled by MaaS and get MaaS to enlist them.
+ Go on MaaS WebUI and change ipmi data and click 'accept and commission'

[regression potential]
This is not a code change but a configuration modification. It is a documented 
option within the dhcp manual so I assume it's been tested through the normal 
means.

[additional]
Expected results:

subnet 192.168.134.0 netmask 255.255.255.0 {
   filename pxelinux.0;
   option subnet-mask 255.255.255.0;
   option broadcast-address 192.168.134.255;
   option domain-name-servers 192.168.134.2;
   option routers 192.168.134.1;
   range dynamic-bootp 192.168.134.10 192.168.134.20;

class PXE {
  match if substring (option vendor-class-identifier, 0, 3) = PXE;
  default-lease-time 30;
  max-lease-time 30;
}

}

May 3 15:18:30 maas2 dhcpd: DHCPDISCOVER from 52:54:00:f7:72:fe via eth0
May 3 15:18:31 maas2 dhcpd: DHCPOFFER on 192.168.134.11 to 52:54:00:f7:72:fe 
via eth0
May 3 15:18:33 maas2 dhcpd: Wrote 0 class decls to leases file.
May 3 15:18:33 maas2 dhcpd: Wrote 0 deleted host decls to leases file.
May 3 15:18:33 maas2 dhcpd: Wrote 0 new dynamic host decls to leases file.
May 3 15:18:33 maas2 dhcpd: Wrote 11 leases to leases file.
May 3 15:18:33 maas2 dhcpd: DHCPREQUEST for 192.168.134.11 (192.168.134.2) from 
52:54:00:f7:72:fe via eth0
May 3 15:18:33 maas2 dhcpd: DHCPACK on 192.168.134.11 to 52:54:00:f7:72:fe via 
eth0

lease 192.168.134.11 {
  starts 5 2013/05/03 19:18:33;
  ends 5 2013/05/03 19:19:03;
  tstp 5 2013/05/03 19:19:03;
  cltt 5 2013/05/03 19:18:33;
  binding state free;
  hardware ethernet 52:54:00:f7:72:fe;
  uid \001RT\000\367r\376;
}

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

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

Title:
  Set PXE class lease expiration to 30 seconds

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1207102/+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 1207102] Re: Set PXE class lease expiration to 30 seconds

[Adam Stokes]

** Changed in: maas (Ubuntu)
 Assignee: (unassigned) = Andres Rodriguez (andreserl)

** Changed in: maas (Ubuntu)
   Importance: Undecided = High

** Patch removed: maas_1.4+bzr1539+dfsg-0ubuntu2.saucy.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1207102/+attachment/3756460/+files/maas_1.4%2Bbzr1539%2Bdfsg-0ubuntu2.saucy.debdiff

** Patch added: maas_1.4+bzr1539+dfsg-0ubuntu2.saucy.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1207102/+attachment/3756462/+files/maas_1.4%2Bbzr1539%2Bdfsg-0ubuntu2.saucy.debdiff

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

Title:
  Set PXE class lease expiration to 30 seconds

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1207102/+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 1003296] Re: lightdm crashed with SIGSEGV in _pam_winbind_change_pwd() when password is expiring

[Adam Stokes]

** Patch removed: samba_3.6.3-2ubuntu2.7.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1003296/+attachment/3729222/+files/samba_3.6.3-2ubuntu2.7.debdiff

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

Title:
  lightdm crashed with SIGSEGV in _pam_winbind_change_pwd() when
  password is expiring

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1003296/+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 1068145] Re: Fix for CVE-2012-3867 (puppet) is too restrictive - TLS certificates now break

[Adam Stokes]

I've started the backport process here: https://bugs.launchpad.net
/precise-backports/+bug/1194901

If anyone is interested in testing out the packages on either Precise,
Quantal, or Raring and provide feedback on that backport request it
would be greatly appreciated! This will also help speed up the backport
approval process.

Thank you
Adam

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

Title:
  Fix for CVE-2012-3867 (puppet) is too restrictive - TLS certificates
  now break

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1068145/+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 1004775] Re: NetworkManager restarts dnsmasq and adds host route on every IPv6 route lookup

[Adam Stokes]

Friendly ping to see what the status is on this issue wrt comment #23

Thanks!
Adam

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

Title:
  NetworkManager restarts dnsmasq and adds host route on every IPv6
  route lookup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1004775/+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 1004775] Re: NetworkManager restarts dnsmasq and adds host route on every IPv6 route lookup

[Adam Stokes]

Thanks Mathieu for the upload!

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

Title:
  NetworkManager restarts dnsmasq and adds host route on every IPv6
  route lookup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1004775/+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 1068145] Re: Fix for CVE-2012-3867 (puppet) is too restrictive - TLS certificates now break

[Adam Stokes]

Agreed, however, from previous discussions with the maintainers I was
under the impression this wouldn't be a trivial fix for 2.7.x.

Jeff,

Could you comment on that?

Thanks
Adam

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

Title:
  Fix for CVE-2012-3867 (puppet) is too restrictive - TLS certificates
  now break

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1068145/+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 1068145] Re: Fix for CVE-2012-3867 (puppet) is too restrictive - TLS certificates now break

[Adam Stokes]

Puppet 3.2.2 is in Saucy now. Will see how feasible it is to just do a
full backport into Precise.

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

Title:
  Fix for CVE-2012-3867 (puppet) is too restrictive - TLS certificates
  now break

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1068145/+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 962046] Re: EC2 metadata retrieval fails with spaces in a resource name

[Adam Stokes]

** Description changed:

  [Impact]
  
  Example when using a key name 'my key':
  
  Caught exception reading instance data:
  http://169.254.169.254/2009-04-04/meta-data/mpi/my key
  
  Is a boto issue, see https://github.com/boto/boto/issues/659
  
  Patches provided for Precise, Quantal and Raring. Fix already exists in
  Saucy.
  
  [Test Case]
  
  There are two ways to test this. The first provides that the change will 
affect
  the url in the required manner but does not test the package. The second will
  test the package but needs to be run within an Openstack instance against an
  API that has calls with spaces on their name.
  
  
  #!/usr/bin/env python
  import urllib
  
  resource = http://169.254.169.254/2009-04-04/meta-data/i love spaces
  print unsafe: %s % resource
  
  resource = urllib.quote(resource, safe=/:)
  print safe: %s % resource
  
  ===
  #!/usr/bin/env python
  from boto import utils
  utils.get_instance_metadata()
  
  [Regression Potential]
  
  This is a very low risk change which makes any non-alphnumeric
  characters in a meta api call name safe for urlib. It is unlikely that
  an api call name would have anything other than alphanumeric chars,
  whitespace and perhaps '_' but even if they did they would be safe here
- so there is no know regression potential.
+ so there is no known regression potential.

** Changed in: python-boto (Ubuntu Raring)
   Importance: Undecided = Medium

** Changed in: python-boto (Ubuntu Precise)
 Assignee: Chris J Arges (arges) = Edward Hope-Morley (hopem)

** Changed in: python-boto (Ubuntu Quantal)
 Assignee: Chris J Arges (arges) = Edward Hope-Morley (hopem)

** Changed in: python-boto (Ubuntu Raring)
 Assignee: Chris J Arges (arges) = Edward Hope-Morley (hopem)

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

Title:
  EC2 metadata retrieval fails with spaces in a resource name

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/962046/+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 962046] Re: EC2 metadata retrieval fails with spaces in a resource name

[Adam Stokes]

** Description changed:

+ [Impact]
+ 
  Example when using a key name 'my key':
  
  Caught exception reading instance data:
  http://169.254.169.254/2009-04-04/meta-data/mpi/my key
  
  Is a boto issue, see https://github.com/boto/boto/issues/659
+ 
+ 
+ [Test Case]
+ 
+ #!/usr/bin/env python
+ from boto import utils
+ utils.get_instance_metadata()
+ 
+ [Regression Potential]
+  This is a very low risk change. It has been tested on Precise. A quantal 
patch is also provided.

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

Title:
  EC2 metadata retrieval fails with spaces in a resource name

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/962046/+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 1068145] Re: Fix for CVE-2012-3867 (puppet) is too restrictive - TLS certificates now break

[Adam Stokes]

3.2.1 is out, once it makes it way into Debian and then Ubuntu archive
I'll work on getting a possible backport accepted for Precise, Quantal
and Raring.

Thanks
Adam

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

Title:
  Fix for CVE-2012-3867 (puppet) is too restrictive - TLS certificates
  now break

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1068145/+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 1068145] Re: Fix for CVE-2012-3867 (puppet) is too restrictive - TLS certificates now break

[Adam Stokes]

Jeff,

I've been searching through the documentation on puppet labs wiki but I
am unable to find a tentative release date for 3.2.0. Do you have that
information and if the date is set do you mind sharing that with me?

Thank you,
Adam

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

Title:
  Fix for CVE-2012-3867 (puppet) is too restrictive - TLS certificates
  now break

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1068145/+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 1069570] Re: 1 MAC Address, two IPs - DNS is out of sync with DHCP leases databases, I think...

[Adam Stokes]

** Changed in: maas (Ubuntu)
   Status: Incomplete = Invalid

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

Title:
  1 MAC Address, two IPs - DNS is out of sync with DHCP leases
  databases, I think...

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1069570/+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 1069570] Re: 1 MAC Address, two IPs - DNS is out of sync with DHCP leases databases, I think...

[Adam Stokes]

This also contains a small change to 00List to fix previous changelog
entry and not have its patch reverted.

** Patch removed: isc-dhcp_4.1.ESV-R4-0ubuntu5.8.precise.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1069570/+attachment/3631784/+files/isc-dhcp_4.1.ESV-R4-0ubuntu5.8.precise.debdiff

** Patch added: isc-dhcp_4.1.ESV-R4-0ubuntu5.8.precise.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1069570/+attachment/3638900/+files/isc-dhcp_4.1.ESV-R4-0ubuntu5.8.precise.debdiff

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

Title:
  1 MAC Address, two IPs - DNS is out of sync with DHCP leases
  databases, I think...

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1069570/+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 1069570] Re: 1 MAC Address, two IPs - DNS is out of sync with DHCP leases databases, I think...

[Adam Stokes]

** Patch removed: isc-dhcp_4.1.ESV-R4-0ubuntu5.8.precise.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1069570/+attachment/3638900/+files/isc-dhcp_4.1.ESV-R4-0ubuntu5.8.precise.debdiff

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

Title:
  1 MAC Address, two IPs - DNS is out of sync with DHCP leases
  databases, I think...

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1069570/+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 1069570] Re: 1 MAC Address, two IPs - DNS is out of sync with DHCP leases databases, I think...

[Adam Stokes]

This also contains a fix from the previous changelog to modify an
apparmor profile. Patch was removed and applied directly to debian
/apparmor-profile.dhcpd

** Patch added: isc-dhcp_4.1.ESV-R4-0ubuntu5.8.precise.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1069570/+attachment/3638941/+files/isc-dhcp_4.1.ESV-R4-0ubuntu5.8.precise.debdiff

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

Title:
  1 MAC Address, two IPs - DNS is out of sync with DHCP leases
  databases, I think...

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1069570/+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 1158465] Re: [SRU] update Windows Azure WALinuxAgent to 1.3.2 (12.04.2, 12.10 and 13.04)

[Adam Stokes]

Re: #6, what is the context of 'Resolved'? Anything you need from me to
make sure this issue is actively reviewed?

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

Title:
  [SRU] update Windows Azure WALinuxAgent to 1.3.2 (12.04.2, 12.10 and
  13.04)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1158465/+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 1069570] Re: 1 MAC Address, two IPs - DNS is out of sync with DHCP leases databases, I think...

[Adam Stokes]

** Description changed:

  Guys,
  
-  During my new tests, I tried to create two nodes simultaneously (both
+  During my new tests, I tried to create two nodes simultaneously (both
  via DHCP + PXE, not by clicking +Add node) and I hit this problem:
  
-  Same MAC Address, two different IPs:
+  Same MAC Address, two different IPs:
  
-  http://pastebin.com/8RYjGe5D
+ # The format of this file is documented in the dhcpd.leases(5) manual page.
+ # This lease file was written by isc-dhcp-4.2.4
+  
+ server-duid \000\001\000\001\030\023\243\007RT\000\360\236\231;
+  
+ lease 192.168.50.1 {
+   starts 5 2012/10/19 06:31:21;
+   ends 5 2012/10/19 18:31:21;
+   cltt 5 2012/10/19 06:31:21;
+   binding state active;
+   next binding state free;
+   rewind binding state free;
+   hardware ethernet 52:54:00:cd:6b:a2;
+   uid \001RT\000\315k\242;
+ }
+ lease 192.168.50.2 {
+   starts 5 2012/10/19 06:31:43;
+   ends 5 2012/10/19 18:31:43;
+   cltt 5 2012/10/19 06:31:43;
+   binding state active;
+   next binding state free;
+   rewind binding state free;
+   hardware ethernet 52:54:00:cd:6b:a2;
+   client-hostname maas-enlist;
+ }
+ lease 192.168.50.2 {
+   starts 5 2012/10/19 06:31:43;
+   ends 5 2012/10/19 18:31:43;
+   cltt 5 2012/10/19 06:31:43;
+   binding state active;
+   next binding state free;
+   rewind binding state free;
+   hardware ethernet 52:54:00:cd:6b:a2;
+   client-hostname maas-enlist;
+ }
+ host 192.168.50.1 {
+   dynamic;
+   hardware ethernet 52:54:00:cd:6b:a2;
+   fixed-address 192.168.50.1;
+ }
+ lease 192.168.50.1 {
+   starts 5 2012/10/19 06:31:21;
+   ends 5 2012/10/19 06:34:48;
+   tstp 5 2012/10/19 06:34:48;
+   cltt 5 2012/10/19 06:31:21;
+   binding state free;
+   hardware ethernet 52:54:00:cd:6b:a2;
+   uid \001RT\000\315k\242;
+ }
  
-  The brief is:
+  The brief is:
  
-  1- DHCP gives address 192.168.50.1 to my machine on its first boot;
+  1- DHCP gives address 192.168.50.1 to my machine on its first boot;
  
-  2- After some time, I think that after some reboots / elist / don'know
+  2- After some time, I think that after some reboots / elist / don'know
  for sure or even after commissioning it; the IP have changed to
  192.168.50.2 and got registered at DNS (192-168-50-2.test.com) that way;
  
-  3- In the end of the day, after allocate it to root and start using it
+  3- In the end of the day, after allocate it to root and start using it
  (the nodes), the DHCP gives again the IP 192.168.50.1 to my node, but
  DNS still remains with 192.158.50.2...
  
-  ---
+  ---
  
-  My second node, first starts with 192.168.50.3, got registered with
+  My second node, first starts with 192.168.50.3, got registered with
  192.168.50.4 at DNS (and at MaaS Web GUI) but the DHCP finish with
  192.168.50.3...
  
-  I'll not try maas-dns again... Too many bugs...   =(
+  I'll not try maas-dns again... Too many bugs...   =(
  
-  I think that MaaS needs some kind of glue between DHCP and DNS to
+  I think that MaaS needs some kind of glue between DHCP and DNS to
  keep it in sync.
  
  Tks!
  Thiago

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

Title:
  1 MAC Address, two IPs - DNS is out of sync with DHCP leases
  databases, I think...

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1069570/+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 1069570] Re: 1 MAC Address, two IPs - DNS is out of sync with DHCP leases databases, I think...

[Adam Stokes]

** Patch added: isc-dhcp_4.1.ESV-R4-0ubuntu5.6.1.precise.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1069570/+attachment/3631196/+files/isc-dhcp_4.1.ESV-R4-0ubuntu5.6.1.precise.debdiff

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

Title:
  1 MAC Address, two IPs - DNS is out of sync with DHCP leases
  databases, I think...

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1069570/+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 1069570] Re: 1 MAC Address, two IPs - DNS is out of sync with DHCP leases databases, I think...

[Adam Stokes]

** Description changed:

- Guys,
- 
-  During my new tests, I tried to create two nodes simultaneously (both
- via DHCP + PXE, not by clicking +Add node) and I hit this problem:
+ [Impact] 
+  During my new tests, I tried to create two nodes simultaneously (both via 
DHCP + PXE, not by clicking +Add node) and I hit this problem:
  
   Same MAC Address, two different IPs:
  
  # The format of this file is documented in the dhcpd.leases(5) manual page.
  # This lease file was written by isc-dhcp-4.2.4
-  
+ 
  server-duid \000\001\000\001\030\023\243\007RT\000\360\236\231;
-  
+ 
  lease 192.168.50.1 {
-   starts 5 2012/10/19 06:31:21;
-   ends 5 2012/10/19 18:31:21;
-   cltt 5 2012/10/19 06:31:21;
-   binding state active;
-   next binding state free;
-   rewind binding state free;
-   hardware ethernet 52:54:00:cd:6b:a2;
-   uid \001RT\000\315k\242;
+   starts 5 2012/10/19 06:31:21;
+   ends 5 2012/10/19 18:31:21;
+   cltt 5 2012/10/19 06:31:21;
+   binding state active;
+   next binding state free;
+   rewind binding state free;
+   hardware ethernet 52:54:00:cd:6b:a2;
+   uid \001RT\000\315k\242;
  }
  lease 192.168.50.2 {
-   starts 5 2012/10/19 06:31:43;
-   ends 5 2012/10/19 18:31:43;
-   cltt 5 2012/10/19 06:31:43;
-   binding state active;
-   next binding state free;
-   rewind binding state free;
-   hardware ethernet 52:54:00:cd:6b:a2;
-   client-hostname maas-enlist;
+   starts 5 2012/10/19 06:31:43;
+   ends 5 2012/10/19 18:31:43;
+   cltt 5 2012/10/19 06:31:43;
+   binding state active;
+   next binding state free;
+   rewind binding state free;
+   hardware ethernet 52:54:00:cd:6b:a2;
+   client-hostname maas-enlist;
  }
  lease 192.168.50.2 {
-   starts 5 2012/10/19 06:31:43;
-   ends 5 2012/10/19 18:31:43;
-   cltt 5 2012/10/19 06:31:43;
-   binding state active;
-   next binding state free;
-   rewind binding state free;
-   hardware ethernet 52:54:00:cd:6b:a2;
-   client-hostname maas-enlist;
+   starts 5 2012/10/19 06:31:43;
+   ends 5 2012/10/19 18:31:43;
+   cltt 5 2012/10/19 06:31:43;
+   binding state active;
+   next binding state free;
+   rewind binding state free;
+   hardware ethernet 52:54:00:cd:6b:a2;
+   client-hostname maas-enlist;
  }
  host 192.168.50.1 {
-   dynamic;
-   hardware ethernet 52:54:00:cd:6b:a2;
-   fixed-address 192.168.50.1;
+   dynamic;
+   hardware ethernet 52:54:00:cd:6b:a2;
+   fixed-address 192.168.50.1;
  }
  lease 192.168.50.1 {
-   starts 5 2012/10/19 06:31:21;
-   ends 5 2012/10/19 06:34:48;
-   tstp 5 2012/10/19 06:34:48;
-   cltt 5 2012/10/19 06:31:21;
-   binding state free;
-   hardware ethernet 52:54:00:cd:6b:a2;
-   uid \001RT\000\315k\242;
+   starts 5 2012/10/19 06:31:21;
+   ends 5 2012/10/19 06:34:48;
+   tstp 5 2012/10/19 06:34:48;
+   cltt 5 2012/10/19 06:31:21;
+   binding state free;
+   hardware ethernet 52:54:00:cd:6b:a2;
+   uid \001RT\000\315k\242;
  }
- 
-  The brief is:
  
   1- DHCP gives address 192.168.50.1 to my machine on its first boot;
  
   2- After some time, I think that after some reboots / elist / don'know
  for sure or even after commissioning it; the IP have changed to
  192.168.50.2 and got registered at DNS (192-168-50-2.test.com) that way;
  
   3- In the end of the day, after allocate it to root and start using it
  (the nodes), the DHCP gives again the IP 192.168.50.1 to my node, but
  DNS still remains with 192.158.50.2...
  
   ---
  
   My second node, first starts with 192.168.50.3, got registered with
  192.168.50.4 at DNS (and at MaaS Web GUI) but the DHCP finish with
  192.168.50.3...
  
+ [Test Case]
+ In a virtual environment: 
+ - Add 2 nodes 
+ - PXE boot the instances
+ - verify dhcp leases have 1 mac address for 2 different IPs
+ 
+ After applying latest debdiff alter the following:
+ 
+* modify /etc/maas/dhcpd.conf to include 'ignore-client-uids true'
+ 
+ re-test by adding 2 additional nodes to verify the mac address is unique
+ between both nodes.
+ 
+ [Regression Potential]
+ Low, as it adds another optional arguement to disable checking client-uids
+ 
+ -- snip --
+ 
   I'll not try maas-dns again... Too many bugs...   =(
  
   I think that MaaS needs some kind of glue between DHCP and DNS to
  keep it in sync.
  
  Tks!
  Thiago

** Patch added: isc-dhcp_4.2.4-1ubuntu10.1.quantal.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1069570/+attachment/3631255/+files/isc-dhcp_4.2.4-1ubuntu10.1.quantal.debdiff

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

Title:
  1 MAC Address, two IPs - DNS is out of sync with DHCP leases
  databases, I think...

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1069570/+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 1068145] Re: Fix for CVE-2012-3867 (puppet) is too restrictive - TLS certificates now break

[Adam Stokes]

Looks like upstream has a pending release to fix this issue positive
testing results from community.

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

Title:
  Fix for CVE-2012-3867 (puppet) is too restrictive - TLS certificates
  now break

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1068145/+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 1069570] Re: 1 MAC Address, two IPs - DNS is out of sync with DHCP leases databases, I think...

[Adam Stokes]

** Patch removed: isc-dhcp_4.1.ESV-R4-0ubuntu5.6.1.precise.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1069570/+attachment/3631196/+files/isc-dhcp_4.1.ESV-R4-0ubuntu5.6.1.precise.debdiff

** Patch removed: isc-dhcp_4.2.4-1ubuntu10.1.quantal.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1069570/+attachment/3631255/+files/isc-dhcp_4.2.4-1ubuntu10.1.quantal.debdiff

** Patch added: isc-dhcp_4.1.ESV-R4-0ubuntu5.8.precise.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1069570/+attachment/3631784/+files/isc-dhcp_4.1.ESV-R4-0ubuntu5.8.precise.debdiff

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

Title:
  1 MAC Address, two IPs - DNS is out of sync with DHCP leases
  databases, I think...

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1069570/+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 1069570] Re: 1 MAC Address, two IPs - DNS is out of sync with DHCP leases databases, I think...

[Adam Stokes]

** Patch added: isc-dhcp_4.2.4-1ubuntu10.3.quantal.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1069570/+attachment/3631785/+files/isc-dhcp_4.2.4-1ubuntu10.3.quantal.debdiff

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

Title:
  1 MAC Address, two IPs - DNS is out of sync with DHCP leases
  databases, I think...

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1069570/+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 1101371] Re: [SRU] Integrate v1.3 of Windows Azure Linux Agent

[Adam Stokes]

** Patch added: walinuxagent_1.2-0ubuntu1~12.04.2.precise.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1101371/+attachment/3507905/+files/walinuxagent_1.2-0ubuntu1%7E12.04.2.precise.debdiff

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

Title:
  [SRU] Integrate v1.3 of Windows Azure Linux Agent

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1101371/+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 1101371] Re: [SRU] Integrate v1.3 of Windows Azure Linux Agent

[Adam Stokes]

** Patch added: walinuxagent_1.2-0ubuntu1~12.10.2.quantal.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1101371/+attachment/3507909/+files/walinuxagent_1.2-0ubuntu1%7E12.10.2.quantal.debdiff

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

Title:
  [SRU] Integrate v1.3 of Windows Azure Linux Agent

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1101371/+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 1101371] Re: [SRU] Integrate v1.3 of Windows Azure Linux Agent

[Adam Stokes]

** Patch added: walinuxagent_1.3-0ubuntu1.raring.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1101371/+attachment/3507912/+files/walinuxagent_1.3-0ubuntu1.raring.debdiff

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

Title:
  [SRU] Integrate v1.3 of Windows Azure Linux Agent

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1101371/+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