[Bug 1780334] Re: kubernetes - new ubuntu package

[Adam Stokes]

** Changed in: ubuntu
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780334

Title:
  kubernetes - new ubuntu package

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1771034] Re: fails to find bridge and storage pool when installing locally

[Adam Stokes]

You wan to run `lxd.migrate` first, https://docs.conjure-up.io/devel/en
/#users-of-lxd

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771034

Title:
  fails to find bridge and storage pool when installing locally

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1780334] Re: kubernetes - new ubuntu package

[Adam Stokes]

This got rejected originally, but it sounds like we're ok uploading the
package in its current state?

If so, do I need to reupload?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780334

Title:
  kubernetes - new ubuntu package

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1780334] Re: kubernetes - new ubuntu package

[Adam Stokes]

Thanks Steve, was a little rusty. I've made changes and did a new
upload.

** Changed in: ubuntu
   Status: Incomplete => New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780334

Title:
  kubernetes - new ubuntu package

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1771034] Re: fails to find bridge and storage pool when installing locally

[Adam Stokes]

** Changed in: conjure-up (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771034

Title:
  fails to find bridge and storage pool when installing locally

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1780334] [NEW] kubernetes - new ubuntu package

[Adam Stokes]

Public bug reported:

This is a new packaging request for package 'kubernetes'. It is
essentially a meta package which provides a user with a text based
selection menu for installing Canonical Distribution of Kubernetes or
microk8s via conjure-up snap.

The kubernetes package coming from Debian has been blocked to make way
for this Ubuntu specific kubernetes package.

PPA: https://code.launchpad.net/~adam-stokes/+archive/ubuntu/gangstar

** Affects: ubuntu
 Importance: Undecided
 Assignee: Adam Stokes (adam-stokes)
 Status: In Progress

** Changed in: ubuntu
   Status: New => In Progress

** Changed in: ubuntu
 Assignee: (unassigned) => Adam Stokes (adam-stokes)

** Description changed:

  This is a new packaging request for package 'kubernetes'. It is
  essentially a meta package which provides a user with a text based
  selection menu for installing Canonical Distribution of Kubernetes or
  microk8s via conjure-up snap.
+ 
+ PPA: https://code.launchpad.net/~adam-stokes/+archive/ubuntu/gangstar

** Description changed:

  This is a new packaging request for package 'kubernetes'. It is
  essentially a meta package which provides a user with a text based
  selection menu for installing Canonical Distribution of Kubernetes or
  microk8s via conjure-up snap.
  
+ The kubernetes package coming from Debian has been blocked to make way
+ for this Ubuntu specific kubernetes package.
+ 
  PPA: https://code.launchpad.net/~adam-stokes/+archive/ubuntu/gangstar

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780334

Title:
  kubernetes - new ubuntu package

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1712431] Re: sphere controller stores OVA files locally

[Adam Stokes]

** Tags added: conjure

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1712431

Title:
  sphere controller stores OVA files locally

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-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
Bugs, which is subscribed to 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-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-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
Bugs, which is subscribed to 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-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-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
Bugs, which is subscribed to 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-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1282837] Re: FFe: new package cloud-install

[Adam Stokes]

An updated tarball can be found here:

https://launchpad.net/cloud-installer/trunk/v0.14/+download/cloud-
installer_0.14%2Bbzr301.orig.tar.gz

The previous checklist still applies

Thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1282837

Title:
  FFe: new package cloud-install

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1311274] [NEW] Include sosreport into ubuntu-seeds/cloud-image

[Adam Stokes]

Public bug reported:

Would like to have sosreport included in future builds of the cloud-
images.

[Impact]
It is included by default in the supported seed for Trusty.

[Regression Potential]
None since this is just adding a package to the seed metadata

[Other info]
Having this available in the cloud images gives users the ability to quickly 
analyze and troubleshoot their deployments as sosreport contains plugins for 
various cloud technologies.

Including but not limited to:

Openstack-*
juju
maas

** Affects: ubuntu
 Importance: Undecided
 Status: New

** Branch linked: lp:~adam-stokes/ubuntu-seeds/ubuntu.trusty.sosreport

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311274

Title:
  Include sosreport into ubuntu-seeds/cloud-image

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576411] Re: UTF-8 is not very well supported inside snaps

[Adam Stokes]

I had to workaround this issue as well for conjure-up by exporting
LC_ALL=C.UTF-8 (https://github.com/conjure-up/conjure-
up/tree/master/snapcraft).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576411

Title:
  UTF-8 is not very well supported inside snaps

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1656580] [NEW] snapd on trusty fails to install snap with error loading shared library

[Adam Stokes]

Public bug reported:

When attempting to snap install from the proposed package in Trusty I
hit this error:

Jan 14 20:27:23 darthbawlz snap[1796]: /usr/lib/snapd/snap-confine:
error while loading shared libraries: libapparmor.so.1: failed to map
segment from shared object: Permission denied

The snap is a classic snap and can be tested with:

snap install conjure-up --classic --edge

This also happens on non classic snaps as well:

ubuntu@darthbawlz:~$ sudo snap install htop
htop 2.0.2 from 'maxiberta' installed
ubuntu@darthbawlz:~$ htop
/usr/lib/snapd/snap-confine: error while loading shared libraries: 
libapparmor.so.1: failed to map segment from shared object: Permission denied

Versions:

ubuntu@darthbawlz:~$ cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Ubuntu 14.04.5 LTS"

snapd 2.21~14.04
Kernel: 3.13.0-107-generic
systemd 204

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

** Affects: snapd (Ubuntu Trusty)
 Importance: Undecided
 Status: New


** Tags: conjure-up

** Tags added: conjure-up

** Description changed:

  When attempting to snap install from the proposed package in Trusty I
  hit this error:
  
  Jan 14 20:27:23 darthbawlz snap[1796]: /usr/lib/snapd/snap-confine:
  error while loading shared libraries: libapparmor.so.1: failed to map
  segment from shared object: Permission denied
  
  The snap is a classic snap and can be tested with:
  
  snap install conjure-up --classic --edge
  
  This also happens on non classic snaps as well:
  
  ubuntu@darthbawlz:~$ sudo snap install htop
  htop 2.0.2 from 'maxiberta' installed
  ubuntu@darthbawlz:~$ htop
  /usr/lib/snapd/snap-confine: error while loading shared libraries: 
libapparmor.so.1: failed to map segment from shared object: Permission denied
+ 
+ Versions:
+ 
+ ubuntu@darthbawlz:~$ cat /etc/lsb-release 
+ DISTRIB_ID=Ubuntu
+ DISTRIB_RELEASE=14.04
+ DISTRIB_CODENAME=trusty
+ DISTRIB_DESCRIPTION="Ubuntu 14.04.5 LTS"
+ 
+ snapd 2.21~14.04
+ Kernel: 3.13.0-107-generic
+ systemd 204

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656580

Title:
  snapd on trusty fails to install snap with error loading shared
  library

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1656580] Re: snapd on trusty fails to install snap with error loading shared library

[Adam Stokes]

During my tests I upgraded to snapd 14.04.2 and the libapparmor error
was not shown and I was able to do a:

$ snap install htop

and can access /snap/bin/htop

I am having another issue with 14.04.2 where conjure-up systemd service
is failing to start

