With bug 1440978 fixed locally I can now reproduce this.
ifup@eth0.service indeed takes some 3 minutes to time out, then the
getty finally appears. So let's run the ifup@ in the background; at
least in Ubuntu we didn't block on these under upstart either, and as I
wrote before the main reason for t
I attempted to fix this, but haven't gotten anywhere. I am seeing the
following errors:
Removing maas-region-controller (1.8.0~beta2+bzr3777-0ubuntu1) ...
* Stopping web server apache2
*
dbconf
*** This bug is a duplicate of bug 1044559 ***
https://bugs.launchpad.net/bugs/1044559
Note: If you try to purge the database, it actually fails in this case,
and the database is left intact.
See comments on bug #1044559.
** Also affects: maas
Importance: Undecided
Status: New
**
I just saw this one again. I found a relevant discussion here:
https://lists.alioth.debian.org/pipermail/dbconfig-common-
devel/2006-September/000627.html
Here's the relevant quote from Sean Finney (the maintainer of dbconfig-
common):
"""
i can reproduce your problem... looking in my postgres l
As for what creates the "Before=network.target" for networking.service
(aka /etc/init.d/networking): this is defined in /etc/insserv.conf.
> We should definitely not be blocking network.target indefinitely on
boot waiting for the results of /etc/init.d/networking.
Agreed. Conceptually we should k
** Summary changed:
- [SRU] Memory leaks in librados.py
+ [SRU] Memory leaks in rados.py
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
https://bugs.launchpad.net/bugs/1425164
Title:
[SRU] Memory leaks in rados.py
Public bug reported:
The syntax for puppetmaster-passenger needs to be updated for Apache
v2.4. The option "SSLCertificateChainFile" is deprecated and so is the
access control.
Order allow,deny
allow from all
needs to be replaced with "Require all granted".
The option "SSLCARevocationCheck" is
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nova (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1439280
I ran into the same issue recently and the solution turned out to do an
interation of
dovecot -n
and installing required packages until the above command ran without
complaints. In the end I had to install all of the following
ii dovecot-common 1:2.0.19-0ubuntu2.2
I tested juju 1.22.0 on vivid with streams and with quickstart (from
vivid). All is good. The client is good for working with all providers
and state servers on trusty and precise.
** Description changed:
We're now in a position to have 1.22.0 enter trusty-proposed and vivid-
proposed, but it
** Patch added: "lp1425164.utopic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1425164/+attachment/4368010/+files/lp1425164.utopic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
https://bugs.
** Patch added: "lp1425164.trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1425164/+attachment/4368009/+files/lp1425164.trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
https://bugs.
** Changed in: lxc (Ubuntu)
Importance: Undecided => High
--
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/1436723
Title:
Regression: Nested LXC is broken on Vivid
To manage notificat
** Changed in: init-system-helpers (Ubuntu)
Importance: Undecided => High
** Changed in: upstart (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to init-system-helpers in Ubuntu.
https://bugs.l
** Changed in: init-system-helpers (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to init-system-helpers in Ubuntu.
https://bugs.launchpad.net/bugs/1439988
Title:
package init-system-helpers 1.
** Description changed:
We're now in a position to have 1.22.0 enter trusty-proposed and vivid-
proposed, but it should not land in trusty-updates or vivid until
upstream passes QA on our proposed binaries, published the tools in
their stable simplestream and announces the release for gene
Public bug reported:
Error to install
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: apache2
Uname: Linux 3.15.5-031505-generic x86_64
Apache2ConfdDirListing: False
Apache2Modules:
Error: command ['/usr/sbin/apachectl', '-D DUMP_MODULES'] failed with exit
code 1: apache2: Syntax erro
I've tried 12.04 and have the same issue
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1315501
Title:
cloud-init does not use interfaces.d in trusty
To manage notifications abo
This guest XML would be expected to fail if the guest is running on a
host that is using qemu w/o kvm acceleration:
1
...as qemu does not support pinning when kvm isn't available. What's not
clear to me is why the Ubuntu version would be adding this line since it
sounds like master/kilo-3 is
** Also affects: maas
Importance: Undecided
Status: New
** Changed in: maas
Milestone: None => 1.8.0
** Changed in: maas
Importance: Undecided => Critical
** Changed in: maas
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
This might be the same fix required here: http://bazaar.launchpad.net
/~ubuntu-branches/ubuntu/vivid/percona-
server-5.6/vivid/view/head:/debian/patches/fix_mtr_ssl_cert.patch
Invalid in the development release since mysql-5.5 has been removed from
Vivid. Trusty could have the update when next nee
** Changed in: juju-core (Ubuntu)
Status: New => Fix Released
** Changed in: juju-core (Ubuntu Trusty)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpa
** Changed in: juju-core (Ubuntu)
Status: Confirmed => Fix Released
--
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/1316272
Title:
juju destroy-environment >=256 nodes fails
** Changed in: juju-core (Ubuntu)
Status: Triaged => Fix Released
--
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/1304407
Title:
juju bootstrap defaults to i386
To manage n
** Changed in: juju-core (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: juju-core (Ubuntu Trusty)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://b
** Changed in: juju-core (Ubuntu)
Status: Triaged => Fix Released
--
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/1318366
Title:
jujud on state server panic misses transacti
** Changed in: juju-core (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1250007
Title:
Bootstrapping azure causes memory to fill
** Changed in: juju-core (Ubuntu)
Status: Triaged => Fix Released
** Changed in: juju-core (Ubuntu Trusty)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.
This bug also prevents the mounting of NFS shares on boot, because
rpcbind is unable to start without the lo interface.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mailman in Ubuntu.
https://bugs.launchpad.net/bugs/1375821
Title:
** Branch linked: lp:~andreserl/maas/fix_lp1273197
** Branch linked: lp:~andreserl/maas/fix_lp1273197_1.7
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1273197
Title:
maas-cluster-co
This bug was fixed in the package libvirt - 1.2.12-0ubuntu9
---
libvirt (1.2.12-0ubuntu9) vivid; urgency=medium
* 9037-virt-aa-helper-add-unix-channels-esp-for-qemu-guest-.patch: Allow
libvirt domains to start when using qemu guest agent. (LP: #1393842)
-- Serge HallynMon,
** Description changed:
-
- SRU Justification:
- Impact: 'service haproxy stop' returns 4 if haproxy was already stopped.
- Development fix: check whether haproxy is running before trying to kill it
- Stable fix: same as development fix
- Te
** Description changed:
[Impact]
When using qemu/kvm/libvirt, if one suspends the VM using actual power
suspending code, the guest cannot resume using 'virsh dompmwakeup'.
[Test Case]
1) Create a KVM VM and install Trusty using libvirt (although qemu alone will
also exhibit thi
** Branch linked: lp:~ubuntudotcom1/maas/kill-all-the-configs-cluster
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1305907
Title:
boot: section in pserv.yaml is obsolete
To manage n
** Branch linked: lp:~ubuntudotcom1/maas/kill-all-the-configs-cluster
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1382196
Title:
Changing IP address for the region causes the cluste
Hope had been that the kernel's new support for cpuset.effective_cpus
would fix this. Removing a cpu from a parent cgroup or offlining a cpu
would remove it from effective_cpus, but not from cpuset.cpus.
Apparently that's not the case (kernel 3.19.0-10-generic was used for
the test in comment #27)
Public bug reported:
not able to modify beanstalkd config
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: beanstalkd 1.4.6-3
ProcVersionSignature: Ubuntu 3.2.0-76.111-generic-pae 3.2.66
Uname: Linux 3.2.0-76-generic-pae i686
ApportVersion: 2.0.1-0ubuntu17.8
Architecture: i386
Date: Fri
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: openvswitch (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in Ubuntu.
https://bugs.launchpad.net
Happened to me too when I updated my vivid system after a few weeks
again.
I still have upstart-bin (1.13.2-0ubuntu9) from before the transition to
upstart installed and tried to upgrade it.
init-system-helpers has a Replaces/Breaks on the transitioned upstart
package but not on the upstart-bin f
*** This bug is a duplicate of bug 1439988 ***
https://bugs.launchpad.net/bugs/1439988
** This bug has been marked a duplicate of bug 1439988
package init-system-helpers 1.22ubuntu4 failed to install/upgrade: trying to
overwrite '/lib/init/apparmor-profile-load', which is also in package
40 matches
Mail list logo
