Blueprint changed by Clint Byrum:
Whiteboard changed:
- Status: ensemble and txzookeeper are in Oneiric NEW queue. txaws --
- waiting for response from developers on a release, or will package a bzr
- snapshot.
+ Status: ensemble and its dependencies are in oneiric. Every week on
+ Tuesday trunk i
** Changed in: libedit (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/816758
Title:
libedit lacks utf-8 support
To manage notifications about th
Tracking PPA-specific bugs in Nova with a "ppa" tag.
** Changed in: nova
Status: Invalid => Triaged
** Changed in: nova
Importance: Undecided => Medium
** Tags added: ppa
** Changed in: nova (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because y
** Branch linked: lp:~openstack-ubuntu-packagers/nova/ubuntu
--
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/758072
Title:
nova compute cannot run radvd
To manage notifications about t
** Changed in: nova (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: nova (Ubuntu)
Assignee: (unassigned) => Thierry Carrez (ttx)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpa
** Changed in: nova (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: nova (Ubuntu)
Assignee: (unassigned) => Thierry Carrez (ttx)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpa
** Branch linked: lp:~openstack-ubuntu-packagers/nova/ubuntu
--
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/798878
Title:
nova.conf should not be world-readable
To manage notification
** Changed in: lxc (Ubuntu)
Status: Incomplete => In Progress
--
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/753308
Title:
Restart containers on upgrade
To manage notifications
** Changed in: cloud-init
Importance: Undecided => Low
** Changed in: cloud-init
Status: New => Fix Committed
--
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/744019
Title
** Branch linked: lp:~smoser/ubuntu/oneiric/ifupdown/static-network-up
--
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/810044
Title:
cloud-init will have race conditions for cloud
Clint pointed me at lp:~clint-fewbar/ubuntu/oneiric/ifupdown/static-network-up/
a few weeks ago.
I made some changes to that to avoid the temp file needs and pushed those to
lp:~smoser/ubuntu/oneiric/ifupdown/static-network-up/
--
You received this bug notification because you are a member of
Thanks, Tamas.
The method of specifying autostart containers has changed in oneiric,
but it still has the same effect.
--
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/753308
Title:
Rest
Blueprint changed by James Page:
Whiteboard changed:
Work Items for oneiric-alpha-2:
- [james-page] File an ITP for octopussy in Debian: INPROGRESS
+ [james-page] File an ITP for octopussy in Debian: DONE
[gandelman-a] Write puppet module for central rsyslog server: INPROGRESS
[gandelman-a]
** Visibility changed to: Public
** This bug is no longer flagged as a security vulnerability
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/815504
Title:
glibc double free when usin
Public bug reported:
lxc-ls and lxc-cgroup are broken with multiple cgroups. There might be
more
** Affects: lxc (Ubuntu)
Importance: High
Assignee: Serge Hallyn (serge-hallyn)
Status: In Progress
** Changed in: lxc (Ubuntu)
Status: New => In Progress
** Changed in: l
Also lxc-netstat. The rest appear to be ok.
--
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/819319
Title:
more lxc scripts are broken with multiple cgroup mounts
To manage notification
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
lxc-unshare spits out an error on exit as well (though it does work).
--
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/819319
Title:
more lxc scripts are broken with multiple cgroup mount
Separating nova_sudoers into node-specific files sounds like a good idea
too (nova user is more exposed on API nodes, and API nodes actually do
not need a nova user that has the power of screwing up your network
configuration)
** Changed in: nova (Ubuntu)
Status: Confirmed => Triaged
** Ch
Ah, the lxc-unshare error on exit should simply be silenced - the cgroup
it is trying to delete is only the one which gets auto-created if the ns
cgroup is composed with the others.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in
@clint,
I think there is an issue with the branch you've been working on when
mappings are used.
I've fixed my branch to use the first token of /var/run/network/ifstate
rather than the second. Experimentation showed that the first field will be
the physical interface and the second would be
My branch (linked above) has a fix for the 'ifquery --list' issue
(manually parsing /etc/interfaces). I realize that is less than ideal.
--
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/b
actually lxc-cgroup is fine.
--
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/819319
Title:
more lxc scripts are broken with multiple cgroup mounts
To manage notifications about this bug
** Changed in: lxc (Ubuntu)
Status: In Progress => Fix Released
--
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/753308
Title:
Restart containers on upgrade
To manage notification
This bug was fixed in the package lxc - 0.7.4.2-3ubuntu5
---
lxc (0.7.4.2-3ubuntu5) oneiric; urgency=low
* debian/patches/0011-fix-lxc-ls.patch:
debian/patches/0012-fix-lxc-netstat.patch:
The cgroup mounts created by cgroup-bin do not show up in /etc/mtab.
lxc-ls and lxc
** Branch linked: lp:cloud-init
--
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/810044
Title:
cloud-init will have race conditions for cloud-config with multiple
network adapter
(lucid is not affected, it doesn't have the initscript)
--
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/753308
Title:
Restart containers on upgrade
To manage notifications about this bu
** Description changed:
+ ===
+ SRU Justification:
+ 1. Impact: running containers are stopped and re-started when the lxc
+ package is updated.
+ 2. How bug addressed: make dh_installinit with -r.
+ 3. Minimal patch:
+ === modified fi
** Changed in: upstart (Ubuntu Lucid)
Status: New => Confirmed
** Changed in: upstart (Ubuntu Maverick)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dhcp3 in Ubuntu.
https://bugs.launchpad.net/
Public bug reported:
The kvm package does not contain any PXE roms nor does it depend on or
suggest another package containing them.
Debian uses ipxe roms with kvm, and ipxe is already in Ubuntu so I don't
see any reason why there can't be package placing the roms where kvm
searches for them.
Pr
--
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/819486
Title:
cannot boot from network - roms missing
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu
This bug was fixed in the package ifupdown - 0.6.10ubuntu5
---
ifupdown (0.6.10ubuntu5) oneiric; urgency=low
[Scott Moser]
* debian/ifupdown.upstart.if-up: emit static-network-up when all auto
network interfaces are up. (LP: #810044)
[ Clint Byrum ]
* debian/rules: dh_ins
Thanks for taking the time to submit this bug.
Unfortunately the log files don't seem to give any indication of what is
actually going wrong. Can you tell us what you use to update the system?
is qemu-kvm working for you?
** Changed in: qemu-kvm (Ubuntu)
Status: New => Incomplete
--
Yo
Blueprint changed by Clint Byrum:
Whiteboard changed:
Status: spec drafting, work items are still in flux
Work Items:
[cjwatson] turn off quiet for server: DONE
[jamesodhunt] allow upstart visualization tool to filter out jobs/events that
aren't in existence: POSTPONED
- [clint-fewbar]
** Branch linked: lp:ubuntu/ifupdown
--
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/810044
Title:
cloud-init will have race conditions for cloud-config with multiple
network ad
Public bug reported:
Right now, cloud-init.py has:
# parse the user data (ec2-run-userdata.py)
try:
cloud.sem_and_run("consume_userdata", "once-per-instance",
cloud.consume_userdata,[],False)
except:
warn("consuming user data failed!\n")
raise
What
--
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/819507
Title:
consume_userdata is only called once per instance
To manage notifications about this bug go to:
https://bugs.launchpa
So, there is some progress on this bug. A new event called 'static-
network-up' was added to oneiric today, which will only be emitted once
all 'auto' interfaces from /etc/network/interfaces are up.
The next step is to delay /etc/init/rc-sysinit.conf until this event is
emitted, and then also prov
Reassigning to me, as I have been working on the fix.
** Changed in: upstart (Ubuntu)
Status: Triaged => In Progress
** Changed in: upstart (Ubuntu)
Milestone: None => ubuntu-11.10-beta-1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is s
milestoned to beta 1 to make sure this happens before beta.
** Summary changed:
- dhcp3-server and other init.d controled services launch before upstart brings
all interface, thus failing to start
+ init.d controled services launch before all interfaces are up, thus failing
to start
** Summary
A MIR for a nut-client package (and some others) is underway:
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/816414
better late than never...
cheers,
Arnaud
** Changed in: nut (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of
This bug was fixed in the package cloud-init - 0.6.1-0ubuntu13
---
cloud-init (0.6.1-0ubuntu13) oneiric; urgency=low
* do not install 92-uec-upgrade-available as a motd hook. This file was
installed but did not do anything since updates-check was removed.
* support multiple s
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu)
Status: New => Triaged
** Changed in: cloud-init
Importance: Undecided => Medium
** Changed in: cloud-init
Thanks for submitting this bug and helping to make Ubuntu better.
Note that pxe is enabled by the roms in the kvm-pxe package.
However, I agree that now that ipxe is packaged, its roms should be
symlinked into /usr/share/qemu/.
That probably should be done, as it is in etherboot, in the
ipxe pac
Public bug reported:
when executing mysqldumpslow without arguments, the response I get is:
Can't find '/var/lib/mysql/*-slow.log'
when it should look for the slow log file at /var/log/mysql/mysql-slow.log
I understand that the tool should be executed with argument pointing to the
correct log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.1 in Ubuntu.
https://bugs.launchpad.net/bugs/819535
Title:
mysqldumpslow looking for slow.log file on an incorrect directory
To manage notifications about this bug go to:
https:
You have been subscribed to a public bug:
Software Center keeps reporting the software index keeps needing to be
rebuilt.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: software-center 4.0.4
ProcVersionSignature: Ubuntu 2.6.38-10.46-server 2.6.38.7
Uname: Linux 2.6.38-10-server x86_64
Arch
** Package changed: software-center (Ubuntu) => mysql-5.1 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.1 in Ubuntu.
https://bugs.launchpad.net/bugs/810731
Title:
MySQL Server installation crashed, now unable to re
Blueprint changed by Clint Byrum:
Whiteboard changed:
Work Items:
[bcsaller] Cloud Camp - May 26, 2011 in San Francisco, CA, USA {1}: DONE
DevOps Day Australia (Taking talk submissions now) - July 22-23rd in
Melbourne, Australia{2}: POSTPONED
HotCloud (Poster submissions are due by Monday
Hello Guys,
I wanned to share my workarroud on this issue, Im using debian squeeze
as OS for a couple of virtualization hosts, each one of them holding a
number of vm's.
What I need is that when shuting down my virtualization host (from cli,
by cron, by ups low batt or by pressing the power butto
Here's my /etc/init.d/libvirt-bin file
** Attachment added: "libvirt-bin"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/350936/+attachment/2248342/+files/libvirt-bin
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in U
Just for reference, the code added here for ifupdown is expected to be
used to fix bug 580319 .
--
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/810044
Title:
cloud-init will have
Just for reference, there was code committed under bug 810044 to
ifupdown that is expected to be used to fix this issue.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dhcp3 in Ubuntu.
https://bugs.launchpad.net/bugs/580319
Title:
i
** Changed in: cloud-init
Importance: Undecided => Medium
** Changed in: cloud-init
Status: Triaged => Fix Committed
--
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/810044
[Expired for bind9 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: bind9 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net
[Expired for mysql-dfsg-5.1 (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: mysql-dfsg-5.1 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.1 in Ubuntu.
[Expired for bacula (Ubuntu) because there has been no activity for 60
days.]
** Changed in: bacula (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bacula in Ubuntu.
https://bugs.launchpad.
[Expired for mysql-dfsg-5.1 (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: mysql-dfsg-5.1 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.1 in Ubuntu.
Public bug reported:
The following recipe appears to reliably nuke a lxc i386 lucid container
running on a oneiric amd64 host:
lxc-start -n
(login)
sudo poweroff -n
- hangs
in another terminal
sudo lxc-stop -n
then
sudo lxc-start -n
shows
sudo lxc-start -n lucid-test-lp
init: plymouth-spla
Further investigation shows that just:
logging into the new container
installing some packages (see https://dev.launchpad.net/Running/LXC)
and calling lxc-stop from another terminal
will cause this.
Am progressing with shorter and shorter tests
** Summary changed:
- container start failure afte
start, login, log out, lxc-stop from another terminal
-> the broken situation.
--
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/819621
Title:
lucid container start failure after calling
And confirmed its still nuked after a reboot.
--
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/819621
Title:
lucid container start failure after calling lxc-stop (fails across
reboots)
So now I made a clean container; copied it to (sudo cp -a ) to a temp
dir, ran the original, and now have a diff of the changes. I've not yet
tested to see if reverting them fixes it.?field.comment=So now I made a
clean container; copied it to (sudo cp -a ) to a temp dir, ran the
original, and now
ps fax for the broken container starting up;
4134 pts/0S+ 0:00 | \_ sudo lxc-start -n lucid-test-lp
4135 pts/0S+ 0:00 | \_ lxc-start -n lucid-test-lp
4150 ?Ss 0:00 | \_ /sbin/init
4192 ?S 0:00 |
Pre breakage:
4534 pts/0S+ 0:00 | \_ sudo lxc-start -n lucid-test-lp
4535 pts/0S+ 0:00 | \_ lxc-start -n lucid-test-lp
4546 ?Ss 0:00 | \_ /sbin/init
4593 ?S 0:00 | \_ upstart-udev-bridg
4936 pts/4 Ss+ 0:00 | \_ /sbin/getty -8 38400 tty4
4937 pts/2 Ss+ 0:00 | \_ /sbin/getty -8 38400 tty2
4939 pts/3 Ss+ 0:00 | \_ /sbin/getty -8 38400 tty3
4945 ? S 0:00 | \_ /bin/sh /etc/init.d/ondemand background
4957 ? S 0:00 | | \_ sleep 60
4952 pts/1 Ss+ 0:00 | \_ /sbin/getty -8 38400 tty1
(Meta: does ondemand make any sense for containers anyhow?)
--
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/819621
Title:
lucid container start failure after calling lxc-stop (fails acro
69 matches
Mail list logo