Ill file another bug for that though

ubuntu@darthbawlz:~$ sudo snap install conjure-up --classic --edge
error: cannot perform the following tasks:
- Start snap "conjure-up" (32) services ([start snap.conjure-up.bridge.service] 
failed with exit status 1: Job for snap.conjure-up.bridge.service failed. See 
'systemctl status snap.conjure-up.bridge.service' and 'journalctl -xn' for 
details.
)


** Changed in: snapd (Ubuntu)
   Status: New => Incomplete

** Changed in: snapd (Ubuntu Trusty)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656580

Title:
  snapd on trusty fails to install snap with error loading shared
  library

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1656580] Re: snapd on trusty fails to install snap with error loading shared library

[Adam Stokes]

Marking incomplete as I can longer reproduce with snapd 2.21~14.04.2
package

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656580

Title:
  snapd on trusty fails to install snap with error loading shared
  library

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1657152] [NEW] snapd 2.21 on 14.04 does not install systemd file properly

[Adam Stokes]

Public bug reported:

You can reproduce by running the following on Trusty with snapd 2.21

sudo snap install conjure-up --edge --classic

Will result in this error:

ubuntu@darthbawlz:~$ sudo snap install conjure-up --classic --edge
error: cannot perform the following tasks:
- Start snap "conjure-up" (32) services ([start snap.conjure-up.bridge.service] 
failed with exit status 1: Job for snap.conjure-up.bridge.service failed. See 
'systemctl status snap.conjure-up.bridge.service' and 'journalctl -xn' for 
details.
)

That systemd file never seems to get installed. My snapcraft.yaml can be
seen here:

https://github.com/conjure-up/conjure-up/blob/master/snapcraft.yaml

This only happens on 14.04.

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

** Affects: snapd (Ubuntu Trusty)
 Importance: Undecided
 Status: New

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1657152

Title:
  snapd 2.21 on 14.04 does not install systemd file properly

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1655369] Re: cannot use the platform plug with a snap in 'classic' confinement

[Adam Stokes]

Seeing the same issue, this is the branch im working from:

https://github.com/conjure-up/conjure-up/tree/snapcraft-
updates/snapcraft

It could be I'm just doing something wrong so any advice is much
appreciated

** Changed in: snapd (Ubuntu)
   Status: Incomplete => New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655369

Title:
  cannot use the platform plug with a snap in 'classic' confinement

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1706733] [NEW] remove openstack package in artful

[Adam Stokes]

Public bug reported:

This package is no longer required as conjure-up packages all spell
requirements in it's snap packaging.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706733

Title:
  remove openstack package in artful

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1706732] [NEW] remove bigdata from artful

[Adam Stokes]

Public bug reported:

This package is no longer required by conjure-up as our spells are now
maintained inside the conjure-up snap itself.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706732

Title:
  remove bigdata from artful

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1706734] [NEW] remove conjure-up from artful

[Adam Stokes]

Public bug reported:

conjure-up is now releasing as a snap as the primary means of
consumption. Please remove this package from the archive.

rdepends also being asked for removal:

bigdata - https://bugs.launchpad.net/ubuntu/+source/bigdata/+bug/1706732
openstack - https://bugs.launchpad.net/ubuntu/+source/openstack/+bug/1706733

** Affects: conjure-up (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706734

Title:
  remove conjure-up from artful

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1706767] [NEW] please remove charm-tools from artful

[Adam Stokes]

Public bug reported:

charm-tools is now releasing as a snap as the primary means of
consumption. Please remove this package from the archive.

** Affects: charm-tools (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706767

Title:
  please remove charm-tools from artful

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1706766] [NEW] remove charm from artful

[Adam Stokes]

Public bug reported:

charm is now releasing as a snap as the primary means of consumption.
Please remove this package from the archive.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706766

Title:
  remove charm from artful

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1669507] Re: Remove juju-core from artful

[Adam Stokes]

Bugs for addressing the rdepends:

charm - https://bugs.launchpad.net/ubuntu/+source/charm/+bug/1706766
charm-tools - https://bugs.launchpad.net/ubuntu/+source/charm-tools/+bug/1706767
conjure-up - https://bugs.launchpad.net/ubuntu/+source/conjure-up/+bug/1706734

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1669507

Title:
  Remove juju-core from artful

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1677417] Re: /etc/ld.so.conf.d/conjure-up.conf breaks apt on host system

[Adam Stokes]

** Changed in: conjure-up (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1677417

Title:
  /etc/ld.so.conf.d/conjure-up.conf breaks apt on host system

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1687126] Re: sosreport does not collect /sys/fs/pstore contents

[Adam Stokes]

Also adding reference to https://github.com/sosreport/sos/pull/1008

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1687126

Title:
  sosreport does not collect /sys/fs/pstore contents

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1581645] Re: [SRU] Juju 2.0 beta7 for Xenial

[Adam Stokes]

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581645

Title:
  [SRU] Juju 2.0 beta7 for Xenial

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1581645] Re: [SRU] Juju 2.0 beta7 for Xenial

[Adam Stokes]

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581645

Title:
  [SRU] Juju 2.0 beta7 for Xenial

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576412] Re: package does not use released charms

[Adam Stokes]

Tested and made sure OpenStack is now coming up using the latest
released charms from the charmstore.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576412

Title:
  package does not use released charms

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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 
usr/

[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 
src/github.com/chai2010/gettext-go/gettext/local.go

[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
Bugs, which is subscribed to 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-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-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
Bugs, which is subscribed to 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-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-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
Bugs, which is subscribed to 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-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1561037] [NEW] [needs-packaging] conjure

[Adam Stokes]

Public bug reported:

This is the application runtime for providing access to apt installable
juju bundles.

URL: https://github.com/Ubuntu-Solutions-Engineering/conjure
License: MIT
Notes: This was blocked waiting on juju2 reaching the Xenial archives.

The PPA containing the package can be found here:

ppa:conjure/ppa

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: needs-packaging

** Tags added: needs-packaging

** Description changed:

  This is the application runtime for providing access to apt installable
  juju bundles.
  
  URL: https://github.com/Ubuntu-Solutions-Engineering/conjure
  License: MIT
  Notes: This was blocked waiting on juju2 reaching the Xenial archives.
+ 
+ The PPA containing the package can be found here:
+ 
+ ppa:conjure/ppa

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1561037

Title:
  [needs-packaging] conjure

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1561043] [NEW] [needs-packaging] bigdata

[Adam Stokes]

Public bug reported:

This is the application wrapper around conjure to provide apt juju
bundle installation for various big data solutions.

URL: https://github.com/Ubuntu-Solutions-Engineering/bigdata-deb
License: MIT
Notes: This was blocked waiting on juju2 reaching the Xenial archives.

The PPA containing the package can be found here:

ppa:conjure/ppa

** Affects: ubuntu
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1561043

Title:
  [needs-packaging] bigdata

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-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
Bugs, which is subscribed to 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-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1306315] Re: juju-mongodb process hangs around after package removal

[Adam Stokes]

I honestly haven't ran into this for a long time. I think we can close
this out.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1306315

Title:
  juju-mongodb process hangs around after package removal

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1575377] [NEW] blank return strings from processing scripts cause json parse error

[Adam Stokes]

