** 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:
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:
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:
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
** 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
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
** 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:
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
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,
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
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 -
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
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,
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
** 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
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
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
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
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
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
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.
** 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
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,
** 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
-
)
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' r
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.
** 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
** 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
** 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
** 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.
** 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
** 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
** 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
** 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
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
** 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
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
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
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.
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
** 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
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
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
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
** 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
** 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
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
xnox, there is this bug: https://bugs.launchpad.net/juju-
core/+bug/1547665
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1545913
Title:
[FFe] juju-core 2.0
To manage
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.
We are using juju-core package name now so there is no need for this
packaging request :)
** Changed in: juju-core (Ubuntu)
Status: Fix Committed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
** Tags added: conjure
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1545913
Title:
[FFe] juju-core 2.0
To manage notifications about this bug go to:
** 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:
Also want to mention the openstack package as well.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1545913
Title:
[FFe] juju-core 2.0
To manage notifications about this bug go
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:
** Changed in: juju-core (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1560315
Title:
[needs packaging] juju2 beta is not in
** 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
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
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
** 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
** 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
** 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
** 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
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:
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:
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
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
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
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
Here is my config:
name: juju-078fe32d-4080-4f11-83e2-e579ead11df8-machine-0
profiles:
- default
- juju-myish
config:
user.juju-model-uuid: "true"
user.user-data: |
#cloud-config
output:
all: '| tee -a /var/log/cloud-init-output.log'
runcmd:
- set -xe
- install -D -m
Also wrt to Juju, if I do the following:
umount /sys/kernel/debug
mount -t debugfs none /sys/kernel/debug
And then reissue a juju bootstrap it will complete successfully :\ where
as before I was running into this error:
http://paste.ubuntu.com/15267564/
--
You received this bug notification
Are you able to `juju bootstrap` outside of the installer?
--
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:
** Tags added: cloud-installer
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid in Ubuntu.
https://bugs.launchpad.net/bugs/1547640
Title:
proxy tries ipv6 and gets 503 when no ipv6 routes
To manage notifications about this bug
** 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/1547640
Title:
proxy tries ipv6 and gets 503 when no ipv6 routes
To manage notifications about this bug go to:
I don't think you have MAAS configured properly, according to this
error:
[INFO: 02-16 23:04:23, openstack-install:227] Starting OpenStack Installer
v0.99.27
[INFO: 02-16 23:04:23, openstack-install:228] Start command:
['/usr/bin/openstack-install', '--openstack-release', 'liberty']
[INFO:
I'm also running into this issue when attempting to deploy a service
with juju + wily template, the template lxc container fails to stop so
cloning doesn't perform.
** Tags added: cloud-installer
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I've also tested manually and via our OpenStack installer and lxcbr0 is
assigned (10.0.4.1) and the network is able to reach out to the internet
as before.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
I've also tested manually and via our OpenStack installer and lxcbr0 is
assigned (10.0.4.1) and the network is able to reach out to the internet
as before.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: cloud-installer
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1509414
Title:
lxc postinst script checks available interfaces, can choose
To manage notifications about
** 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/1509414
Title:
lxc postinst script checks available interfaces, can choose
To manage notifications about this bug go
** Changed in: lxc (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509414
Title:
lxc postinst script checks available interfaces, can choose
To manage
** Changed in: lxc (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1509414
Title:
lxc postinst script checks available interfaces, can
** Description changed:
- The released wily image preinstalls lxc, which breaks the assumption
- that lxc's preinst packaging script makes:
+ [Problem]
+ The released wily image preinstalls lxc, which breaks the assumption that
lxc's preinst packaging script makes:
It inspects the network
** Description changed:
- The released wily image preinstalls lxc, which breaks the assumption
- that lxc's preinst packaging script makes:
+ [Problem]
+ The released wily image preinstalls lxc, which breaks the assumption that
lxc's preinst packaging script makes:
It inspects the network
** Description changed:
[Problem]
The released wily image preinstalls lxc, which breaks the assumption that
lxc's preinst packaging script makes:
It inspects the network to try to pick a 10.0.N.0 network that isn't
being used, with N starting at 3, so this appears to have picked
** Description changed:
[Problem]
The released wily image preinstalls lxc, which breaks the assumption that
lxc's preinst packaging script makes:
It inspects the network to try to pick a 10.0.N.0 network that isn't
being used, with N starting at 3, so this appears to have picked
I hit this too, I actually just had to run:
/usr/lib/x86_64-linux-gnu/lxc/lxc-net stop
And it seemed to put itself back into a state that systemd could work
with
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
I hit this too, I actually just had to run:
/usr/lib/x86_64-linux-gnu/lxc/lxc-net stop
And it seemed to put itself back into a state that systemd could work
with
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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.
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.
** 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
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
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
** 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
** 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
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
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
** 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
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:
Tested with python3-netaddr 0.7.10-1ubuntu1.1
code:
In[2]:from netaddr import IPSet
In [3]: ,.join(str(x) for x in list(IPSet(['10.0.4.0/24'])))
Out[3]:
Tested with python3-netaddr 0.7.10-1ubuntu1.1
code:
In[2]:from netaddr import IPSet
In [3]: ,.join(str(x) for x in list(IPSet(['10.0.4.0/24'])))
Out[3]:
1 - 100 of 679 matches
Mail list logo
