Thanks for reporting this
Looking at the logs it seems to be an issue with mysql connection. Please can
you check mysql status and connection parameters and retry?
** Changed in: keystone (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Please could you check the latest upstream version of nagios-plugins to
see if this is a bug in Ubuntu or in the upstream project itself? If it
turns out to be upstream, this bug would best be submitted and
Blueprint changed by Yolanda Robla:
Work items changed:
Work items:
[andreserl] write dep-8 test for heartbeat/corosync/pacemaker: TODO
[andreserl] write dep-8 test for tftpd-hpa: TODO
[gandelman-a] write dep-8 test for haproxy: TODO
[gandelman-a] write dep-8 tests puppet + facter: TODO
Well, I don't think that this is fixed, according to
http://search.cpan.org/~jesse/perl-5.14.0/pod/perl5135delta.pod#Use_of_qw%28...%29_as_parentheses
the qw() function has to be wrapped in parentheses in order to be parsed
correctly by perl 5.
If you do grep 'qw(' /usr/share/munin/plugins/* -n
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I can reproduce this problem as it appears in your cache.log with the
command:
http_proxy=http://localhost:3128/ curl -H 'Accept-Language: pt-bz'
http://nonexistent.example.com
It looks like squid is simply
** Changed in: facter (Ubuntu Quantal)
Status: New = Triaged
** Changed in: facter (Ubuntu Raring)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to facter in Ubuntu.
** Changed in: facter (Ubuntu)
Status: New = Triaged
** Changed in: facter (Ubuntu Precise)
Status: New = Triaged
** Changed in: facter (Ubuntu Quantal)
Status: New = Triaged
** Changed in: facter (Ubuntu Raring)
Status: New = Triaged
--
You received this bug
I presume this crash is reproducible? In that case, could you try a few
things to isolate the problem, please?
As you say this could be a regression caused by an update, please
downgrade to samba packages of version 2:3.6.3-2ubuntu2 and see if that
fixes the problem. If it does, then please try
Blueprint changed by Louis Bouchard:
Work items changed:
Work items:
- [louis-bouchard] document use of cloud images in kvm in the server guide:
POSTPONED
+ [louis-bouchard] document use of cloud images in kvm in the server guide: DONE
[motu] package oz (see links above): POSTPONED
Hi,
Any update / solution on this issue?
I got the same problem as I install OpenStack Grizzly on VM with OS Ubuntu
12.04 (The Host OS is Ubuntu 12.04 as well).
set libvirt_type=qemu in nova.conf does not work too.
When execute virsh capabilities I got...
some information omited...
Thanks. I misunderstood your report before. I now understand, have
confirmed by reading the full init script and forwarded the bug on to
Debian.
Ubuntu is ahead of Debian in the upstream version but this script comes
from a patch in Debian packaging, so ideally Debian will accept a fix
and then
Blueprint changed by Yolanda Robla:
Work items changed:
Work items:
[andreserl] write dep-8 test for heartbeat/corosync/pacemaker: TODO
[andreserl] write dep-8 test for tftpd-hpa: TODO
[gandelman-a] write dep-8 test for haproxy: TODO
[gandelman-a] write dep-8 tests puppet + facter: TODO
@stgraber, That is a good point. However, I'm not sure it's practical
to bake a solution tied to using iPXE, even if chain loaded, still
requires an initial DHCP lease to be consumed by the firmware PXE
client.
I still maintain that a pretty good direction for this fix is the
ignore-client-uid
Public bug reported:
I'm trying to install Nagios3 and apt reports an error with the
dependency nagios3-cgi:
Les paquets suivants contiennent des dépendances non satisfaites :
nagios3 : Dépend: nagios3-cgi (= 3.2.3-3ubuntu1) mais ne sera pas installé
E: Impossible de corriger les problèmes, des
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I cannot reproduce this problem on 13.04. I can install nagios3, and
nagios3-cgi is pulled in as expected.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm
Confirming that Nova and Keystone have been rebased on a security
update, and accepted into quantal-proposed.
Thanks.
--
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/1179707
Title:
Thanks for your work
** Changed in: python-gevent (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-gevent in Ubuntu.
https://bugs.launchpad.net/bugs/1181942
Title:
Sync python-gevent
This bug was fixed in the package python-gevent - 0.13.7-4
Sponsored for Logan Rosen (logan)
---
python-gevent (0.13.7-4) unstable; urgency=low
* Last bits of -dbg package fix (closes: #703611).
-- Laszlo Boszormenyi (GCS) g...@debian.hu Sun, 24 Mar 2013 01:18:51
+0100
Confirmed that Nova and Keystone have been re-based and accepted into
raring-proposed.
Thanks.
--
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/1179626
Title:
Meta bug for tracking
Is it possible to backport this patch on Lucid?
The server version is still supported and this patch is needed, otherwise slapd
will break Kerberos KDC.
The solution of adding the sleep 1 to the slapd init script is really
odd.
--
You received this bug notification because you are a member
** Changed in: memcached (Debian)
Status: Unknown = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to memcached in Ubuntu.
https://bugs.launchpad.net/bugs/1177398
Title:
init-script status method doesn't handle instances
Public bug reported:
no further details
ProblemType: Package
DistroRelease: Ubuntu 12.10
Package: qemu 1.2.0+noroms-0ubuntu2.12.10.4
ProcVersionSignature: Ubuntu 3.5.0-31.52-generic 3.5.7.11
Uname: Linux 3.5.0-31-generic x86_64
ApportVersion: 2.6.1-0ubuntu10
AptOrdering: qemu: Purge
Blueprint changed by Scott Moser:
Work items changed:
Work items:
[louis-bouchard] document use of cloud images in kvm in the server guide: DONE
[motu] package oz (see links above): POSTPONED
- [utlemming] update https://help.ubuntu.com/community/UEC/Images for
cloud-localds: POSTPONED
+
Confirmed fixed. Thanks!
** Changed in: openssh (Ubuntu)
Status: Confirmed = Fix Released
--
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/1180834
Title:
No such identity
To
Public bug reported:
on 13.04, after running maas-import-pxe, we end up with 2 copies of the
root.tar.gz files (that are available for the fast path installer).
example:
/var/lib/maas/ephemeral/raring/ephemeral/amd64/20130518/dist-root.tar.gz
Public bug reported:
Currently we wget the ubuntu-cloud template without any integrity
verification. We then proceed to execute binaries like /bin/passwd
while still in the ubuntu-cloud template (in a chroot, but without any
effective containment). We should be verifying that the image we
Thanks - I follow you now.
I've reproduced this behaviour on 2.2.14-5ubuntu8.11 (Lucid),
2.2.22-1ubuntu1.3 (Precise) and 2.2.22-6ubuntu5 (Saucy).
But I can't find any regression as you describe.
The init script does have access to the owner and group configured in
/etc/apache2/envvars, so I
@shedoh,
Please post the full xml for a failing vm.
--
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/1031063
Title:
internal error no supported architecture for os type 'hvm'
To
Thanks for reporting this bug. Unfortunately I can't quite tell from
the logs what was going on.
Could you tell us exactly what triggered this? Did this happen on 'sudo
apt-get purge qemu'? (that is the last action logged in
DpkgHistoryLog.txt)
What does 'dpkg -l | grep qemu' show now?
Could
This install command worked for me on precise:
sudo sh -c mkdir -p /var/lib/rrdcached/db /var/lib/rrdcached/journal
chown $(printf %q $USER):$(printf %q $(groups | awk '{print $1}'))
/var/lib/rrdcached/db /var/lib/rrdcached/journal apt-get install
rrdcached
--
You received this bug
Public bug reported:
1. set lxc.logfile = /tmp/foo
2. use set -x on any pre-mount… or equivalent scripts
3. try to use echo or anything else in the script
4. run lxc-start
see that nothing from those scripts (nor stderr, nor stdout) are logged
into those files. This makes it particularly
Public bug reported:
No log at all are written, even with:
lxc.loglevel = debug
lxc.logfile = /tmp/foo
the file is created, but remains empty.
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
I tried multiple things:
c.set_config_item(lxc.loglevel, 1)
c.set_config_item(lxc.loglevel, 9)
c.set_config_item(lxc.loglevel, debug)
And I always get:
lxc: invalid log priority 9
Without those, setting in the lxc config:
lxc.logfile = /tmp/foo
lxc.loglevel = debug
it creates an empty /tmp/foo
*** This bug is a duplicate of bug 1181136 ***
https://bugs.launchpad.net/bugs/1181136
** This bug has been marked a duplicate of bug 1181136
Empty log file when a container is started with the API
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Yes it will continue to work without manual configuration. We've already
discussed this with ScottK via the IRC channel and he had agreed that
this is good to go.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
Thanks, this is likely related to how the python bindings are
interpreting the second command. I woudl actually expect
c.set_config_item('lxc.loglevel', 'info') to work, but that
fails here too.
status: confirmed
assignee: stgraber
priority: medium
--
You received this bug notification
*** This bug is a duplicate of bug 1182085 ***
https://bugs.launchpad.net/bugs/1182085
Please add
lxc.loglevel = 1
I'm going to mark this as a dup of the bug about lxc.loglevel not being
documented in lxc.conf(5). If this does not work for you, then please
show the output and un-mark this
*** This bug is a duplicate of bug 1181136 ***
https://bugs.launchpad.net/bugs/1181136
Quoting Didier Roche (didro...@ubuntu.com):
Public bug reported:
No log at all are written, even with:
lxc.loglevel = debug
lxc.logfile = /tmp/foo
When I add
lxc.loglevel=1
lxc.logfile=/tmp/foo
to
Thank you for reporting this bug to Ubuntu. hardy has reached EOL
(End of Life) and is no longer supported. As a result, this bug
against hardy is being marked Won't Fix. Please see
https://wiki.ubuntu.com/Releases for currently supported Ubuntu
releases.
Please feel free to report any other bugs
Thank you for reporting this bug to Ubuntu. oneiric has reached EOL
(End of Life) and is no longer supported. As a result, this bug
against oneiric is being marked Won't Fix. Please see
https://wiki.ubuntu.com/Releases for currently supported Ubuntu
releases.
Please feel free to report any other
Thank you for reporting this bug to Ubuntu. hardy has reached EOL
(End of Life) and is no longer supported. As a result, this bug
against hardy is being marked Won't Fix. Please see
https://wiki.ubuntu.com/Releases for currently supported Ubuntu
releases.
Please feel free to report any other bugs
Thank you for reporting this bug to Ubuntu. oneiric has reached EOL
(End of Life) and is no longer supported. As a result, this bug
against oneiric is being marked Won't Fix. Please see
https://wiki.ubuntu.com/Releases for currently supported Ubuntu
releases.
Please feel free to report any other
Thank you for reporting this bug to Ubuntu. hardy has reached EOL
(End of Life) and is no longer supported. As a result, this bug
against hardy is being marked Won't Fix. Please see
https://wiki.ubuntu.com/Releases for currently supported Ubuntu
releases.
Please feel free to report any other bugs
*** This bug is a duplicate of bug 1181136 ***
https://bugs.launchpad.net/bugs/1181136
did you try with the python bindings (hence why I duplicated it to the
other bug report)?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc
Public bug reported:
The saucy smoke test for lxc test_lxc_apparmor appears to be hung with
saucy installations of 20130521.
The following tests appear to have completed successfully.
- test: test_lxc_reboot
- test: test_lxc_simple
- test: test_lxc_api
The steps to reproduce:
1. utah is used
We not only end up with to copies of root.tar.gz but we also end up with
two copies of 'initrd' and 'linux' files.
ubuntu@cluster:~$ ls /var/lib/maas/ephemeral/precise/ephemeral/amd64/20121008/
disk.img info initrd.gz linux root.tar.gz tgt.conf
ubuntu@cluster:~$ ls
two*
--
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/1182459
Title:
clean up root.tar.gz and fast path installer files
To manage notifications about this bug go to:
Thank you for reporting this bug to Ubuntu. oneiric has reached EOL
(End of Life) and is no longer supported. As a result, this bug
against oneiric is being marked Won't Fix. Please see
https://wiki.ubuntu.com/Releases for currently supported Ubuntu
releases.
Please feel free to report any other
Thank you for reporting this bug to Ubuntu. oneiric has reached EOL
(End of Life) and is no longer supported. As a result, this bug
against oneiric is being marked Won't Fix. Please see
https://wiki.ubuntu.com/Releases for currently supported Ubuntu
releases.
Please feel free to report any other
Blueprint changed by Serge Hallyn:
Definition Status: Discussion = Drafting
--
Virtualization Stack Work for Saucy
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-virtstack
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe
** Tags added: qa-daily-testing rls-s-incoming
--
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/1182540
Title:
lxc smoke test, test_lxc_apparmor appears to hang on saucy VM
To manage
Public bug reported:
On start up. Don't know what to do to reproduce the bug other than using
the latest updates from Ubuntu 13.04 ( inluding proposed ) and starting
the system.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: clamav-freshclam 0.97.8+dfsg-1ubuntu1.13.04.1
SegvAnalysis : Segfaullt happened at: 0x7f372ca408c1:mov
(%rdx,%rax,8),%rsi
PC (0x7f372ca408c1) ok
source (%rdx,%rax,8) (0x7f3827d053a0) not located in a known VMA region
(needed readable region)!
destination %rsiok
Signal : 11
Uname : Linux 3.8.0-22-generic x86_64
I'll leave the
Hello Andres, or anyone else affected,
Accepted celery into precise-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/celery/2.4.6-1ubuntu0.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
When I took a close look the first time, it appeared to be hung in the
lxc-ubuntu template on flock.
If this is reproducible, and hangs again on flock, then it sounds like a
kernel bug and we should mark as affecting linux.
I couldn't reproduce this on a saucy canonistack instance, but that may
Marking incomplete until it is reproduced. If it happens again, then
please mark it confirmed.
** Changed in: lxc (Ubuntu)
Importance: Undecided = High
** Changed in: lxc (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
** Changed in: openssh (Ubuntu)
Assignee: (unassigned) = Colin Watson (cjwatson)
** Changed in: openssh (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
This is occurring in all the runs with today's image. The latest active
one is on utah-9138-saucy-server-amd6. Marking as confirmed. Thanks
** Changed in: lxc (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team,
** Changed in: sysvinit (Ubuntu)
Status: Triaged = Won't Fix
--
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/1098299
Title:
entropy pool should be seeded earlier in boot
Reviewed: https://review.openstack.org/28133
Committed:
http://github.com/openstack/keystone/commit/ff76a1b5cd3308cfb0ce936800364e27413ed946
Submitter: Jenkins
Branch:master
commit ff76a1b5cd3308cfb0ce936800364e27413ed946
Author: Jamie Lennox jlen...@redhat.com
Date: Fri May 3 14:04:09
** Description changed:
The saucy smoke test for lxc test_lxc_apparmor appears to be hung with
saucy installations of 20130521.
The following tests appear to have completed successfully.
- test: test_lxc_reboot
- test: test_lxc_simple
- test: test_lxc_api
-
- The steps
Blueprint changed by Andres Rodriguez:
Work items changed:
Work items for ubuntu-13.07:
Investigation zeromq support in havana: TODO
[gandelman-a] Check on status of heartbeating in AMQP for RabbitMQ HA: TODO
+ [andreserl] Investigate upgrade path for Corosync 2.0 based clusters: TODO
Blueprint changed by Adam Gandelman:
Whiteboard set to:
User stories:
John is maintaining some openstack juju charms. When he wants to push a
change affecting multiple charms, he does not want to duplicate his work
across bash and shell.
Mike wants to ensure deploying specific configuration of
Blueprint changed by Adam Gandelman:
Work items set to:
Work items:
openstack-dashboard python rewrite: TODO
glance python rewrite: TODO
cinder python rewrite: TODO
swift-storage python rewrite: TODO
nova-compute python rewrite: TODO
nova-cloud-controller python rewrite: TODO
Integrate current
Blueprint changed by Andres Rodriguez:
Work items changed:
Work items:
openstack-dashboard python rewrite: TODO
- glance python rewrite: TODO
+ [andreserl] glance python rewrite: TODO
cinder python rewrite: TODO
swift-storage python rewrite: TODO
nova-compute python rewrite: TODO
Public bug reported:
Can't run any command.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: puppet 3.1.1-1ubuntu1
ProcVersionSignature: User Name 3.9.0-2.7-generic 3.9.3
Uname: Linux 3.9.0-2-generic x86_64
ApportVersion: 2.10.1-0ubuntu1
Architecture: amd64
Date: Tue May 21 18:52:11 2013
$ puppet
/usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load
such file -- facter (LoadError)
from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
from /usr/lib/ruby/vendor_ruby/puppet.rb:4:in `top (required)'
from
Apparently the problem is that the default ruby is now 1.9. Running
/usr/bin/ruby1.8 /usr/bin/puppet seems to work around the problem.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
See also Bug #1093934 which seems to be a similar issue.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1182613
Title:
puppet completely broken on saucy
To manage notifications
*** This bug is a duplicate of bug 1181136 ***
https://bugs.launchpad.net/bugs/1181136
Do you mean c-start(c) in python bindings, with
lxc.loglevel = debug
lxc.logfile = /tmp/foo
in container config, fails? If so that's very interesting. If not,
then it matches my current expectation.
Public bug reported:
A recent change in the Folsom code has resulted in issues building new
instances with a non-zero root disk size. It is currently trying to
compare the flavor size to the size of the base image before the base
image is actually pulled down. As a result, builds fail with the
Blueprint changed by Andres Rodriguez:
Work items changed:
Work items:
- Install templates in /etc/maas: TODO
- maas-ipmi-autodetect and maas-signal should be shipped with MAAS: TODO
+ [andreserl] Install templates in /etc/maas: TODO
+ [andreserl] maas-ipmi-autodetect and maas-signal should be
This may be invalid for Ubuntu. I intended to open it in OpenStack/nova
originally.
--
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/1182624
Title:
Uncached instance builds fail with
Fix proposed to branch: stable/folsom
Review: https://review.openstack.org/29982
--
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/1182624
Title:
Uncached instance builds fail with
** Description changed:
A recent change in the Folsom code has resulted in issues building new
instances with a non-zero root disk size. It is currently trying to
compare the flavor size to the size of the base image before the base
image is actually pulled down. As a result, builds fail
2 comments:
a.) bug 997371 is now fixed, so you should be able to do: apt-add-repository
multiverse
b.) some relevant discussion at
https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2013-May/014503.html
** Description changed:
Backports are currently not enabled in the cloud-init
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: maas (Ubuntu)
Status: New = Confirmed
--
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/1153077
I think I'm seeing the same issue. I have a celeryd process that appears
to be stuck in a loop and a queue in the vhost /maas_workers named
c1d352af-8060-4bf4-b820-f468b22a97fb. One thing that stands out to me is
that the queue has 4 unacknowledged messages at all times. New ones seem
to come in
Public bug reported:
[Impact]
Raring is not enabled by default so images are not imported by maas. This
causes that someone has to manually enable raring and re-run
maas-import-pxe-files in order to be able deploy raring.
[Test Case]
1. Install maas
2. Run maas-import-pxe-files
3. Try to
** Changed in: maas (Ubuntu)
Importance: Undecided = Critical
** Changed in: maas
Importance: Undecided = High
** Changed in: maas (Ubuntu)
Importance: Critical = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in
** Branch linked: lp:~ubuntu-branches/ubuntu/precise/celery/precise-
proposed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to celery in Ubuntu.
https://bugs.launchpad.net/bugs/1177855
Title:
[SRU] Drop Build-Depends on
Blueprint changed by Antonio Rosales:
Work items changed:
Work items for ubuntu-13.04-month-6:
[jjo] Case Studies from webops (move to 2.0 messaging): TODO
[mthaddon] Case Studies from webops (move to 2.0 messaging): TODO
[timrchavez] Case Studies from PES (move to 2.0 messaging): TODO
Public bug reported:
[Impact]
If new ephemeral images are ready to be installed, maas-import-* scripts fail
because it cannot overwrite a symlink that has been created to support FPI.
This prevents maas from importing new ephemeral images.
[Test Case]
1. Install maas.
2. maas-import-pxe-files
** Changed in: maas (Ubuntu)
Status: New = Confirmed
** Changed in: maas (Ubuntu)
Importance: Undecided = Critical
** Changed in: maas (Ubuntu)
Importance: Critical = High
** Changed in: maas (Ubuntu Raring)
Importance: Undecided = High
--
You received this bug notification
** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete = New
--
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/1181777
Title:
kvm: freeze a guest with a NIC PCI passthrough
To
I've tested this and works as expected.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to celery in Ubuntu.
https://bugs.launchpad.net/bugs/1177855
Title:
[SRU]
** Tags removed: verification-failed
** Tags added: verification-done
--
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/1109283
Title:
[SRU] maas to Quantal and Precise
To manage
** Branch linked: lp:ubuntu/saucy-proposed/maas
--
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/1182646
Title:
maas-import-pxe-files fails to update ephemeral images
To manage
** Branch linked: lp:ubuntu/saucy-proposed/maas
--
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/1182642
Title:
Raring is not enabled by default
To manage notifications about this bug
** Branch linked: lp:ubuntu/saucy-proposed/maas
--
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/1171418
Title:
MAAS fails to power up machines when trying to install nodes
To manage
** Branch linked: lp:ubuntu/saucy-proposed/maas
--
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/1171988
Title:
MAAS fails to use virsh when managing virtual nodes
To manage
** Branch linked: lp:ubuntu/saucy-proposed/maas
--
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/1131418
Title:
Nodes don't go to ready, after commissioning they get a 500 error when
Hello Seth, or anyone else affected,
Accepted lxc into quantal-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/lxc/0.8.0~rc1-4ubuntu39.12.10.3 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Public bug reported:
This may be related to
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1010501
and
https://bugs.launchpad.net/ubuntu/lucid/+source/upstart/+bug/494141
After a reboot Samba printers are not visible until smbd is restarted.
I've tried adding and started cups to
** Changed in: maas (Ubuntu)
Status: Confirmed = 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/1182646
Title:
maas-import-pxe-files fails to update ephemeral
** Changed in: maas (Ubuntu)
Status: Confirmed = 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/1182642
Title:
Raring is not enabled by default
To manage
** Also affects: udev (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
- The saucy smoke test for lxc test_lxc_apparmor appears to be hung with
- saucy installations of 20130521.
+ The root of the problem as pertains to lxc is that debootstrap is
+ resulting in a udev
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: samba (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
** Tags added: raring
--
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/1182655
Title:
Samba printers are missing after reboot until smbd is restarted
To manage notifications about
This bug was fixed in the package maas - 1.3+bzr1461+dfsg-0ubuntu3
---
maas (1.3+bzr1461+dfsg-0ubuntu3) saucy; urgency=low
* debian/patches:
- 99-fix-ipmi-stat-lp1086160.patch: Drop. The following patch removes
the need for this fix. (LP: #1171988)
-
1 - 100 of 1373 matches
Mail list logo