Public bug reported:

During parsing of results from post processing scripts that return a
JSON dictionary and error would occur if that JSON response was not
properly formatted or an empty string.

** Affects: conjure-up (Ubuntu)
 Importance: Critical
 Assignee: Adam Stokes (adam-stokes)
 Status: In Progress

** Changed in: conjure-up (Ubuntu)
 Assignee: (unassigned) => Adam Stokes (adam-stokes)

** Changed in: conjure-up (Ubuntu)
   Importance: Undecided => Critical

** Changed in: conjure-up (Ubuntu)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575377

Title:
  blank return strings from processing scripts cause json parse error

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1573176] Re: [SRU] Juju 2.0 for Xenial

[Adam Stokes]

Also tested on a separate system utilizing conjure-up and juju beta6 and
saw no agent lost errors for bug 1572237

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573176

Title:
  [SRU] Juju 2.0 for Xenial

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1575377] Re: blank return strings from processing scripts cause json parse error

[Adam Stokes]

** Description changed:

- During parsing of results from post processing scripts that return a
- JSON dictionary and error would occur if that JSON response was not
- properly formatted or an empty string.
+ [Impact]
+ This will break any post processing script attempting to retry a invalid JSON 
string.
+ 
+ [Test Case]
+ Simply running `conjure-up openstack` through to the end will show this error.
+ 
+ [Regression Potential]
+ This should be minimal as we add additional exception handling to gracefully 
deal with these errors.
+ 
+ [Additional Info]
+ During parsing of results from post processing scripts that return a JSON 
dictionary and error would occur if that JSON response was not properly 
formatted or an empty string.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575377

Title:
  blank return strings from processing scripts cause json parse error

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1567040] Re: openstack-install fails v0.99.27

[Adam Stokes]

Please try with conjure-up and open a separate bug if problem persists

Thanks!

** Changed in: openstack (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567040

Title:
  openstack-install fails v0.99.27

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1546484] Re: openstack-install fails

[Adam Stokes]

You'll want to make sure you've:

sudo openstack-install -u
rm -rf ~/.cloud-install


Then re-run the installer, please note that you do not have to define 
--openstack-release as Autopilot is already configured to use the appropriate 
version.

