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
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
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
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
**
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
*** 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:
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
** 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
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
*** 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
** 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.
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
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
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
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:
** 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
** 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
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
--
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
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
@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
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
**
: #961894)
* Add i18n to the landscape-client-ui-install script. (LP: #961891)
-- David Britton d...@canonical.com Thu, 22 Mar 2012 10:10:39 -0600
** Affects: landscape-client (Ubuntu)
Importance: Undecided
Status: New
** Branch linked: lp:~landscape/landscape-client/landscape
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
** Changed in: landscape-client (Ubuntu)
Status: Fix Committed = 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/962448
Title:
update package to 12.04.2
To manage notifications
Newly installed oneric vm shows the update available.
ubuntu@ubuntu:~$ apt-cache show landscape-client
Package: landscape-client
Priority: optional
Section: admin
Installed-Size: 212
Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com
Original-Maintainer: Landscape Team
deb http://dl.google.com/linux/chrome/deb/ stable main
deb http://dl.google.com/linux/talkplugin/deb/ stable main
#deb http://dl.google.com/linux/earth/deb/ stable main
I can get the failure pretty consistently on oneiric with the above two
lines enabled.
- either alone work fine
- either
Wanted to update this in case anyone else came in, the thunderbird
extension here appears to be actively developed and works really well in
my environment:
https://launchpad.net/libnotify-mozilla
It was in a comment earlier, but this is a more direct link.
--
You received this bug
Looks good. Thanks All!
** 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/1058218
Title:
do-release-upgrade (lucid-precise)
Bad news, after the upgrade, postgres-8.4 is still not running:
root@ubuntu:~# /etc/init.d/postgresql-8.4 status
Running clusters:
root@ubuntu:~#
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Attached files from upgrade attempt with 8.4.14-0ubuntu12.04.1
** Attachment added: dist-upgrade.tar.gz
https://bugs.launchpad.net/ubuntu/+source/postgresql-8.4/+bug/1058218/+attachment/3393646/+files/dist-upgrade.tar.gz
--
You received this bug notification because you are a member of
Martin -- Yes, after a reboot, 8.4 is running.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1058218
Title:
do-release-upgrade (lucid-precise) leaves postgres 8.4 in bad state
To manage
root@ubuntu:~# ls -l /etc/init.d/postgres*
-rwxr-xr-x 1 root root 1095 Sep 6 12:53 /etc/init.d/postgresql
-rwxr-xr-x 1 root root 1027 Sep 27 05:46 /etc/init.d/postgresql-8.4
root@ubuntu:~# pg_lsclusters
Version Cluster Port Status OwnerData directory Log
file
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
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
** Tags added: theme-oil
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1229275
Title:
[maas] juju destroy-environment also destroys nodes that are not
controlled by juju
To manage notifications
Public bug reported:
It's happened a couple times now. I suspend, and it hangs with the
keyboard LEDs illuminated, the power still on, but everything else off.
Only option to recover is to hard reset the system (hold down the power
button).
I'll attach the crash file if it's not already.
Crash file from the suspend.
** Attachment added: susres.2013-10-18_20:25:11.437666.crash
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1241911/+attachment/3883079/+files/susres.2013-10-18_20%3A25%3A11.437666.crash
--
You received this bug notification because you are a member of
/proc/acpi/wakeup
Device S-state Status Sysfs node
P0P2 S4*disabled pci::00:01.0
ECS4*disabled
HDEF S4*disabled pci::00:1b.0
RP02 S4*disabled pci::00:1c.1
ARPT S4*disabled pci::02:00.0
EHC1 S3*enabled
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1099900
Title:
rados parsing error with hostnames in
This does appear to be fixed in trunk -- confirmed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1099900
Title:
rados parsing error with hostnames in mon_host
To manage notifications about this
Rudimentry Lucid client tests went ok from proposed. Install, Upgrade,
Script, package install, graphs, hardware reporting.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/978884
Title:
SRU: release
Rudimentry natty/oneiric tests went ok from proposed as well. Install,
Upgrade, Script, package install, graphs, hardware reporting.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/978884
Title:
The following patch to service fixes it for precise. This may not be
the most graceful, but this bug is really annoying. Could we get
something pushed through?
121c121,128
start|stop|status|reload)
---
status)
# Make sure status only succeeds in the started case
Hi Martin --
I'm still seeing an anomoly in the upgrade. After do-release upgrade,
postgres-8.4 is no longer running. I see at the beginning of the
upgrade, the explicit stop of the service, but I never see it started
again. After I upgrade, I get the following:
root@ubuntu:~# sudo -u
Screen log from the update attempt.
** Attachment added: screenlog.0.gz
https://bugs.launchpad.net/ubuntu/+source/postgresql-8.4/+bug/1058218/+attachment/3365652/+files/screenlog.0.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
More debugging: failed attempt by libpam to restart postgresql
(postgresql-8.4 in lucid does not have an init script called
postgresql, it's called postgresql-8.4) :
Setting up libpam0g (1.1.3-7ubuntu2) ...
Checking for services that may need to be restarted...Checking init scripts...
WARNING:
Here is where I would expect to see the start of postgresql-8.4 on
precise after the upgrade, but I don't see it:
Setting up postgresql-8.4 (8.4.14-0ubuntu12.04) ...
Setting up python-central (0.6.17ubuntu2) ...
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Upgrade from lucid - precise using packages in pitti's PPA work great.
Attached apt-term.log from that attempt just for safe keeping.
** Attachment added: apt-term.log
https://bugs.launchpad.net/ubuntu/+source/postgresql-8.4/+bug/1058218/+attachment/3366205/+files/apt-term.log
--
You
Upgrade from lucid - precise using 9.1 packages in pitti's PPA work
great. Attached apt-term.log from that attempt just for safe keeping.
** Attachment added: apt-term.log
https://bugs.launchpad.net/ubuntu/+source/postgresql-8.4/+bug/1058218/+attachment/3366251/+files/apt-term.log
--
You
Public bug reported:
I'm seeing a bug in both 8.4 and 9.1 after upgrading through do-release-
upgrade from lucid to precise.
Steps to Repro:
1) Install either 9.1 from pitti's repo, or use 8.4 in lucide
2) run do-release-upgrade
3) Skip the reboot
4) run the following
root@ubuntu:~# sudo -u
*** 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
Reproduced by:
sudo apt-get install vlan
sudo vconfig add eth0 2
sudo ifconfig eth0.2 192.168.8.8 # or some other unusued local address
landscape-sysconfig # should filter out that interface.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Grub-efi-amd64 package upgrade to trusty (from saucy) fails. I get an
odd error when running
dpb@starbuck:grub-efi-amd64$ sudo apt-get -f install grub-efi-amd64
Reading package lists... Done
Building dependency tree
Reading state information... Done
grub-efi-amd64 is
** Attachment added: grub-install -v output
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1282375/+attachment/3987680/+files/grub-install-v-output.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246320
Title:
Azure bootstrap fails: versioning header is not specified
To
** Tags added: landscape
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1299588
*** 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
Bugs, which is subscribed to Ubuntu.
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
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1372977
Title:
1.7.0~beta3+bzr3043-0ubuntu1~ppa3 upgrade breaks squid proxy setup
To manage notifications about this
** Also affects: ntpmaster (Ubuntu)
Importance: Undecided
Status: New
** Branch linked: lp:~tribaal/charms/trusty/ntpmaster/resync-charm-
helpers
** Changed in: ntpmaster (Ubuntu)
Status: New = Fix Released
** Changed in: ntpmaster (Ubuntu)
Assignee: (unassigned) = David
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1190986
Title:
ERROR Nonce already used
To manage notifications about this bug go to:
** Tags added: landscape
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1274944
Title:
maas-dhcp-server should be configured to start after all network
interfaces it serves are up
To manage
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300507
Title:
Rabbit password is reset on every
I just hit it again -- on upgrading from 1.6rc1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300507
Title:
Rabbit password is reset on every upgrade which forces lockstep
cluster restarts
To
1 - 100 of 507 matches
Mail list logo
