I am re-opening this due to the closure being based on an assumption
that the original report was accurate.
pt-bz refers to Portuguese reading/writing citizens of Belize (NOT
Brazil). Which is a valid ISO code missing from the squid-langpack
package.
Any information on whether Belize Portuguese d
@ Serge
I write down the process I have tried to solve this issue...
First the nova-compute.log show an ERROR as follow...
2013-05-21 16:19:11.230 ERROR nova.compute.manager [req-0e30e53b-
8d93-4a0b-b378-672a02d6eb417c0d5d8e458f4580972e14af22e8a6ca
8d6292b82686470bb5a46d3c1a565c03] [instance:
71
Public bug reported:
Imported from Debian bug http://bugs.debian.org/708692:
Source: dnsjava
Version: 2.1.4-0.1
Severity: serious
Justification: fails to build from source
dnsjava requires internet connectivity to build an OSGi bundle.
Package builds must not rely on external network connectivit
libsasl2-modules 2.1.25.dfsg1-6
from commit through svn+ssh
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/827151
Title:
Annoying log message "DIGEST-MD5 common mech free"
To m
** Changed in: nova
Status: New => Confirmed
** Changed in: nova
Importance: Undecided => Critical
--
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 ins
** 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/1161338
Title:
python-nova should depend on ebtables
To manage notifications about this bug go to:
https://bu
*** This bug is a duplicate of bug 1051982 ***
https://bugs.launchpad.net/bugs/1051982
We cannot "look at the other bug report" because it is private. Clicking
on your link to the bug gives us "Bug 1051982 cannot be found". bug
#1051982 is private.
--
You received this bug notification becau
*** This bug is a duplicate of bug 1051982 ***
https://bugs.launchpad.net/bugs/1051982
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: php5 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
observed when upgrading from cinder-api 2012.2.3-0ubuntu2~cloud0 to
1:2013.1-0ubuntu2~cloud0.
The required auth_token middleware has moved from python-keystone to
python-keystoneclient. Cinder's api-paste.ini has been updated to
reflect this:
[filter:authtoken]
paste.filter
Urgh this is nasty.
We have plans to completely re-write the importer script in Python in
the near future. That would be an ideal time to address any of these
problems, so if you can firm up a plan and document it here, we'll
implement it.
Please don't write any more shell, or changes to shell.
Aimon- Please use the grizzly pocket of the Ubuntu Cloud Archive instead
of the trunk PPAs. The PPAs are unsupported. If this is a valid bug
that warrants an update, it will be published to Ubuntu and the Cloud
Archive, not the PPAs. I'm having trouble reproducing this with what we
have packaged
Noticed today as well on 13.04 (64-bit).
The "reload-smbd" upstart script already exists to handle this per the
prior bugs, but apparently something's still racing.
-rw-r--r-- 1 root root 213 Nov 23 08:55 /etc/init/reload-smbd.conf
smbd.log appears to suggest that the reload isn't happening (boo
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)
- 99-fix-ipmi-lp1171
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)
- 99-fix-ipmi-lp1171
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)
- 99-fix-ipmi-lp1171
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)
- 99-fix-ipmi-lp1171
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)
- 99-fix-ipmi-lp1171
** 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
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.
https://bugs.launchpad.net/bugs/118265
** 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
** 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 notific
** 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 ima
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 /etc/ini
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
https:
** 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
r
** 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 notificatio
** 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 no
** 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 g
** 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 notifica
** 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 notific
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] Dro
** 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 m
** 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
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
3
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): TO
** 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 python-sphinxc
** 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 i
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 deplo
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 an
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
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 templ
** 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 w
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 non-ze
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 non
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 s
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
fol
*** 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.
Th
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 abou
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.
https://bugs.launchpad.net/bugs/11
$ 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 `'
from /usr/lib/ruby/1.9.1/rubygems/custom
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
Ec2
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
nova-
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 ope
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 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
W
** 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 to
Reviewed: https://review.openstack.org/28133
Committed:
http://github.com/openstack/keystone/commit/ff76a1b5cd3308cfb0ce936800364e27413ed946
Submitter: Jenkins
Branch:master
commit ff76a1b5cd3308cfb0ce936800364e27413ed946
Author: Jamie Lennox
Date: Fri May 3 14:04:09 2013 +1000
Imple
** 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 proc
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, whi
** 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.
https://b
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
Serv
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
n
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
https://w
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 "%rsi"ok
Signal : 11
Uname : Linux 3.8.0-22-generic x86_64
I'll leave the
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
ProcVersionSignatur
** 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 not
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 at
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
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:
https://bugs.launch
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 /var/lib/maas/tftp/amd64/g
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
*** 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 in
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 bug
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 bug
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 bug
*** 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
*** 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 a
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 becau
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.
https://b
*** 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, which
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 empt
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
Serve
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 difficul
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 n
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
@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 manage
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 thin
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
downlo
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
/var/lib/maas/tftp/amd64/generic/raring/commission
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
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
+ [s
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
Architecture:
** 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 co
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 membe
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 Open
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) Sun, 24 Mar 2013 01:18:51
+0100
python-gevent (0.13.7-3
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
1 - 100 of 116 matches
Mail list logo