Also note on 16.04 you'll want to use the new installer via `conjure-up
openstack` (apt install conjure-up)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1546484

Title:
  openstack-install fails

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1575800] [NEW] post processing neutron fails to configure network

[Adam Stokes]

Public bug reported:

Once a deploy has completed using the OpenStack with Nova-LXD bundle
there are attempts made to configure neutron automatically for a more
turnkey experience. Problem is we do not want to mess with the existing
lxdbr0 for this so a new bridge will need to be defined and configured
to work with neutron.

The bug is currently a network is defined but not associated with any
bridge from the host system.

** Affects: openstack (Ubuntu)
 Importance: Critical
 Assignee: Adam Stokes (adam-stokes)
 Status: In Progress

** Changed in: openstack (Ubuntu)
   Status: New => In Progress

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575800

Title:
  post processing neutron fails to configure network

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1575906] [NEW] post processing fails to add ssh keypair

[Adam Stokes]

Public bug reported:

During post processing phase the ssh keypair is not properly imported
and at times an error is printed to the screen about unable to locate
any ssh keys to import.

** Affects: openstack (Ubuntu)
 Importance: Critical
 Assignee: Adam Stokes (adam-stokes)
 Status: In Progress

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

** Changed in: openstack (Ubuntu)
   Status: New => In Progress

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575906

Title:
  post processing fails to add ssh keypair

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1575377] Re: blank return strings from processing scripts cause json parse error

[Adam Stokes]

** Changed in: conjure-up (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575377

Title:
  blank return strings from processing scripts cause json parse error

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576412] [NEW] package does not use released charms

[Adam Stokes]

Public bug reported:

openstack package should use the released charms from the charmstore
rather than openstack-charmers-next

** Affects: openstack (Ubuntu)
 Importance: Critical
 Assignee: Adam Stokes (adam-stokes)
 Status: In Progress

** Changed in: openstack (Ubuntu)
   Status: New => In Progress

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576412

Title:
  package does not use released charms

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1575800] Re: post processing neutron fails to configure network

[Adam Stokes]

** Also affects: openstack (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Description changed:

- Once a deploy has completed using the OpenStack with Nova-LXD bundle
- there are attempts made to configure neutron automatically for a more
- turnkey experience. Problem is we do not want to mess with the existing
- lxdbr0 for this so a new bridge will need to be defined and configured
- to work with neutron.
+ [Impact]
+ Any user wishing to deploy a fully turnkey solution will fail to be able to 
access external networks.
  
- The bug is currently a network is defined but not associated with any
- bridge from the host system.
+ [Test Case]
+ A full deploy with 'conjure-up openstack', once deployed login to horizon and 
start an instance. Once sshing to that instance attempt to ping google.com or 
do any sort of dns lookup.
+ 
+ [Regression Potential]
+ This doesn't impact the overall deploying of OpenStack but does call a few 
'neutron' commands in order to define the internal and external networks.
+ 
+ [Additional Info]
+ Once a deploy has completed using the OpenStack with Nova-LXD bundle there 
are attempts made to configure neutron automatically for a more turnkey 
experience. Problem is we do not want to mess with the existing lxdbr0 for this 
so a new bridge will need to be defined and configured to work with neutron.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575800

Title:
  post processing neutron fails to configure network

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1575906] Re: post processing fails to add ssh keypair

[Adam Stokes]

** Description changed:

- During post processing phase the ssh keypair is not properly imported
- and at times an error is printed to the screen about unable to locate
- any ssh keys to import.
+ [Impact]
+ Users wishing to ssh into their instances will fail to do so without manually 
importing their ssh key.
+ 
+ [Test Case]
+ Deploy with 'conjure-up openstack', login to horizon, check the access and 
security tab/ssh key pairs and see that no keypair has been imported.
+ 
+ [Regression Potentional]
+ This checks for the existence of a key if not there, runs the relevant 
openstack command to import a newly generated key pair. Regression is minimal 
as nothing is overwritten.
+ 
+ [Additional Info]
+ During post processing phase the ssh keypair is not properly imported and at 
times an error is printed to the screen about unable to locate any ssh keys to 
import.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575906

Title:
  post processing fails to add ssh keypair

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576412] Re: package does not use released charms

[Adam Stokes]

** Description changed:

- openstack package should use the released charms from the charmstore
- rather than openstack-charmers-next
+ [Impact]
+ All users wanting to deploy a production grade OpenStack via Juju bundles.
+ 
+ [Test Case]
+ This basically uses the vetted 16.04 charms from charmstore so just running 
'conjure-up openstack' and seeing the services start and booting an instance is 
enough.
+ 
+ [Regression Potential]
+ This would would actually reduce regression risks as we were pulling from the 
charmers next branch where at any given time could break.
+ 
+ [Additional Info]
+ openstack package should use the released charms from the charmstore rather 
than openstack-charmers-next

** Also affects: openstack (Ubuntu Xenial)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576412

Title:
  package does not use released charms

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1575906] Re: post processing fails to add ssh keypair

[Adam Stokes]

** Also affects: openstack (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575906

Title:
  post processing fails to add ssh keypair

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576412] Re: package does not use released charms

[Adam Stokes]

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576412

Title:
  package does not use released charms

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1575800] Re: post processing neutron fails to configure network

[Adam Stokes]

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575800

Title:
  post processing neutron fails to configure network

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-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
Bugs, which is subscribed to 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-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-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
Bugs, which is subscribed to 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-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-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
Bugs, which is subscribed to 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-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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
Bugs, which is subscribed to 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-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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 upon

[Bug 1586131] [NEW] 'creds' keyerror when deploying openstack/bigdata

[Adam Stokes]

dist-packages/urwid/container.py", line 1128, in 
keypress
return self.body.keypress( (maxcol, remaining), key )
  File "/usr/share/conjure-up/conjure/ui/views/cloud.py", line 21, in keypress
return super().keypress(size, key)
  File "/usr/lib/python3/dist-packages/urwid/decoration.py", line 836, in 
keypress
return self._original_widget.keypress((maxcol,), key)
  File "/usr/lib/python3/dist-packages/urwid/container.py", line 1587, in 
keypress
key = self.focus.keypress(tsize, key)
  File "/usr/lib/python3/dist-packages/urwid/decoration.py", line 621, in 
keypress
return self._original_widget.keypress(maxvals, key)
  File "/usr/lib/python3/dist-packages/urwid/wimp.py", line 535, in keypress
self._emit('click')
  File "/usr/lib/python3/dist-packages/urwid/widget.py", line 463, in _emit
signals.emit_signal(self, name, self, *args)
  File "/usr/lib/python3/dist-packages/urwid/signals.py", line 264, in emit
result |= self._call_callback(callback, user_arg, user_args, args)
  File "/usr/lib/python3/dist-packages/urwid/signals.py", line 294, in 
_call_callback
return bool(callback(*args_to_pass))
  File "/usr/share/conjure-up/conjure/ui/views/cloud.py", line 72, in submit
self.cb(result.label, create_cloud=True)
  File "/usr/share/conjure-up/conjure/controllers/cloud.py", line 39, in finish
return self.app.controllers['newcloud'].render(cloud)
  File "/usr/share/conjure-up/conjure/controllers/newcloud.py", line 118, in 
render
creds,
UnboundLocalError: local variable 'creds' referenced before assignment
arosales@x230:~$ conjure-up --version
conjure-up 0.1.0
arosales@x230:~$ uname -a
Linux x230 4.4.0-22-generic #40-Ubuntu SMP Thu May 12 22:03:46 UTC 2016 x86_64 
x86_64 x86_64 GNU/Linux
arosales@x230:~$ cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04 LTS"
arosales@x230:~$

** Affects: conjure-up (Ubuntu)
 Importance: Critical
 Assignee: Adam Stokes (adam-stokes)
 Status: In Progress

** Affects: conjure-up (Ubuntu Xenial)
     Importance: Critical
 Assignee: Adam Stokes (adam-stokes)
 Status: New

** Changed in: conjure-up (Ubuntu)
   Status: New => In Progress

** Also affects: conjure-up (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: conjure-up (Ubuntu)
   Importance: Undecided => Critical

** Changed in: conjure-up (Ubuntu Xenial)
   Importance: Undecided => Critical

** Changed in: conjure-up (Ubuntu)
 Assignee: (unassigned) => Adam Stokes (adam-stokes)

** Changed in: conjure-up (Ubuntu Xenial)
 Assignee: (unassigned) => Adam Stokes (adam-stokes)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1586131

Title:
  'creds' keyerror when deploying openstack/bigdata

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1586131] Re: 'creds' keyerror when deploying openstack/bigdata

[Adam Stokes]

** Changed in: conjure-up (Ubuntu)
   Status: In Progress => Fix Released

** Description changed:

+ [Impact]
+ Any user using the latest Juju beta7 which changed the cloud listing from lxd 
to localhost
+ 
+ [Test]
  I did the following:
  
  apt install conjure-up #per instructions
- conjure-up bigdata 
+ conjure-up bigdata
  In the menu
  
  choose Apache Flume/Spark/Zeppelin
  choose local host
  get:
  
  arosales@x230:~$ conjure-up bigdata
  Exception in ev.run():
  Traceback (most recent call last):
-   File "/usr/share/conjure-up/ubuntui/ev.py", line 83, in run
- cls.loop.run()
-   File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 278, in run
- self._run()
-   File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 376, in _run
- self.event_loop.run()
-   File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 1328, in run
- raise 
self._exc_info[0](self._exc_info[1]).with_traceback(self._exc_info[2])
-   File "/usr/lib/python3.5/asyncio/events.py", line 125, in _run
- self._callback(*self._args)
-   File "/usr/lib/python3/dist-packages/urwid/raw_display.py", line 393, in 

- event_loop, callback, self.get_available_raw_input())
-   File "/usr/lib/python3/dist-packages/urwid/raw_display.py", line 493, in 
parse_input
- callback(processed, processed_codes)
-   File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 403, in 
_update
- self.process_input(keys)
-   File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 503, in 
process_input
- k = self._topmost_widget.keypress(self.screen_size, k)
-   File "/usr/lib/python3/dist-packages/urwid/wimp.py", line 643, in keypress
- return self._current_widget.keypress(size, key)
-   File "/usr/lib/python3/dist-packages/urwid/container.py", line 1128, in 
keypress
- return self.body.keypress( (maxcol, remaining), key )
-   File "/usr/share/conjure-up/conjure/ui/views/cloud.py", line 21, in keypress
- return super().keypress(size, key)
-   File "/usr/lib/python3/dist-packages/urwid/decoration.py", line 836, in 
keypress
- return self._original_widget.keypress((maxcol,), key)
-   File "/usr/lib/python3/dist-packages/urwid/container.py", line 1587, in 
keypress
- key = self.focus.keypress(tsize, key)
-   File "/usr/lib/python3/dist-packages/urwid/decoration.py", line 621, in 
keypress
- return self._original_widget.keypress(maxvals, key)
-   File "/usr/lib/python3/dist-packages/urwid/wimp.py", line 535, in keypress
- self._emit('click')
-   File "/usr/lib/python3/dist-packages/urwid/widget.py", line 463, in _emit
- signals.emit_signal(self, name, self, *args)
-   File "/usr/lib/python3/dist-packages/urwid/signals.py", line 264, in emit
- result |= self._call_callback(callback, user_arg, user_args, args)
-   File "/usr/lib/python3/dist-packages/urwid/signals.py", line 294, in 
_call_callback
- return bool(callback(*args_to_pass))
-   File "/usr/share/conjure-up/conjure/ui/views/cloud.py", line 72, in submit
- self.cb(result.label, create_cloud=True)
-   File "/usr/share/conjure-up/conjure/controllers/cloud.py", line 39, in 
finish
- return self.app.controllers['newcloud'].render(cloud)
-   File "/usr/share/conjure-up/conjure/controllers/newcloud.py", line 118, in 
render
- creds,
+   File "/usr/share/conjure-up/ubuntui/ev.py", line 83, in run
+ cls.loop.run()
+   File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 278, in run
+ self._run()
+   File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 376, in _run
+ self.event_loop.run()
+   File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 1328, in run
+ raise 
self._exc_info[0](self._exc_info[1]).with_traceback(self._exc_info[2])
+   File "/usr/lib/python3.5/asyncio/events.py", line 125, in _run
+ self._callback(*self._args)
+   File "/usr/lib/python3/dist-packages/urwid/raw_display.py", line 393, in 

+ event_loop, callback, self.get_available_raw_input())
+   File "/usr/lib/python3/dist-packages/urwid/raw_display.py", line 493, in 
parse_input
+ callback(processed, processed_codes)
+   File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 403, in 
_update
+ self.process_input(keys)
+   File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 503, in 
process_input
+ k = self._topmost_widget.keypress(self.screen_size, k)
+   File "/usr/lib/python3/dist-packages/urwid/wimp.py", line 643, in keypress
+ return self._current_widget.keypress(size, key)
+   File "/usr/lib/python3/dist-packages/urwid/container.py", line 1128, in 
keypress
+ return self.body.keypress( (maxcol, remaining), key )
+   File "/usr/share/conjure-up/conjure/ui/views/cloud.py", line 21, in keypress
+ return super().keypress(size, key)
+   File "/usr/lib/python3/dist-packages/urwid/decoration.py", line 836, in 
keypress
+ return self._original_widget.keypress((maxcol,), key)
+   File "/usr/lib/python3/dist-packages/u

[Bug 1575800] Re: post processing neutron fails to configure network

[Adam Stokes]

I've done several tests using proposed and have had it successfully
deploy openstack with neutron working and instances pingable out of the
box.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575800

Title:
  post processing neutron fails to configure network

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1575906] Re: post processing fails to add ssh keypair

[Adam Stokes]

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575906

Title:
  post processing fails to add ssh keypair

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 423252] Re: NSS using LDAP+SSL breaks setuid applications like su, sudo, apache2 suexec, and atd

[Adam Stokes]

re #108 (cdmiller)

Is this fix still a workable solution for you and have you run into any
issues not yet experienced on this bug?

Thanks

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/423252

Title:
  NSS using LDAP+SSL breaks setuid applications like su, sudo, apache2
  suexec, and atd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/423252/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1339842] Re: GlanceMirror item filters are hardcoded

[Adam Stokes]

** Tags added: cloud-installer

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

** Changed in: simplestreams (Ubuntu)
   Importance: Critical => High

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1339842

Title:
  GlanceMirror item filters are hardcoded

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1339842] Re: GlanceMirror item filters are hardcoded

[Adam Stokes]

** Description changed:

+ [Impact]
  The GlanceMirror class has a hard-coded filter for items to be
  downloaded.
  
  Anyone using it directly or via the script in
  tools/sstream-mirror-glance to load images into an openstack cloud
  will end up with a large number of images, at least one for each of
  the available release series, and only x86_64 or amd64.
  
  It is likely that users will want to be able to limit the images they
  download to just one release, and may want to be able to download
  images for other architectures, such as arm*.
  
  The attached diff simply exposes the existing filter mechanism as a
  config option, using the previous hardcoded values as defaults.
  
  This config option is used (currently it is just ignored by the
  published simplestreams code) in an charm that is released on the
  charm store for trusty, 'glance-simplestreams-sync'. Users of
  OpenStack on Trusty are likely to want the option to control image
  downloads via that charm.
  
  [Test Case]
  
  In an openstack cloud, with proper openstack env vars (OS_USERNAME,
  OS_PASSWORD, OS_REGION etc), run the sstream-mirror-glance tool to
  download images locally:
  
  from the source tree top directory,
  
  PYTHONPATH=. tools/sstream-mirror-glance --max=1 -v -v -v --output-dir \
  images/ --cloud-name test_cloud --content-id test_content \
  --keyring /usr/share/keyrings/ubuntu-cloudimage-keyring.gpg \
  http://cloud-images.ubuntu.com/releases/ streams/v1/index.json
  
  verify that it downloads many images. This may take a while.  If you
  like, you can just check that it will download an image for an old
  series like raring or quantal.
  
  Clean up after it by removing the images/ directory.
  
  Then with the update applied, from the source tree top dir:
  
  PYTHONPATH=. tools/sstream-mirror-glance --max=1 -v -v -v --output-dir \
  images/ --cloud-name test_cloud --content-id test_content \
  --keyring /usr/share/keyrings/ubuntu-cloudimage-keyring.gpg \
  --item-filter="release=trusty" --item-filter="arch=arm64" \
  http://cloud-images.ubuntu.com/releases/ streams/v1/index.json
  
  and verify that it downloads only one matching image, trusty on arm64.
  
  [Regression Potential]
  
  This has very limited regression potential, because anyone relying on
  the existing behavior will still get it because the previous behavior
  is retained via defaults.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1339842

Title:
  GlanceMirror item filters are hardcoded

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1339842] Re: GlanceMirror item filters are hardcoded

[Adam Stokes]

** Patch added: "simplestreams_0.1.0~bzr341-0ubuntu2.trusty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/simplestreams/+bug/1339842/+attachment/4154134/+files/simplestreams_0.1.0%7Ebzr341-0ubuntu2.trusty.debdiff

** Patch removed: "simplestreams-1339842.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/simplestreams/+bug/1339842/+attachment/4150733/+files/simplestreams-1339842.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1339842

Title:
  GlanceMirror item filters are hardcoded

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-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
Bugs, which is subscribed to 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-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1486296] Re: Unable to start VMs under a lxc container

[Adam Stokes]

Here is the bit of code we use to create a container with, it shells out
to lxc-create passing in a custom userdata file:

```
@classmethod
def create(cls, name, userdata):
""" creates a container from ubuntu-cloud template
"""
# NOTE: the -F template arg is a workaround. it flushes the lxc
# ubuntu template's image cache and forces a re-download. It
# should be removed after https://github.com/lxc/lxc/issues/381 is
# resolved.
flushflag = "-F"
if os.getenv("USE_LXC_IMAGE_CACHE"):
log.debug("USE_LXC_IMAGE_CACHE set, so not flushing in lxc-create")
flushflag = ""
out = utils.get_command_output(
'sudo -E lxc-create -t ubuntu-cloud '
'-n {name} -- {flushflag} '
'-u {userdatafilename}'.format(name=name,
   flushflag=flushflag,
   userdatafilename=userdata))
