Blueprint changed by James Page:
Work items changed:
Work items:
[james-page] Setup team, PPA's and branch for packaging and charms: DONE
[james-page] Package openattestation for Canonical partner archive: DONE
[james-page] Write charm for openattestation: DONE
UPSTREAM - fix issues
Public bug reported:
since some time now, I have a very strange problem with audio output on
a Windows Vista guest. Right after booting the guest, audio output does
not work (that is: I can PLAY audio, but can't hear anything, although
volume is at 100%). If I leave the guest running for some
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1060053
Title:
Audio starts working several hours after starting Windows Vista guest
To manage notifications about this bug go to:
This bug was fixed in the package libvirt - 0.9.8-2ubuntu17.4
---
libvirt (0.9.8-2ubuntu17.4) precise-proposed; urgency=low
* storage-fix-a-potential-crash-when-creating-vol-object: avoid a crash
on bad free() on error lvm storage. (LP: #1035320)
* add pm-utils as suggests to
This bug was fixed in the package libvirt - 0.9.8-2ubuntu17.4
---
libvirt (0.9.8-2ubuntu17.4) precise-proposed; urgency=low
* storage-fix-a-potential-crash-when-creating-vol-object: avoid a crash
on bad free() on error lvm storage. (LP: #1035320)
* add pm-utils as suggests to
I do believe it tries to be careful not to delete other packages' files
in the process. Did you see any files left in those locations?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
Yes, the 127.0.1.1:53 solution works so long as dnsmasq and others are
run in bind-interfaces (or equivalent) mode.
NM-dnsmasq currently (12.04) listens at 127.0.01:53 which prevents
others from listening on either ALL:53 or lo:53, i.e., 127.0.0.1:53.
The new (12.10) behavior allows others to
** Tags added: canonistack
--
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/1059899
Title:
nova fails to configure dnsmasq, resulting in DNS timeouts in
instances
To manage
IIRC correctly the not deleted files were pyc files.
--
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/1059973
Title:
purging packages can't remove files because dirs are not empty
To
Public bug reported:
# lsb_release -rd
Description:Ubuntu 12.04.1 LTS
Release:12.04
# apt-cache policy puppet
puppet:
Installed: 2.7.11-1ubuntu2.1
Candidate: 2.7.11-1ubuntu2.1
Version table:
*** 2.7.11-1ubuntu2.1 0
500 http://gb.archive.ubuntu.com/ubuntu/
Oh, i forgot to mention. I discovered this bug on a server, and then to
confirm i set up a clean install of ubuntu server (same version) in
virtualbox and it shows the same problem.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Branch linked: lp:~jimbaker/juju/hook-command-error-cases
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1050592
Title:
exceptions.TypeError: object of type 'NoneType' has no len()
This was because of some config option gone wrong. invalid.
** Changed in: libvirt (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1060175
We use python-setup-git for our ci testing so that we can create
tarballs based off the git tree, so it is necessary for the packaging
building but not necessarily for the archive since we use the upstream
tarballs.
** Changed in: nova (Ubuntu)
Status: New = Won't Fix
--
You received
** Branch linked: lp:~therve/cloud-init/fix-landscape-config-precise
--
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/1042758
Title:
landscape handler needs to set RUN=1 in
Public bug reported:
I got the following error when I ran sudo apt-get remove --purge --yes
isc-dhcp-server bind9 maas python-django-maas maas-cli python-maas-
client maas-dhcp maas-dns
Purging configuration files for maas-cluster-controller ...
Removing user `maas' ...
Warning: group `maas' has
** Also affects: lxc (Ubuntu Precise)
Importance: Undecided
Status: New
--
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/1050351
Title:
lxc-start-ephemeral suppresses command
So there needs an option to have multiple dns servers correct?
** Changed in: nova (Ubuntu)
Status: New = Incomplete
** Changed in: nova (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Same problem. Patch fixes it for me.
** Changed in: logwatch (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to logwatch in Ubuntu.
https://bugs.launchpad.net/bugs/1058760
Title:
unmatched
Public bug reported:
Got this error installing maas - 0.1+bzr1122+dfsg-0+1132+112~ppa0~quantal1
...
maas-cluster-celery start/running, process 12831
Processing triggers for ureadahead ...
Setting up maas (0.1+bzr1122+dfsg-0+1132+112~ppa0~quantal1) ...
Setting up maas-dhcp
In precise and quantal (as of today, 2 October 2012) the logwatch config
still directs logwatch to look in messages.
** Tags added: lucid natty precise quantal
** Summary changed:
- Ubutu-specific afpd configuration missing
+ Logwatch looks for afpd output in messages, not in log files that
Blueprint changed by Chuck Short:
Work items changed:
Work items:
Write up policy for cloud archive: DONE
Write up process for cloud archvie: DONE
Create related packaging branches: DONE
Write upgrade tests for Openstack: POSTPONED
Create openstack-ci infrastructure: DONE
Liase with
Public bug reported:
**Unmatched Entries**
pam_sss(sshd:auth): authentication success; logname= uid=0 euid=0 tty=ssh
ruser= rhost=[CENSORED] user=[CENSORED] : 1 time(s)
Probably lines similar to these in
/usr/share/logwatch/scripts/services/sshd are needed:
($ThisLine =~
** Tags added: ops
--
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/1059899
Title:
nova fails to configure dnsmasq, resulting in DNS timeouts in
instances
To manage notifications
Looks like r111 of the packaging branch caused this. maas-dhcp tries to
stop isc-dhcp-server, but since it wasn't running (this was a new
install), apt-get got this error instead isc_dhcp_server: unrecognized
service
--
You received this bug notification because you are a member of Ubuntu
Server
Thanks for reporting this bug. Could you give the full kvm command line
you are using, or, if you are using libvirt, the xml domain definition?
Do you know exactly when this started happening? Does this happen with
linux guests as well?
** Changed in: qemu-kvm (Ubuntu)
Status: New =
I'm using libvirt, but here's the kvm command line as taken from ps
-ef|grep kvm anyway:
/usr/bin/kvm-spice -name WindowsVista -S -M pc-1.0 -cpu
Opteron_G3,+wdt,+skinit,+osvw,+3dnowprefetch,+cr8legacy,+extapic,+cmp_legacy,+3dnow,+3dnowext,+pdpe1gb,+fxsr_opt,+mmxext,+ht,+vme
-enable-kvm -m 2048
To confirm, this is purely a build dependency, and not a binary
dependency. This means that it should not be installing python-
setuptools-git on your system, if it is - please re-open this bug.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Changed in: samba (Ubuntu)
Status: Incomplete = Confirmed
--
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/913809
Title:
smbd crashed with SIGABRT in rep_strlcpy()/null
This now cleanly backports to oneiric from quantal.
Using:
backportpackage -s quantal -d oneiric -B pbuilder-dist -b whois -w .
** Description changed:
- Please backport whois 5.0.17 (main) from quantal
+ Please backport whois 5.0.19 (main) from quantal
Description:
- Please backport
I believe this is already handled by the changelog and NEWS entries
already present. Closing as Fix Released.
** Changed in: php5 (Ubuntu Quantal)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5
I believe the problems manifest themselves when pointed at Rackspace
Cloud.
** Changed in: juju
Assignee: (unassigned) = Martin Packman (gz)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
Everything ;-)
So we need to maintain compatibility with diablo/hpcloud and essex. The
core of the changes are nova-volume and nova-network split out into
separate services (cinder quantum). We'll need to do some more magic
around svc catalog introspection and dispatch of capabilities handling
This is also what rackspace public cloud v2 offering is on. Their service
catalog is a bit complicated because it also has multiple nova endpoint
versions advertised in it (relating to the fact they really have more than
one implementation to choose from).
-k
On Tue, Oct 2, 2012 at 12:22 PM,
** Changed in: genshi (Ubuntu Quantal)
Milestone: ubuntu-12.10-beta-2 = ubuntu-12.10
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a bug assignee.
https://bugs.launchpad.net/bugs/935516
Title:
genshi version 0.6-2 FTBFS on i386 in precise
Blueprint changed by James Page:
Work items changed:
Work items for quantal-alpha-3:
[james-page] Ceph 0.47.2 update for Ubuntu: DONE
[james-page] Ceph 0.48 update for Ubuntu: DONE
[james-page] Review MIR actions for ceph from last cycle: DONE
[james-page] Check on status of libvirt+rdb
** Branch linked: lp:~gandelman-a/ubuntu/quantal/openvswitch/1.4.3
--
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/bugs/1057098
Title:
[FFe] Please update to 1.4.3
To manage
Sorry to get back with this again, but a flaw was found that may cause data
loss and was fixed only in 8.3.13.
http://lists.linbit.com/pipermail/drbd-announce/2012-May/000169.html
Of course, the problem is in the kernel module, not the userspace tools, so I
guess it's the kernel package that
No log files available - known issue that was patched in 8.3.13 as noted
in comment #3 above.
Especially important since the new default scheduler of cfq in Precise
is known to cause the bug.
** Changed in: drbd8 (Ubuntu)
Status: Triaged = Confirmed
** Changed in: linux (Ubuntu)
This bug is missing log files that will aid in diagnosing the problem.
From a terminal window please run:
apport-collect 912254
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment
Public bug reported:
Installing nova-novncproxy 2012.2-0ubuntu2:
$ sudo apt-get install nova-novncproxy
$ service nova-novncproxy status
nova-novncproxy: unrecognized service
$ which nova-novncproxy
In addition to this affecting Nova, the novnc package's init scripts
requires the presence of
FFe Approved.
Having discussed the testing that this has undergone, and understanding
that most people seem to have been using the PPA as of late, and that
this resolves some release critical issues.
Thanks.
** Changed in: juju (Ubuntu)
Status: New = Triaged
--
You received this bug
This bug was fixed in the package openvswitch - 1.4.3-0ubuntu1
---
openvswitch (1.4.3-0ubuntu1) quantal; urgency=low
* New upstream release (LP: #1057098).
* Dropped Debian patches:
- debian/patches/debian-changes-1.4.2+git20120612-6
-
As discussed in IRC:
If the domain I assign to nova is its own (which I believe it should
be), then it should be authoritative for that zone. As in it shouldn't
go asking the upstream resolver to give it answers for things that are
delegated to it. This is also true of the reverse zone for the
Public bug reported:
Commit @ https://review.openstack.org/#/c/13633/ removes the explicit
specification of volume config files to tgt-admin, and instead relies in tgt's
configuration being set to find those config files in the appropriate place
(nova's volumes directory). We've been
Thanks James Clint for your answers.
I would like to add some details:
Currently, as a temporary solution, we use crontab to kill the process
at 00h00 and start again at 00h01. With that, we are sure that the agent
works every days.
With my co-worker, we have updated a server (Ubuntu 12.04
** Branch linked: lp:~openstack-ubuntu-testing/nova/quantal-folsom-
proposed
** Branch linked: lp:~openstack-ubuntu-testing/nova/precise-folsom-
proposed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
** Branch linked: lp:~openstack-ubuntu-testing/nova/quantal-folsom-
proposed
** Branch linked: lp:~openstack-ubuntu-testing/nova/precise-folsom-
proposed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
** Description changed:
Please backport whois 5.0.19 (main) from quantal
Description:
Please backport whois 5.0.19 (main) from quantal to oneiric.
Reason for the backport:
This provides some needed updates to users who need to query .hr/.sx/.pe
TLDs,
** Description changed:
Please backport whois 5.0.19 (main) from quantal
Description:
Please backport whois 5.0.19 (main) from quantal to oneiric.
Reason for the backport:
This provides some needed updates to users who need to query .hr/.sx/.pe
TLDs,
** Changed in: maas (Ubuntu)
Status: New = Fix Committed
--
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/1060237
Title:
apt-get install maas maas-dhcp maas-dns fails
To manage
fwiw, its actually a packaging bug to change configuration of another
package (by disabling it).
--
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/1059459
Title:
Existing DHCP server not
Ok - I'm able to reproduce this when qemu-user-static is not installed.
When qemu-user-static is installed, container creation succeeds.
Looking at the lxc-ubuntu template, I'm not sure what we want to do in
the failing case. I would guess we want to announce that qemu-armhf-
static is not
I have confirmed that the updated packages solve the issue by doing a
devstack install on standard precise, seeing the issue, upgrading the
ovs packages manually via deb, rebooting the system to load the new
kernel module, and then testing that the issue is no longer seen.
thanks!
** Tags
This bug was fixed in the package nova - 2012.2-0ubuntu3
---
nova (2012.2-0ubuntu3) quantal; urgency=low
* nova-xvpvncproxy, nova-novncproxy: Add missing .install, .logrotate,
.postrm, manpages and upstart jobs (LP: #1060336)
* debian/{rules, nova-volume.install}: Rename
This bug was fixed in the package nova - 2012.2-0ubuntu3
---
nova (2012.2-0ubuntu3) quantal; urgency=low
* nova-xvpvncproxy, nova-novncproxy: Add missing .install, .logrotate,
.postrm, manpages and upstart jobs (LP: #1060336)
* debian/{rules, nova-volume.install}: Rename
** Branch linked: lp:~barry/ubuntu/quantal/genshi/lp935516
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a bug assignee.
https://bugs.launchpad.net/bugs/935516
Title:
genshi version 0.6-2 FTBFS on i386 in precise
To manage notifications about
@jibel,
to be clear, you should NOT get this if you have qemu-user-static
installed. If you do, please shout to have the priority raised.
The question for now is what we should do about this. Should we detect
foreign arch and insist qemu-user-static be installed?
In the meantime, since there
(my guess fwiw is that calling qemu-arm in a chroot fails because the
libraries it links against are not available; hence the need for qemu-
arm-static)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
also linking to python-keystoneclient project since it's CLI related
** Also affects: python-keystoneclient
Importance: Undecided
Status: New
** Changed in: python-keystoneclient
Importance: Undecided = High
** Changed in: python-keystoneclient
Status: New = Triaged
**
Thanks - what exact command are you using to connect? spicy?
** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete = New
** Package changed: qemu-kvm (Ubuntu) = qemu-kvm-spice (Ubuntu)
** Changed in: qemu-kvm-spice (Ubuntu)
Status: New = Incomplete
--
You received this bug
Did a local test build, and the package in unapproved appears to indeed
fix this. Approved through the queue.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a bug assignee.
https://bugs.launchpad.net/bugs/935516
Title:
genshi version 0.6-2 FTBFS
This bug was fixed in the package genshi - 0.6-2ubuntu1
---
genshi (0.6-2ubuntu1) quantal; urgency=low
* genshi/filters/tests/html.py: Adjust some tests which used to fail
before changes in upstream Python 2.7.3. These now succeed. While
this change is appropriate for the
I can't reopen this bug. Please have a look at the debian/control file
of python-nova it is a depends not a build depends.
It should depend on python-setuptools not python-setuptools-git
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Branch linked: lp:ubuntu/genshi
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a bug assignee.
https://bugs.launchpad.net/bugs/935516
Title:
genshi version 0.6-2 FTBFS on i386 in precise
To manage notifications about this bug go to:
Only first line with devnode work.
Working config:
devnode_blacklist {
## Ubuntu BUG #927540
devnode ^((ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*|(hd|xvd|vd|sd)[a-z]*)
wwid *
}
## Use user friendly names, instead of using WWIDs as names.
defaults {
user_friendly_names yes
path_grouping_policy
Sorry, this config not working too.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/927540
Title:
multipath ignores blacklist in multipath.conf
To manage notifications
Public bug reported:
ipsec-tools 0.7.1 which comes with Lucid has a bug (several, really)
that renders it inoperable for host-to-host IPSec via IPv6. The
particular bug I'm interested in eliminating has already been addressed
in ipsec-tools 0.8.0 which is available as of Oneiric.
The bug is
Public bug reported:
Got this error installing maas 0.1+bzr1134+dfsg-0+1136+113~ppa0~quantal1
with apt-get install maas maas-dhcp maas-dns
matsubara Setting up maas-dns (0.1+bzr1134+dfsg-0+1136+113~ppa0~quantal1) ...
matsubara chown: invalid user: `maas:root'
matsubara dpkg: error processing
Public bug reported:
use lxc-start-ephemeral to start four ephemeral containers
then lxc-ls reports twice as many as it should:
$ ls /var/lib/lxc/
lptests lptests-temp-1FaKWwb lptests-temp-c8jcW0W lptests-temp-qoZ6ncr
lptests-temp-wbvIQLE
jenkins@ip-10-218-67-147:~$ watch lxc-ls
$ lxc-ls
** Changed in: maas (Ubuntu)
Status: New = In Progress
** Changed in: maas (Ubuntu)
Assignee: (unassigned) = Julian Edwards (julian-edwards)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
** Branch linked: lp:~julian-edwards/maas/broken-dns-install-bug-1060549
--
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/1060549
Title:
maas-dns fails to install because maas user
Update for the record. As we have since found out, it's much worse than
just needing an expect fork. Somewhere along the line, before it gets
around to running the start-cluster-controller code proper, maas-
provision does a whole bunch of other forks. The question is whether we
can make
** Changed in: maas (Ubuntu)
Status: In Progress = Fix Committed
--
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/1060549
Title:
maas-dns fails to install because maas user
Fair enough. How else could we do this?
** Changed in: maas
Assignee: (unassigned) = Julian Edwards (julian-edwards)
** Changed in: maas
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas
Chris, since this is in quantal now, we'll need to backport through
precise, so we'll need the reverse dependencies tested with the latest
version of whois built on oneiric and precise.
** Also affects: precise-backports
Importance: Undecided
Status: New
--
You received this bug
On Wednesday 03 October 2012 02:47:05 you wrote:
Update for the record. As we have since found out, it's much worse than
just needing an expect fork. Somewhere along the line, before it gets
around to running the start-cluster-controller code proper, maas-
provision does a whole bunch of
77 matches
Mail list logo
