** Changed in: maas/1.5
Status: Fix Committed = Fix Released
** Changed in: maas
Status: Fix Committed = Fix Released
** Changed in: maas
Milestone: 14.10 = None
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas
** Changed in: maas/1.5
Milestone: None = 1.5.1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-django in Ubuntu.
https://bugs.launchpad.net/bugs/1311433
Title:
REGRESSION: AttributeError: 'functools.partial' object has
** Changed in: maas
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1306701
Title:
bootresources.yaml references daily builds for trusty
To
** Changed in: maas/1.5
Status: Fix Committed = Fix Released
** Changed in: maas
Status: Fix Committed = Fix Released
** Changed in: maas/1.4
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
This also affects the `gnome-keyring` package. The System76 imaging
system (Tribble) uses a tar-based approach similar to the MAAS fast-path
installer, and we've had to add a work-around for /usr/bin/gnome-
keyring-daemon on our desktop images:
$ getcap /usr/bin/gnome-keyring-daemon
** Changed in: maas
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1240972
Title:
[SRU] maas dhcp.conf template not adding ignore-client-uids
Public bug reported:
Affected release:
Description: Ubuntu 14.04 LTS
Release: 14.04
Affected packages:
python-swift:
Installed: 1.13.1-0ubuntu1
Candidate: 1.13.1-0ubuntu1
python-happybase:
Installed: 0.7-1build1
Candidate: 0.7-1build1
The swift-proxy service fails to start.
Contents of
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ntp (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1278359
Since this still appears to be an issue on Trusty (14.04) and the Debian
bugtracker notes that they're no longer tracking autofs in unstable,
what happens to this bug?
And is it still the case that autofs (now version 5 in Trusty's repo's)
doesn't use upstart? I'm going to try the solution
** 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/1316556
Title:
vmware: boot from image (create volume) is failing
To manage
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: php5 (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1308059
** Changed in: nova (Ubuntu)
Status: Confirmed = In Progress
--
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/1316556
Title:
vmware: boot from image (create volume) is failing
Public bug reported:
dnsmasq is spinning at 100% CPU. This also causes networking to fail.
Problem seems to be that it is calling recvmsg(STDIN_FILENO, ...) which
is totally invalid. See attached strace log.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: dnsmasq-base 2.70-1
** Summary changed:
- Upon upgrade, DNS resolution no longer works
+ Upon upgrade, DNS resolution no longer works; dnsmasq uses 100% CPU
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
*** This bug is a duplicate of bug 1314697 ***
https://bugs.launchpad.net/bugs/1314697
** This bug has been marked a duplicate of bug 1314697
Upon upgrade, DNS resolution no longer works; dnsmasq uses 100% CPU
--
You received this bug notification because you are a member of Ubuntu
Attached is a full strace from dnsmasq startup showing the problem.
** Attachment added: dnsmasq-strace.log
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1314697/+attachment/4107998/+files/dnsmasq-strace.log
** Summary changed:
- Upon upgrade, DNS resolution no longer works;
Updated description since problem is unrelated to upgrade - it just
occurs with the version of dnsmasq currently in utopic.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1314697
Public bug reported:
The error popped up during the automatic update of installed packages.
ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: openssh-server 1:6.2p2-6ubuntu0.4
ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
Uname: Linux 3.11.0-15-generic x86_64
ApportVersion:
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1317477
Title:
package openssh-server 1:6.2p2-6ubuntu0.4 failed to install/upgrade:
** Changed in: juju-core/1.18
Assignee: John A Meinel (jameinel) = Ian Booth (wallyworld)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-quickstart in Ubuntu.
https://bugs.launchpad.net/bugs/1306537
Title:
LXC local
Public bug reported:
virsh blockcommit hangs at 100% and nothing happens.
I only found the following discussion:
http://t358434.emulators-libvirt-user.emulatortalk.info/virsh-blockcommit-hangs-at-100-t358434.html
** Affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
--
gnome-keyring-daemon isn't really a problem because all official images
shipping it have installer hooks to restore the flag.
Setting the binary setuid would also be completely wrong as we never
want this to run as root, we just want it to have extra ipc locking
capabilities. My understanding is
I can confirm that it is fixed in proposed, too. When can we expect the
fix to be pushed to updates repository?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1310919
Title:
Public bug reported:
Puppet client daemon config file /etc/default/puppet is missing in puppet
from Ubuntu Saucy, Trusty and Utopic:
http://packages.ubuntu.com/trusty/all/puppet/filelist
Perhaps there are some other files missing, see content of working package from
Ubuntu Raring:
Public bug reported:
An ipropd-slave process running on Precise Pangolin will crash if a
principal is modified on the master with del_enctype:
ipropd-slave[20814]: replaying entry 196
ipropd-slave[20814]: heim_abort: Wouldn't log and replay key history:(mask
KADM5_TL_DATA)
It seems this was
** Description changed:
- The backport of drbd8-utils-8.4.3 has several issues when running in
- compat-8.3 mode as part of corosync/pacemaker clusters.
+ SRU Justification:
+ The backport of drbd8-utils-8.4.3 has several issues when running in
compat-8.3 mode as part of corosync/pacemaker
After doing a little more investigation, it looks like there are other
distributions that are having problems with vsftpd running on AWS EC2
instances.
It sounds like it may be related to a kernel bug that affect Xen
paravirtualized hosts.
http://www.gossamer-
** Tags added: paravirtualization xen
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vsftpd in Ubuntu.
https://bugs.launchpad.net/bugs/1313450
Title:
Unable to start vsftpd on Ubuntu 14.04 (Amazon/EC2) with default
When will this be backported to trusty? It is a quite relevant and
important fix for those using the new radeon vdpau acceleration for
XBMC. I don't think many people would expect the source of their tearing
to be in libsdl1.2 and find this fix on their own.
--
You received this bug notification
Public bug reported:
Current version in 14.04 Trusty is 0.98.1, ClamAV recommends 0.98.3:
ClamAV update process started at Thu May 8 09:38:12 2014
WARNING: Your ClamAV installation is OUTDATED!
WARNING: Local version: 0.98.1 Recommended version: 0.98.3
** Affects: clamav (Ubuntu)
Stéphane,
Gotcha, thanks for the feedback! So am I correct in thinking that the
--xattrs option is currently broken in tar on 14.04? If so, is there any
chance this could be fixed in an SRU?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1300476
Title:
Unable to setup BMC/UCS user on Cisco B200 M3
So yeah, my understanding is that --xattr is broken at the moment, we should
fix that as an SRU but we also have the problem that:
1) It's not set by default in either create or extract mode
2) Not all tar implementations we use support it
3) Not all version of gnu-tar we support have it
So
** Changed in: maas (Ubuntu)
Importance: Undecided = Critical
--
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/1300476
Title:
Unable to setup BMC/UCS user on Cisco B200 M3
To manage
Excerpts from Jason Gerard DeRose's message of 2014-05-08 16:45:23 UTC:
Stéphane,
Gotcha, thanks for the feedback! So am I correct in thinking that the
--xattrs option is currently broken in tar on 14.04? If so, is there any
chance this could be fixed in an SRU?
No, --xattrs works fine in
** Branch linked: lp:~ubuntu-branches/ubuntu/utopic/maas/utopic-proposed
--
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/1300476
Title:
Unable to setup BMC/UCS user on Cisco B200 M3
** Branch linked: lp:~ubuntu-branches/ubuntu/utopic/maas/utopic-proposed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to curtin in Ubuntu.
https://bugs.launchpad.net/bugs/1310076
Title:
lost connectivity to a node when using
** Branch linked: lp:~ubuntu-branches/ubuntu/utopic/maas/utopic-proposed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-django in Ubuntu.
https://bugs.launchpad.net/bugs/1311433
Title:
REGRESSION: AttributeError:
** Branch linked: lp:~ubuntu-branches/ubuntu/utopic/maas/utopic-proposed
--
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/1310082
Title:
d-i with precise+hwe-s stops at Architecture not
** Branch linked: lp:~ubuntu-branches/ubuntu/utopic/maas/utopic-proposed
--
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/1311151
Title:
MAAS imports Trusty's 'rc' images by default.
Public bug reported:
[Impact]
This new upstream bugfix release of MAAS includes bug fixes for several bugs
reports. This includes Hardware Enablement for the Cisco B Series.
- Hardware Enablement for Cisco B-Series. (LP: #1300476)
- Allow AMT power type to specify IP Address. (LP: #1308772)
This bug was fixed in the package maas - 1.5+bzr2267-0ubuntu1
---
maas (1.5+bzr2267-0ubuntu1) utopic; urgency=medium
* New upstream bugfix release. Fixes:
- Hardware Enablement for Cisco B-Series. (LP: #1300476)
- Allow AMT power type to specify IP Address. (LP: #1308772)
** Description changed:
+ [Test Case]
+ Without the Fix:
+ 1. Install MAAS
+ 2. Power on Cisco B Series Nodes to boot from MAAS.
+ 3. Nodes won't have Power Management set. MAAS won't be able to control.
- On MAAS 1.5+bzr1977-0ubuntu5 enlisting nodes fails to detect the BMC
- power type and
This bug was fixed in the package maas - 1.5+bzr2267-0ubuntu1
---
maas (1.5+bzr2267-0ubuntu1) utopic; urgency=medium
* New upstream bugfix release. Fixes:
- Hardware Enablement for Cisco B-Series. (LP: #1300476)
- Allow AMT power type to specify IP Address. (LP: #1308772)
This bug was fixed in the package maas - 1.5+bzr2267-0ubuntu1
---
maas (1.5+bzr2267-0ubuntu1) utopic; urgency=medium
* New upstream bugfix release. Fixes:
- Hardware Enablement for Cisco B-Series. (LP: #1300476)
- Allow AMT power type to specify IP Address. (LP: #1308772)
Public bug reported:
When a VM is created for a p4080-e500mc ; the VM can not be rebooted
or terminated.
The qemu-system-ppc process must be killed.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: qemu-system-ppc 2.0.0~rc1+dfsg-0ubuntu3.1
ProcVersionSignature: Ubuntu
This bug was fixed in the package maas - 1.5+bzr2267-0ubuntu1
---
maas (1.5+bzr2267-0ubuntu1) utopic; urgency=medium
* New upstream bugfix release. Fixes:
- Hardware Enablement for Cisco B-Series. (LP: #1300476)
- Allow AMT power type to specify IP Address. (LP: #1308772)
** Description changed:
+ [Test Case]
+ 1. Install MAAS
+ 2. Add a node.
+ 3. Select a Hardware Enablement Kernel. (Distro Series: Precise,
Architecture: amd64/hwe-s)
+ 4. Deploy will fail.
+
+ With the fix:
+ 4. Deploy will succeed
+
After setting up hwe-s for precise along with the doc
** Description changed:
+ [Test Case]
+ 1. Install MAAS
+ 2. Add a node.
+ 3. Select a Hardware Enablement Kernel. (Distro Series: Precise,
Architecture: amd64/hwe-s)
+ 4. Deploy will fail.
+
+ With the fix:
+ 4. Deploy will succeed
+
+
After setting up hwe-s for precise along with the doc
** Description changed:
+ [Test Case]
+ 1. Install MAAS
+ 2. maas-import-pxe-files Will import RC images and Release images.
+
+ With the fix:
+ 2. maas-import-pxe-files will import only Release images.
+
MAAS imports both the 'rc' and the 'release' images for Trusty by
default.
This
It is related to a kernel bug.
Don't know if you have the ability to upgrade kernels on EC2, but this
bug can be worked around by installing one of the latest Ubuntu Mainline
kernels.
You need at least: linux-image-3.15.0-031500rc2
Reference: http://www.deinon.com/wiki/doku.php?id=linux:ubuntu
Public bug reported:
Настраивается пакет samba4 (4.0.0+dfsg1-1ubuntu1) …
Unknown enumerated value 'cups' for 'printing'
ERROR(runtime): uncaught exception - Unable to load default file
File /usr/lib/python2.7/dist-packages/samba/netcmd/__init__.py, line 175,
in _run
return self.run(*args,
MAAS does not pull in ipmitool by default (it is a Suggests, due to
ipmitool being in universe). While I understand that we can't add a
strict dependency w/o including ipmitool in main, I do think it is an
issue that it can cause MAAS to silently fail to work. IMO, there should
minimally be some
Hello Stefan, or anyone else affected,
Accepted drbd8 into precise-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/drbd8/2:8.4.3-0ubuntu0.12.04.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Stefan, or anyone else affected,
Accepted drbd8 into precise-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/drbd8/2:8.4.3-0ubuntu0.12.04.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1311433
Title:
REGRESSION: AttributeError:
Public bug reported:
If the cgmanager crashes while the cgproxy is waiting for a reply from
the server, the proxy will hang indefinately.
Set a 2 second timeout for the reply.
** Affects: cgmanager (Ubuntu)
Importance: High
Status: Fix Released
** Affects: cgmanager (Ubuntu
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1308069
Title:
test_prepare_holds_startup_lock() fails
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1298784
Title:
Vulnerable to user-interface redressing (e.g.
Clint,
Ah, thanks for bringing up --xattrs-include=*, I didn't notice this
option!
I agree this is really a bug/misfeature in tar... if I use --xattrs both
when creating and unpacking a tarball, I expect it to just work.
--
You received this bug notification because you are a member of Ubuntu
Packaging the new release in Debian and then we'll get it out to all
Ubuntu releases.
** Also affects: clamav (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: clamav (Ubuntu Saucy)
Importance: Undecided
Status: New
** Also affects: clamav (Ubuntu Precise)
** Description changed:
When starting a privileged container with cgmanager, cgroups look like:
3:cpuset:/lxc/u5
2:name=systemd:/user/1000.user/c2.session
where all controllers other than name=systemd are correct. lxc needs
to set the new cgroup for name=systemd, and cgmanager
** Changed in: cgmanager (Ubuntu Utopic)
Status: Confirmed = Fix Released
** Changed in: cgmanager (Ubuntu Trusty)
Status: Fix Committed = Confirmed
** Description changed:
+ ===
+ Impact: unprivileged users cannot attach
** Description changed:
When starting a privileged container with cgmanager, cgroups look like:
3:cpuset:/lxc/u5
2:name=systemd:/user/1000.user/c2.session
where all controllers other than name=systemd are correct. lxc needs
to set the new cgroup for name=systemd, and cgmanager
+1 for trusty backport
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libsdl1.2 in Ubuntu.
https://bugs.launchpad.net/bugs/1280665
Title:
libsdl1.2 always uses backingstore which causes tearing in modern X
servers
To manage
Public bug reported:
I install Linux Mint 16 Petra ( on Toshiba Portege R200 )
Everything works fine just
when I close the lid of my laptop the problem starts:
The laptop hibernate, but can get out of that mode when the lid is open.
The screen remains black. I tried all buttons on the keyboard -
** Description changed:
- This seems to be a regression introduced in the latest security update
- which is causing the error
+ [Test case]
- AttributeError: 'functools.partial' object has no attribute
- '__module__'
+ Without the fix:
+ 1. Install MAAS
+ 2. Access the MAAS home page
Annoyingly, I still can't reproduce this on the systems I have
available. On a system where the problem occurs, can it be reproduced
when dnsmasq is started standalone with the same command-line
parameters? The idea situation would be to get the bug to show up in a
dnsmasq instance running under
Hi,
I have UbuntuStudio 14.04
Got errors on reinstall, purge, remove
I looked for a more specifc error. Got this. doing an install after the
remove failed...
Selecting previously unselected package clamav-freshclam.
Preparing to unpack .../clamav-freshclam_0.98.1+dfsg-4ubuntu1.1_amd64.deb ...
** Description changed:
- = Impact =
- A remote attacker could trick users into performing unintended actions within
the application.
+ [Test Case]
+ Without the fix:
+ 1. Install MAAS.
+ 2. Create web page on other domain that loads MAAS in an IFRAME.
+ 3. MAAS loads and is usable.
- =
** Description changed:
+ [Test Case]
+ No test case; the code that's being patched is only a test and does not
actually appear in the package.
+
+
+ [Description of the problem]
+
This happened when trying to land a documentation-only branch:
** Tags added: patch
--
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/1311433
Title:
REGRESSION: AttributeError: 'functools.partial' object has no
attribute '__module__'
To manage
Public bug reported:
1. perform a direct install to a new file by obtaining the network install
components from
http://ports.ubuntu.com/ubuntu-ports/dists/trusty/main/installer-powerpc/current/images/e500mc/netboot/
qemu-system-ppc -M ppce500 -nographic -kernel vmlinux \
-initrd
Thank you for your report.
This change was deliberate: http://anonscm.debian.org/gitweb/?p=pkg-
puppet/puppet.git;a=commit;h=911303eee71f64299714de9a92326e2ed098984d
Since this is not a bug in Ubuntu, I'm marking this bug as Invalid. If
you disagree, please explain why this is a bug, rather than
The verification of the Stable Release Update for apache2 has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
This bug was fixed in the package apache2 - 2.2.22-1ubuntu1.6
---
apache2 (2.2.22-1ubuntu1.6) precise; urgency=low
* debian/patches/sni.patch:
- apache2 doesn't compare SNI hostname against Host header
case-insensitively (lp: #1298273)
-- Ritesh Khadgaray
A bit of debugging shows that the culprit is blockdata_expand() which is
being called via blockdata_init(). The issue seems to be that
blockdata_expand() is passed a parameter of zero. That function then
mallocs zero bytes (successfully seemingly), the proceeds to overwrite
data before the
BTW - the problem is recreatable for me every time simply by spinning up
a utopic kvm instance.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1314697
Title:
DNS resolution no
Public bug reported:
Please sync ipvsadm 1:1.26-3 (main) from Debian unstable (main)
Explanation of the Ubuntu delta and why it can be dropped:
* Merge from Debian unstable (LP: #1077874). Remaining changes:
- debian/control:
+ Add Build-Depends on pkg-config.
+ Update
** Also affects: xen (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to xen in Ubuntu.
https://bugs.launchpad.net/bugs/1311870
Title:
pygrub on 12.04 don't start 14.04
To manage
I think I hit this on 1.18.1-0ubuntu1 on Trusty. Adding an LXC container
on the manual provider failed. It appears fixed in ppa:juju/stable in
1.18.2-0ubuntu1~14.04.1~juju1. Adding a Trusty task.
** Also affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
** Also affects:
** Tags added: cloud-installer
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1317680
Title:
can't juju add machine when multiple images with same arch/release
exist
To manage
Public bug reported:
Setup the following:
$ cat ~/.juju/environments.yaml
default: local
environments:
local:
type: local
container: kvm
Execute the following:
$ juju add-machine
You will see:
$ juju status
environment: local
machines:
0:
agent-state: started
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: juju-core (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
You have been subscribed to a public bug:
freenode #ubuntu-server pointed me to create the bug here. Not sure if
it belongs here or elsewhere.
Create a container like so:
$ sudo lxc-create -t ubuntu-cloud -n base -- -S ~/.ssh/id_rsa.pub -r trusty
Start it:
$ sudo lxc-start -d -n base
Attach
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: openssh (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
I think this bug is occurs on non-containerized VMs.
** Project changed: lxc = openssh (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1317592
Title:
cannot log into
This bug was fixed in the package ipvsadm - 1:1.26-3
---
ipvsadm (1:1.26-3) unstable; urgency=medium
* [8fe73cf] Move to quilt 3.0
* [9ae82d1] wrap-and-sort
* [d8b7ba7] Move to debhelper compat v9
* [450ce1d] Remove obsolete dpatch patches
* [86caa7e] Remove obsolete
Public bug reported:
If a user does 'cgm movepid all xxx $$', they likely want to be moved
into cgroup xxx for the name=systemd controller as well.
** Affects: cgmanager (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
** Summary changed:
- Unable to start vsftpd on Ubuntu 14.04 (Amazon/EC2) with default
configuration
+ Unable to start vsftpd on Ubuntu 14.04 (Amazon/EC2 or Xen) with default
configuration
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Changed in: cgmanager (Ubuntu)
Importance: Undecided = High
** Changed in: cgmanager (Ubuntu)
Status: New = Triaged
** Also affects: cgmanager (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: cgmanager (Ubuntu Trusty)
Importance: Undecided = High
**
Public bug reported:
In setup_proxy, if the proxy fails to connect to the server, it returns
success rather than returning an error code and exiting.
===
Impact: proxy may proceed even though it is not
Test case: Start cgmanager on a host; start
This bug was fixed in the package cgmanager - 0.26-0ubuntu2
---
cgmanager (0.26-0ubuntu2) utopic; urgency=low
* 0001-cgm-make-all-also-reference-name-systemd.patch: make cgm all
also act on the name=systemd container (LP: #1317687)
-- Serge Hallyn serge.hal...@ubuntu.com
** Changed in: juju-core/1.18
Assignee: Nate Finch (natefinch) = Ian Booth (wallyworld)
--
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
** Branch linked: lp:~wallyworld/juju-core/1.18-backport-1304407
--
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
Dann, there is some work happening this cycle that will better report
node lifecycle events to enable easier debugging of this sort of fault.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
Public bug reported:
with a precise server (openvpn 2.2.1-8ubuntu1.2) and trusty client
(2.3.2-7ubuntu3):
In the config, I had:
push route xx.xx.xx.xx 255.255.255.255 net_gateway
push route yy.yy.yy.yy 255.255.255.255 net_gateway
(and another route for the /21 containing both of the hosts
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: openvpn (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvpn in Ubuntu.
** Changed in: juju-core/1.18
Status: In Progress = 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/1304407
Title:
juju bootstrap defaults to i386
To manage
** Changed in: maas
Status: Triaged = Fix Committed
** Changed in: maas
Assignee: (unassigned) = Jeroen T. Vermeulen (jtv)
** Changed in: maas/1.5
Status: Triaged = Fix Committed
** Changed in: maas/1.5
Assignee: (unassigned) = Jeroen T. Vermeulen (jtv)
** Changed in:
1 - 100 of 121 matches
Mail list logo