if out['status'] > 0:
raise Exception("Unable to create container: "
"{0}".format(out['output']))
return out['status']
```

We also setup a custom lxc config file:

```
def create_container_and_wait(self):
""" Creates container and waits for cloud-init to finish
"""
self.tasker.start_task("Creating Container",
   self.read_container_status)

Container.create(self.container_name, self.userdata)

with open(os.path.join(self.container_abspath, 'fstab'), 'w') as f:
f.write("{0} {1} none bind,create=dir\n".format(
self.config.cfg_path,
'home/ubuntu/.cloud-install'))
f.write("/var/cache/lxc var/cache/lxc none bind,create=dir\n")
# Detect additional charm plugins and make available to the
# container.
charm_plugin_dir = self.config.getopt('charm_plugin_dir')
if charm_plugin_dir \
   and self.config.cfg_path not in charm_plugin_dir:
plug_dir = os.path.abspath(
self.config.getopt('charm_plugin_dir'))
plug_base = os.path.basename(plug_dir)
f.write("{d} home/ubuntu/{m} "
"none bind,create=dir\n".format(d=plug_dir,
m=plug_base))

extra_mounts = os.getenv("EXTRA_BIND_DIRS", None)
if extra_mounts:
for d in extra_mounts.split(','):
mountpoint = os.path.basename(d)
f.write("{d} home/ubuntu/{m} "
"none bind,create=dir\n".format(d=d,
m=mountpoint))

