on (prefer-ipv6)
> that would cause backports to be used, but in normal deployments the
> version in 14.04 should be used.
I hit this by simply deploying the haproxy charm on trusty. Openstack
was not really involved in what I was testing. I then recognized the
pattern of the bug.
--
Davi
Confirmed broken again on a default trusty install on maas:
haproxy:
Installed: 1.5.4-1ubuntu2.1~ubuntu14.04.1
Candidate: 1.5.4-1ubuntu2.1~ubuntu14.04.1
Package pin: 1.5.4-1ubuntu2.1~ubuntu14.04.1
Version table:
*** 1.5.4-1ubuntu2.1~ubuntu14.04.1 500
100
** Tags added: kanban-cross-team
--
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/1302962
Title:
Syslog suggests problem with MAAS DHCP lease file creation
To manage notifications
I have installed haproxy as part of an openstack (icehouse/trusty)
installation using the trusty-proposed archive. We no longer see the
issue with the updated package:
Package version tested:
1.4.24-2ubuntu0.4
** Tags removed: verification-needed
** Tags added: verification-done
--
You
It's looking like this is caused by haproxy (1.4.24-2ubuntu0.3) trusty;
urgency=medium which landed in trusty-updates on 09-DEC-2015
** Also affects: haproxy (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server
** Tags removed: landscape-release-29
--
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/1477225
Title:
ceph-radosgw restart fails
To manage notifications about this bug go to:
** Tags added: kanban-cross-team
--
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/1477225
Title:
ceph-radosgw restart fails
To manage notifications about this bug go to:
** Tags removed: landscape-release-29
** Tags added: kanban
** Also affects: landscape/cisco-odl
Importance: Undecided
Status: New
** Changed in: landscape/cisco-odl
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server Team,
** Also affects: landscape
Importance: Undecided
Status: New
** Also affects: landscape/release-29
Importance: Undecided
Status: New
** No longer affects: landscape
** Changed in: landscape/release-29
Milestone: None => 15.07
** Also affects: landscape
Importance:
** Tags added: landscape
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1490727
Title:
"Invalid IPC credentials" after corosync, pacemaker service restarts
To manage
** Tags added: landscpae
** Tags removed: landscpae
** Tags added: landscape
--
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/1439649
Title:
Pacemaker unable to communicate with
Just so it's clear, confirmed these steps are broken on an updated vivid
install.
--
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
** Changed in: landscape-client
Status: In Progress = Fix Released
--
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/904248
Title:
python-central build-dependencies in main
Public bug reported:
Issue is described in http://sourceforge.net/p/tmux/tickets/122/
When you switch panes in an even tiled split (say, 2x2, 2x3 or 3x3) a
MRU type algorithm is used to determine where your movement goes across
a split boundary.
This algorithm works fine if your splits are
@arges -- installation of qemu-kvm has fixed the problem.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1387881
Title:
qemu fails to recognize full virtualization
To manage
apport information
** Attachment added: Card0.Codecs.codec.3.txt
https://bugs.launchpad.net/bugs/1387881/+attachment/4250082/+files/Card0.Codecs.codec.3.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1387881/+attachment/4250089/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k3.13.0-39-generic.
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser',
apport information
** Attachment added: PciMultimedia.txt
https://bugs.launchpad.net/bugs/1387881/+attachment/4250086/+files/PciMultimedia.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
apport information
** Attachment added: AlsaDevices.txt
https://bugs.launchpad.net/bugs/1387881/+attachment/4250079/+files/AlsaDevices.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
apport information
** Attachment added: CRDA.txt
https://bugs.launchpad.net/bugs/1387881/+attachment/4250081/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1387881
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1387881/+attachment/4250088/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1387881/+attachment/4250084/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1387881
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1387881/+attachment/4250083/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1387881/+attachment/4250087/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
dpkg -l |grep qemu:
ii qemu-utils 2.0.0+dfsg-2ubuntu1.6
amd64QEMU utilities
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1387881
Title:
qemu fails
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1387881/+attachment/4250090/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/1387881/+attachment/4250092/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1387881/+attachment/4250091/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1387881/+attachment/4250085/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1387881
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1387881/+attachment/4250080/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
apt history.log for packages installed on top of base system. Note that
only the last entry was done by me, the others were done in preparation
of the image:
http://paste.ubuntu.com/8761810/
Basically, I booted a curtain installed maas node with an amd64 trusty
image from maas. Logged in, ran
** Tags added: cloud-installer
--
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/1372977
Title:
1.7.0~beta3+bzr3043-0ubuntu1~ppa3 upgrade breaks squid proxy setup
To manage
With scott's help, I spun this about 2000x over the weekend and did not
hit the issue. I would call it verified from my perspective.
Changing tag.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
** Tags added: cloud-installer landscape
--
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/1366893
Title:
cloud-init --local needs mounted /run but not guaranteed by upstart
job
** Tags added: landscape
--
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/1274944
Title:
maas-dhcp-server should be configured to start after all network
interfaces it serves are up
Got another instance maybe? maas package version:
1.6.1+bzr2548-0ubuntu1~ppa1
ERROR 2014-08-19 20:01:18,871 maasserver
Exception: 'Nonce already used: 48723931'
ERROR 2014-08-19 20:01:18,871 maasserver Traceback (most recent
comment #9 was while running juju bootstrap -v
--
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/1190986
Title:
ERROR Nonce already used
To manage notifications about this bug go to:
I just hit it again -- on upgrading from 1.6rc1
--
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/1300507
Title:
Rabbit password is reset on every upgrade which forces lockstep
cluster
Saw this as well, Latest in trusty - 1.6b6.
** Tags added: landscape
** Tags added: cloud-installer
--
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/1300507
Title:
Rabbit password is
Some suggestions (possibly combine them based on what is possible):
1) Log the download and extraction somewhere and point people at that
log.
2) Print the total number expected in the GUI in that message.
3) Estimate the total size somewhere so we know how long to wait.
4) Import images as
an addendum to my 4) in comment #5:
Perhaps also sneakily prioritizing amd64 as an architecture and trusty
as a release, on the basis that once that's done interesting stuff
should work for most people and demo's can move forward.
--
You received this bug notification because you are a member
** Tags added: landscape
--
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/1299588
Title:
LXC permission denied issue with 1.17.7
To manage notifications about this bug go to:
Seems like it's very easy to repro on AWS. Anything but the bootstrap
node gets this when you deploy lxc ala:
juju deploy --to lxc:1 ubuntu
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
*** This bug is a duplicate of bug 1192651 ***
https://bugs.launchpad.net/bugs/1192651
Public bug reported:
the tool subunit2junitxml as shipped in the subunit package cannot
work without installing python3-junitxml. This should be added as a
dependency of the subunit package in trusty.
*** This bug is a duplicate of bug 1192651 ***
https://bugs.launchpad.net/bugs/1192651
This is not a duplicate of lp:1192651. This specifically requests that
the 'subunit' package includes a dependency on python3-junitxml
(required by one of the scripts it ships). Maybe I'm mistaken in this
This appears to be just subunit v1 output. subunit2junitxml only parses
subunit v2 output. You can use the following fix:
Starting with 13.09, you can address this to parse the old output:
./run-my-old-tests | subunit-1to2 | subunit2junitxml
I'm closing this bug now, as this is just an old
Actually, I guess I'll leave this open to address the packaging issue.
subunit in trusty should include a dependency of python3-junitxml
Sorry for the noise
** Summary changed:
- subunit2junitxml errors parsing subunit v1 output
+ subunit should depend on python3-junitxml
** Description
** Attachment added: Patch to the ubuntu/subunit packaging branch (trusty)
https://bugs.launchpad.net/ubuntu/+source/subunit/+bug/1192651/+attachment/4008347/+files/patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to subunit in
Should this also be ported to 1.17, since that is the default with
trusty?
--
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/1246320
Title:
Azure bootstrap fails: versioning header
** Tags added: theme-oil
--
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/1229275
Title:
[maas] juju destroy-environment also destroys nodes that are not
controlled by juju
To manage
nova boot has a similar problem. You get a 500 when attempting to use
a duplicated (by name) security group:
DEBUG (shell:768) The server has either erred or is incapable of performing the
requested operation. (HTTP 500) (Request-ID:
req-aded6143-c8d0-45fa-abd3-fd28a80cfd0d)
Traceback (most
This does appear to be fixed in trunk -- confirmed.
--
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/1099900
Title:
rados parsing error with hostnames in mon_host
To manage
Public bug reported:
In /etc/ceph/ceph.conf, if I set hostnames in the mon_host variable and
separate them with spaces, the parsing algorithm breaks down. The
expectation is that all three of these cases should work. Once
hostnames are introduced in the mon_host line, spaces are no longer
Was there a bug fix for it? I think a colleague has reproduced the
issue with ceph git trunk.
--
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/1099900
Title:
rados parsing error with
Public bug reported:
Permissions on the created lxc container somehow are reflecting the
users /etc/password file:
ubuntu@dpb-local-landscape-client-0:~$ cat /etc/passwd |grep landscape
landscape:x:104:109::/var/lib/landscape:/bin/false
ubuntu@dpb-local-landscape-client-0:~$ ll /etc/landscape
The following fixes the problem:
dpb@starbuck:templates$ pwd
/usr/share/lxc/templates
dpb@starbuck:templates$ diff *.orig lxc-ubuntu-cloud
344c344
tar -zxf $cache/$filename
---
tar --numeric-owner -zxf $cache/$filename
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 969299 ***
https://bugs.launchpad.net/bugs/969299
If I turn apparmour off, I can no longer effectively install through
juju if the package includes NTP. I'll work to reproduce with a minimal
environment.
--
You received this bug notification because you
*** This bug is a duplicate of bug 969299 ***
https://bugs.launchpad.net/bugs/969299
I'm the same has @breu. the juju charm I was using was making the
hostname of my system 40 characters. Reducing the charm name length
solved the problem. I think this bug should be re-opened and fixed in
Public bug reported:
Latest precise update:
root@ubuntu:~# apt-get install python-image-store-proxy
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation
Public bug reported:
ii nova-api 2012.1~e4~20120210.12574-0ubuntu1 OpenStack Compute - API
frontend
# curl -s http://169.254.169.254/2008-02-01/meta-data/ami-launch-index
1
This should be zero indexed like on amazon:
# curl -s http://169.254.169.254/2008-02-01/meta-data/ami-launch-index
0
**
61 matches
Mail list logo
