Is the unit test messing with the services on the host system? I hope
not.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1665160
Title:
MachineSuite.TestMachineWorkers
** Changed in: juju
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1665160
Title:
MachineSuite.TestMachineWorkers timed out waiting for
** Also affects: dbus (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- MachineSuite.TestMachineWorkers timed out waiting for workers zesty
+ MachineSuite.TestMachineWorkers timed out waiting for workers zesty because
dbus is in interactive mode
--
You received this
** Changed in: juju-ci-tools
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1635639
Title:
Seccomp error with
** Changed in: juju-ci-tools
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1635639
Title:
Seccomp error with
Current and new lxd containers are still broken. We see errors like this
lxc start xenial-manual-a xenial-manual-b xenial-manual-c
error: Error calling 'lxd forkstart xenial-manual-a /var/lib/lxd/containers
/var/log/lxd/xenial-manual-a/lxc.conf': err='exit status 1'
lxc 20161021035819.243
omp-hack.conf
# Advised to stgraber to add this file after seeing lxc-start fail with
# lxc-start 20161020121833.069 ERRORlxc_seccomp - seccomp.
lxc.seccomp=
** Affects: juju-ci-tools
Importance: Critical
Assignee: Curtis Hovey (sinzui)
Status: Fix Committed
** Affects:
This issue is now seen in xenial. This was not a problem a few hours
ago. We can see on xenial now. These versions
9.20160110ubuntu4 and 9.20160110ubuntu0.1 remove the py2 module, but do
not provide a py2 package to install.
--
You received this bug notification because you are a member of
** Summary changed:
- python2 cannot import lsb_release on yakkety
+ python2 cannot import lsb_release on yakkety and now xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lsb in Ubuntu.
Public bug reported:
python2 cannot import lsb_release on yakkety. `locate` shows "lsb-
release" installed several files, but
/usr/lib/python2.7/dist-packages/lsb_release.py
is missing from disk. This was seen on an aws instance provisioned using
the 20160526 daily image.
** Affects: lsb
** Changed in: juju-core
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1492088
Title:
juju bootstrap fails inside a wily container
This was also seen by the in Juju CI on the wily hosts that pull lxd/lxc
packages from the lxd ppa. We downgrades the wily machines to packages
from wily-updates to get lxc working again.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
This is the error
jenkins@wily-slave:~$ sudo lxc-start -n curtis -F
ln: failed to create symbolic link
‘/usr/lib/x86_64-linux-gnu/lxc/sys/fs/cgroup/cpu/cpu,cpuacct’: Read-only file
system
lxc-start: conf.c: run_buffer: 347 Script exited with status 1
lxc-start: conf.c: lxc_setup: 3750 failed to
** Changed in: juju-core
Milestone: 1.23-beta1 => None
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1403955
Title:
DHCP's "Option interface-mtu 9000" is being
** Also affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** Changed in: juju-core
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
Juju CI confirms this is fixed:
http://reports.vapour.ws/releases/3016/job/local-deploy-wily-amd64/attempt/297
** Changed in: juju-core
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
** Changed in: juju-core
Milestone: 1.25-alpha1 = 1.25-beta1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1480310
Title:
systemctl link request failed for service
The duplicate bug confirms what we are seeing in CI
wily + 1.24.5: Failed to execute operation: Unit name
/etc/systemd/system/juju-clean-shutdown.service is not valid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd
We are still seeing this issue after getting this fix and rebooting the
machine:
jenkins@wily-slave:~$ apt-cache policy systemd
systemd:
Installed: 224-1ubuntu3
Candidate: 224-1ubuntu3
Version table:
*** 224-1ubuntu3 0
500 http://archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
This bug blocks bug 1481556
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1480310
Title:
dbus link request failed for service FOO: Unit name FOO is not valid.
Status in
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1480310
Title:
dbus link request failed for
** Changed in: systemd (Ubuntu)
Status: New = Confirmed
** Changed in: juju-core
Importance: Critical = High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Changed in: juju-core
Status: Fix Released = Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1403955
Title:
DHCP's Option interface-mtu 9000 is being
** Changed in: juju-core
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1403955
Title:
DHCP's Option interface-mtu 9000 is
** Changed in: juju-core
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1403955
Title:
DHCP's Option interface-mtu 9000 is being ignored on
From James's duplicate bug:
In our MAAS based openstack deployment, we provide MTU via DHCP to all
servers to enable jumbo frames.
This works fine until juju creates the bridge devices for LXC or KVM
containers, at which point we reliably lose the MTU 9000 setting on the
bridge, resulting in all
** Changed in: juju-core
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1355813
Title:
Interface MTU management across MAAS/juju
** Changed in: juju-core
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1402005
Title:
agent-state-info: 'error executing lxc-start: command
** Tags added: lxc network
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
lxc*1.0.3 looks odd. That is one version I don't expect to see.
trusty has 1.0.6 which is what I think the host is and should be using.
a precise host has 1.0.4
found in the cloud tools archive
http://ubuntu-cloud.archive.canonical.com/ubuntu/pool/main/l/lxc/
juju stable ppa provides
The host machine is trusty and was missing updated. We have updated the
lxc and other packages. We will watch the processes to see if the issue
is resolved or still exists.
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = High
** Tags
** Tags added: cts-cloud-review
** Tags added: add-unit
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = Medium
** Tags added: placement
** Tags added: network
** Changed in: juju-core
Milestone: None = 1.22
** Changed in:
** Changed in: juju-core
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1307215
Title:
destroy-environment fails to clear lxc containers
** Changed in: juju-core
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1355813
Title:
LXC containers reset bridge MTU on start/restart
** Tags added: ubuntu-engineering
** Changed in: juju-core
Importance: Medium = High
** Changed in: juju-core
Milestone: None = next-stable
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
** Changed in: juju-core
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1307215
Title:
destroy-environment fails to clear lxc containers
Status
36 matches
Mail list logo