# update container config
with open(os.path.join(self.container_abspath, 'config'), 'a') as f:
f.write("lxc.mount.auto = cgroup:mixed\n"
"lxc.start.auto = 1\n"
"lxc.start.delay = 5\n"
"lxc.mount = {}/fstab\n".format(self.container_abspath))
```

Here is the userdata.yaml file we output and pass into the container:

```
#cloud-config

write_files:
  - content: |
  #!/bin/sh
  mkdir -p /dev/net || true
  mknod /dev/kvm c 10 232
  mknod /dev/net/tun c 10 200
  exit 0
path: /etc/rc.local
permissions: '0755'
packages:
  - software-properties-common
groups:
  - libvirtd: [ubuntu]
  - sudo: [ubuntu]
apt_proxy: http://10.0.3.1:3142
apt_https_proxy: http://10.0.3.1:3142
apt_get_wrapper:
  command: eatmydata
  enabled: auto
apt_sources:
  - source: deb http://ppa.launchpad.net/juju/stable/ubuntu $RELEASE main
key: |
  -BEGIN PGP PUBLIC KEY BLOCK-
  Version: SKS 1.1.4
  Comment: Hostname: keyserver.ubuntu.com

  mI0ETDzUZwEEAK3pnEmDZFVTehdKEN6jWs5UBfiEuyqHOmeINREQVn2ue+3bvFb+pYnjaPoz
  CxLRDa4gitS8Wt/rtLvC/Gl+0UNXl71yVdQoPCOPTjfcc4WfPe5EaVNUqNZsEou31jRLvuq9
  D/047ZjUbEFjy/oMY5I/zBA5X0BjNc30Tlm9NoMRABEBAAG0FkxhdW5jaHBhZCBFbnNlbWJs
  ZSBQUEGItgQTAQIAIAUCTDzUZwIbAwYLCQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJEDdqKQ7I
  BosRT50EAJQVKoSFSxyIlx4fdH9vhftKwvvmZK6KHYHqVY8Hee3exU/wdPCH+nssG2s/9/oW
  ReHiRNgIhc+iIDr+OTh/9TNPoClybkvrlWBgqUh6CIUNXbJQMigZlly90gkaLtUMGfsfW2+1
  u9j+vBKs9toPKDN1ybKu61k4lCrxoDUo9QDp
  =4LP9
  -END PGP PUBLIC KEY BLOCK-
  
  - source: deb http://ppa.launchpad.net/cloud-installer/stable/ubuntu $RELEASE 
main
key: |
  -BEGIN PGP PUBLIC KEY BLOCK-
  Version: SKS 1.1.4
  Comment: Hostname: keyserver.ubuntu.com

  mI0EUwap0AEEAOcvGspxrV0/83Xa6grEAplHLuuvj3CrOH26XwSleu/wzzTmNqKDnZLWjBkA
  qdbfYzQ3T4aD2uWfMJ2doqemBmLZWKrkMInLcS2o3cqraFHJaZDAvJHg7wiDBYiuq0cCrj/m
  enC351p/DLQ+QuiHE1hgX6JV4nF527rCmGbWSSTRABEBAAG0KExhdW5jaHBhZCBQUEEgZm9y
  IFVidW50dSBDbG91ZCBJbnN0YWxsZXKIuAQTAQIAIgUCUwap0AIbAwYLCQgHAwIGFQgCCQoL
  BBYCAwECHgECF4AACgkQ3eaD+NL/Ce1RuQQApA4AaFl

[Bug 1486296] Re: Unable to start VMs under a lxc container

[Adam Stokes]

** Changed in: libvirt (Ubuntu Vivid)
   Importance: Undecided => High

** Changed in: libvirt (Ubuntu Wily)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1408833] Re: broken postinst test for uvtool-libvirt

[Adam Stokes]

Enki,

Looks like you just need the enablement kernel: See here for more
information:

https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes#LTS_Hardware_Enablement_Stack

You'll want to make sure you're on a 3.16-0-38.52 or higher

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1408833

Title:
  broken postinst test for uvtool-libvirt

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-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
Bugs, which is subscribed to 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-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1486296] Re: Unable to start VMs under a lxc container

[Adam Stokes]

I was able to start up VM's within the container without any issues now.

Thanks!

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1282837] [NEW] FFe: new package cloud-install

[Adam Stokes]

Public bug reported:

[Why]

 Ubuntu Cloud installer is a metal to cloud image that provides an extremely
 simple way to install, deploy and scale an openstack cloud on top of
 Ubuntu server. Initial configurations are available for single
 physical system deployments as well as multiple physical system
 deployments.

[Source]

bzr:
lp:cloud-installer

ppa:
ppa:cloud-installer/ppa

tarball:
https://launchpad.net/cloud-installer/trunk/v0.2/+download/cloud-install_0.2.orig.tar.gz

[Checklist]
Packaging review
MUST:
[Y] Package must meet Ubuntu versioning & Maintainer requirements
[Y] Package must match current Ubuntu (and Debian) packaging policies
[Y] Package must build, install, run, remove, and purge cleanly
SHOULD:
[N] Package should be lintian clean
   - made some overrides to dh_installinit as it was erroring on no 
/etc/init.d/cloud-install even though we only have an upstart file
[Y] Contents of debian/ should be sane
[Y] Changelog should close a "needs-packaging" bug
[Y] Package should follow 
http://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.html
Maintenance review
MUST:
[Y] Package must contain a watch file or get-orig-source rule
[N/A] If upstream is no more, the packager should consider adopting the 
upstream package somewhere
[N :(] Packages who implement get-orig-source for packages with watch files get 
extra points
[Y] Packaged version must not have any known security or critical bugs
SHOULD:
[Y] Packaging scripts should be readable and readily comprehensible
[Y] Upstream should be responsive, and maintain a bug tracker
[Y] Packaged version should be latest upstream
[Y] Package should not be native without an approved spec
Suitability review
MUST:
[Y] Package must meet copyright / licensing requirements
[Y] Non-native packages must have verifiable cryptographic path to upstream 
source
[Waiting] Package must be advocated by at least two members of ubuntu-dev (the 
packager may count as one)
SHOULD:
[Y] Package should work on a standard Ubuntu/Kubuntu/Xubuntu/etc. system
[Y] Package should provide hints to system services (app-install-data, menus, 
etc.) to ease installation and use
[Y] Package should provide Ubuntu-specific documentation for variances in 
behaviour from upstream
[Y] Package should provide a Homepage: header in debian/control

Thanks

** Affects: ubuntu
 Importance: High
 Status: New

** Affects: Ubuntu Trusty
 Importance: High
 Status: New

** Affects: Ubuntu U-series
 Importance: High
 Status: New

** Also affects: Ubuntu Trusty
   Importance: Undecided
   Status: New

** Also affects: Ubuntu U-series
   Importance: Undecided
   Status: New

** Changed in: Ubuntu Trusty
   Importance: Undecided => High

** Changed in: Ubuntu U-series
   Importance: Undecided => High

** Description changed:

  [Why]
  
-  Ubuntu Cloud installer is a metal to cloud image that provides an extremely
-  simple way to install, deploy and scale an openstack cloud on top of
-  Ubuntu server. Initial configurations are available for single
-  physical system deployments as well as multiple physical system
-  deployments.
+  Ubuntu Cloud installer is a metal to cloud image that provides an extremely
+  simple way to install, deploy and scale an openstack cloud on top of
+  Ubuntu server. Initial configurations are available for single
+  physical system deployments as well as multiple physical system
+  deployments.
  
  [Source]
  
- bzr: 
- lp:cloud-installer 
+ bzr:
+ lp:cloud-installer
+ 
+ ppa:
+ ppa:cloud-installer/ppa
  
  tarball:
  
https://launchpad.net/cloud-installer/trunk/v0.2/+download/cloud-install_0.2.orig.tar.gz
  
  [Checklist]
  Packaging review
  MUST:
  [Y] Package must meet Ubuntu versioning & Maintainer requirements
  [Y] Package must match current Ubuntu (and Debian) packaging policies
  [Y] Package must build, install, run, remove, and purge cleanly
  SHOULD:
  [N] Package should be lintian clean
-- made some overrides to dh_installinit as it was erroring on no 
/etc/init.d/cloud-install even though we only have an upstart file
+    - made some overrides to dh_installinit as it was erroring on no 
/etc/init.d/cloud-install even though we only have an upstart file
  [Y] Contents of debian/ should be sane
  [Y] Changelog should close a "needs-packaging" bug
  [Y] Package should follow 
http://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.html
  Maintenance review
  MUST:
  [Y] Package must contain a watch file or get-orig-source rule
  [N/A] If upstream is no more, the packager should consider adopting the 
upstream package somewhere
  [N :(] Packages who implement get-orig-source for packages with watch files 
get extra points
  [Y] Packaged version must not have any known security or critical bugs
  SHOULD:
  [Y] Packaging scripts should be readable and readily comprehensible
  [Y] Upstream should be responsive, and maintain a bug tracker
  [Y] Packaged version shou

[Bug 1375977] Re: cloud-installer hangs at initializing

[Adam Stokes]

This bug should be fixed with latest testing packages. Please re-open if
necessary.

** Changed in: cloud-installer (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1375977

Title:
  cloud-installer hangs at initializing

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1408833] Re: broken postinst test for uvtool-libvirt on utopic

[Adam Stokes]

The problem exists in kernel 3.16.0-30-generic on trusty as well. Can we
get this fix backported to trusty?

** Also affects: cloud-installer
   Importance: Undecided
   Status: New

** Changed in: cloud-installer
   Status: New => Confirmed

** Summary changed:

- broken postinst test for uvtool-libvirt on utopic
+ broken postinst test for uvtool-libvirt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1408833

Title:
  broken postinst test for uvtool-libvirt

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1356211] Re: cannot collect rotated syslog.1

[Adam Stokes]

Merged upstream

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1356211

Title:
  cannot collect rotated syslog.1

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1433761] Re: apt-key and add-apt-repository don't honor Acquire::http::Proxy

[Adam Stokes]

** Tags added: cloud-installer

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1433761

Title:
  apt-key and add-apt-repository don't honor Acquire::http::Proxy

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-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
Bugs, which is subscribed to 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-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1207123] Re: Key usage violation in certificate has been detected

[Adam Stokes]

Jonathan, are you able to test quantal as well?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1207123

Title:
  Key usage violation in certificate has been detected

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-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
Bugs, which is subscribed to 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-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-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.16

[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
Bugs, which is subscribed to 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-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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
Bugs, which is subscribed to 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-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-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
Bugs, which is subscribed to 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-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1157943] Re: apt-get update fails hash checks on https repositories when file size changes

[Adam Stokes]

Ping, need some movement/response to OP comments.

Thanks!
Adam

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1157943

Title:
  apt-get update fails hash checks on https repositories when file size
  changes

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1157943] Re: apt-get update fails hash checks on https repositories when file size changes

[Adam Stokes]

David, sorry that ping was meant for you to try and unblock this issue.

Thanks again
Adam

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1157943

Title:
  apt-get update fails hash checks on https repositories when file size
  changes

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1247299] Re: apparmor blocks cgroup-lite from mounting

[Adam Stokes]

as asked on irc here is my log output from `juju deploy wordpress`
running on Saucy with version 1.16.2-saucy-amd64

environments.yaml

  ## https://juju.ubuntu.com/docs/config-local.html
  local:
type: local
admin-secret: 3303a7c433559ea535350fd1e6ac7f22
# Override the directory that is used for the storage files and database.
# The default location is $JUJU_HOME/.
# $JUJU_HOME defaults to ~/.juju
root-dir: /opt/juju
# Override the storage port if you have multiple local providers, or if the
# default port is used by another program.
# storage-port: 8040
# Override the shared storage port if you have multiple local providers, or 
if the
# default port is used by another program.
# shared-storage-port: 8041
# Override the network bridge if you have changed the default lxc bridge
# network-bridge: lxcbr0

juju status

~ » juju status 
adam@bigboi
environment: local
machines:
  "0":
agent-state: started
agent-version: 1.16.2.1
dns-name: 10.0.3.1
instance-id: localhost
series: saucy
  "1":
agent-state: started
agent-version: 1.16.2.1
instance-id: adam-local-machine-1
instance-state: missing
series: precise
services:
  wordpress:
charm: cs:precise/wordpress-20
exposed: false
relations:
  loadbalancer:
  - wordpress
units:
  wordpress/0:
agent-state: error
agent-state-info: 'hook failed: "install"'
agent-version: 1.16.2.1
machine: "1"
public-address: 10.0.3.227


/opt/juju/log/machine-1.log

2013-11-04 00:43:45 INFO juju machine.go:109 machine agent machine-1 start
2013-11-04 00:43:45 DEBUG juju.agent agent.go:237 Reading agent config, format: 
format 1.16
2013-11-04 00:43:45 INFO juju runner.go:253 worker: start "api"
2013-11-04 00:43:45 INFO juju apiclient.go:111 state/api: dialing 
"wss://10.0.3.1:17070/"
2013-11-04 00:43:45 INFO juju apiclient.go:121 state/api: connection established
2013-11-04 00:43:45 INFO juju runner.go:253 worker: start "machiner"
2013-11-04 00:43:45 INFO juju runner.go:253 worker: start "upgrader"
2013-11-04 00:43:45 INFO juju runner.go:253 worker: start "logger"
2013-11-04 00:43:45 DEBUG juju.worker.logger logger.go:35 initial log config: 
"=DEBUG"
2013-11-04 00:43:45 DEBUG juju.worker.logger logger.go:60 logger setup
2013-11-04 00:43:45 INFO juju runner.go:253 worker: start "deployer"
2013-11-04 00:43:45 DEBUG juju.worker.logger logger.go:45 reconfiguring logging 
from "=DEBUG" to "=INFO"
2013-11-04 00:43:45 INFO juju.worker.deployer deployer.go:106 checking unit 
"wordpress/0"
2013-11-04 00:43:45 INFO juju.worker.deployer deployer.go:146 deploying unit 
"wordpress/0"
2013-11-04 00:43:45 INFO juju.worker.upgrader upgrader.go:134 desired tool 
version: 1.16.2.1
2013-11-04 00:43:45 INFO juju.worker.machiner machiner.go:52 "machine-1" started

/opt/juju/log/unit-wordpress-0.log

2013-11-04 00:43:45 DEBUG juju.agent agent.go:237 Reading agent config, format: 
format 1.16
2013-11-04 00:43:45 INFO juju.jujud unit.go:73 unit agent unit-wordpress-0 start
2013-11-04 00:43:45 INFO juju runner.go:253 worker: start "api"
2013-11-04 00:43:45 INFO juju apiclient.go:111 state/api: dialing 
"wss://10.0.3.1:17070/"
2013-11-04 00:43:45 INFO juju apiclient.go:121 state/api: connection established
2013-11-04 00:43:45 INFO juju runner.go:253 worker: start "upgrader"
2013-11-04 00:43:45 INFO juju runner.go:253 worker: start "logger"
2013-11-04 00:43:45 DEBUG juju.worker.logger logger.go:35 initial log config: 
"=DEBUG"
2013-11-04 00:43:45 INFO juju runner.go:253 worker: start "uniter"
2013-11-04 00:43:45 DEBUG juju.worker.logger logger.go:60 logger setup
2013-11-04 00:43:45 DEBUG juju.worker.logger logger.go:45 reconfiguring logging 
from "=DEBUG" to "=INFO"
2013-11-04 00:43:45 INFO juju.worker.uniter uniter.go:83 unit "wordpress/0" 
started
2013-11-04 00:43:45 INFO juju.worker.uniter modes.go:421 ModeInit starting
2013-11-04 00:43:45 INFO juju.worker.uniter modes.go:29 updating unit addresses
2013-11-04 00:43:45 INFO juju.worker.upgrader upgrader.go:134 desired tool 
version: 1.16.2.1
2013-11-04 00:43:45 INFO juju.worker.uniter modes.go:54 reconciling relation 
state
2013-11-04 00:43:45 INFO juju.worker.uniter modes.go:421 ModeContinue starting
2013-11-04 00:43:45 INFO juju.worker.uniter modes.go:67 loading uniter state
2013-11-04 00:43:45 INFO juju.worker.uniter modes.go:70 charm is not deployed
2013-11-04 00:43:45 INFO juju.worker.uniter modes.go:421 ModeInstalling 
cs:precise/wordpress-20 starting
2013-11-04 00:43:45 INFO juju.worker.uniter uniter.go:221 fetching charm 
"cs:precise/wordpress-20"
2013-11-04 00:43:45 INFO juju charm.go:61 worker/uniter/charm: downloading 
cs:precise/wordpress-20 from http://10.0.3.1:8040/cs_3a_precise_2f_wordpress-20
2013-11-04 00:43:45 INFO juju charm.go:76 worker/uniter/charm: download complete
2013-11-04

[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
Bugs, which is subscribed to 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-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-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
Bugs, which is subscribed to 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-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-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
Bugs, which is subscribed to 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-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-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
Bugs, which is subscribed to 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-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1121874] Re: MySQL launch fails silently if < 4MB of disk space is available

[Adam Stokes]

Thanks and will do. I haven't been able to build a successful mysql
package via sbuild with or without the patches so Ill go through the
process of getting it uploaded to a PPA and built that way.

Ill re-subscribe sponsors once I can get a reliable package built.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1121874

Title:
  MySQL launch fails silently if < 4MB of disk space is available

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-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
Bugs, which is subscribed to 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-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1121874] Re: MySQL launch fails silently if < 4MB of disk space is available

[Adam Stokes]

** Patch added: "mysql-5.5_5.5.32-0ubuntu0.13.04.2.raring.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1121874/+attachment/3769727/+files/mysql-5.5_5.5.32-0ubuntu0.13.04.2.raring.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1121874

Title:
  MySQL launch fails silently if < 4MB of disk space is available

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1121874] Re: MySQL launch fails silently if < 4MB of disk space is available

[Adam Stokes]

** Patch added: "mysql-5.5_5.5.32-0ubuntu3.saucy.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1121874/+attachment/3769726/+files/mysql-5.5_5.5.32-0ubuntu3.saucy.debdiff

** Patch removed: "mysql-5.5_5.5.32-0ubuntu0.13.04.1.raring.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1121874/+attachment/3769725/+files/mysql-5.5_5.5.32-0ubuntu0.13.04.1.raring.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1121874

Title:
  MySQL launch fails silently if < 4MB of disk space is available

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1121874] Re: MySQL launch fails silently if < 4MB of disk space is available

[Adam Stokes]

** Patch added: "mysql-5.5_5.5.32-0ubuntu0.13.04.1.raring.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1121874/+attachment/3769725/+files/mysql-5.5_5.5.32-0ubuntu0.13.04.1.raring.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1121874

Title:
  MySQL launch fails silently if < 4MB of disk space is available

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1121874] Re: MySQL launch fails silently if < 4MB of disk space is available

[Adam Stokes]

** Patch added: "mysql-5.5_5.5.32-0ubuntu0.12.10.2.quantal.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1121874/+attachment/3769724/+files/mysql-5.5_5.5.32-0ubuntu0.12.10.2.quantal.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1121874

Title:
  MySQL launch fails silently if < 4MB of disk space is available

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1121874] Re: MySQL launch fails silently if < 4MB of disk space is available

[Adam Stokes]

** Patch removed: "mysql-5.5_5.5.32-0ubuntu2.saucy.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1121874/+attachment/3756361/+files/mysql-5.5_5.5.32-0ubuntu2.saucy.debdiff

** Patch removed: "mysql-5.5_5.5.32-0ubuntu0.13.04.2.raring.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1121874/+attachment/3756360/+files/mysql-5.5_5.5.32-0ubuntu0.13.04.2.raring.debdiff

** Patch removed: "mysql-5.5_5.5.32-0ubuntu0.12.10.2.quantal.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1121874/+attachment/3756359/+files/mysql-5.5_5.5.32-0ubuntu0.12.10.2.quantal.debdiff

** Patch removed: "mysql-5.5_5.5.32-0ubuntu0.12.04.2.precise.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1121874/+attachment/3756341/+files/mysql-5.5_5.5.32-0ubuntu0.12.04.2.precise.debdiff

** Patch added: "mysql-5.5_5.5.32-0ubuntu0.12.04.2.precise.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1121874/+attachment/3769723/+files/mysql-5.5_5.5.32-0ubuntu0.12.04.2.precise.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1121874

Title:
  MySQL launch fails silently if < 4MB of disk space is available

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1121874] Re: MySQL launch fails silently if < 4MB of disk space is available

[Adam Stokes]

Updated with new diffs to include the mysqld_get_param routine

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1121874

Title:
  MySQL launch fails silently if < 4MB of disk space is available

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1121874] Re: MySQL launch fails silently if < 4MB of disk space is available

[Adam Stokes]

** Tags removed: verification-failed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1121874

Title:
  MySQL launch fails silently if < 4MB of disk space is available

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs