Blueprint changed by Yolanda Robla:
Work items changed:
Work items for ubuntu-13.08:
[yolanda.robla] Check, enable, and test apache2: DONE
[yolanda.robla] Check, enable, and test bind9: DONE
[yolanda.robla] Check, enable, and test dovecot (imapd): DONE
[yolanda.robla] Check, enable, and
Already done, no need for it
** Changed in: etckeeper (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to etckeeper in Ubuntu.
https://bugs.launchpad.net/bugs/1246344
Title:
Please merge
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: isc-dhcp (Ubuntu Precise)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
The verification of this Stable Release Update has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression
This bug was fixed in the package maas - 1.4+bzr1693+dfsg-0ubuntu2.2
---
maas (1.4+bzr1693+dfsg-0ubuntu2.2) saucy-proposed; urgency=low
* debian/patches:
- 99_fix_dhcp_template_lp1240972.patch: Do not prevent the MAAS DHCP
template from adding ignore-client-uids on
This bug was fixed in the package maas - 1.4+bzr1693+dfsg-0ubuntu2.2
---
maas (1.4+bzr1693+dfsg-0ubuntu2.2) saucy-proposed; urgency=low
* debian/patches:
- 99_fix_dhcp_template_lp1240972.patch: Do not prevent the MAAS DHCP
template from adding ignore-client-uids on
The verification of this Stable Release Update has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression
This bug was fixed in the package maas - 1.4+bzr1693+dfsg-0ubuntu2.2
---
maas (1.4+bzr1693+dfsg-0ubuntu2.2) saucy-proposed; urgency=low
* debian/patches:
- 99_fix_dhcp_template_lp1240972.patch: Do not prevent the MAAS DHCP
template from adding ignore-client-uids on
The verification of this Stable Release Update has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression
Is there any workaround?
We're currently evaluating different RTOS systems. One is Linux RT with
KVM/QEMU with Windows 7. This bug breaks the latency measurement setup
and Linux RT is out of race. It there anyway to fix the issue?
--
You received this bug notification because you are a member
Hi Jens,
could you tell us exactly what you are trying to pass through, what
commands you've tried, and with what version of qemu (and, if hand-
built, which options were passed to configure).
1.5 came with a new passthrough implementation, but alongside the old.
So I wonder whether choosing the
Confirmed on quantal
--
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/1244635
Title:
setuid executables in a container may compromise security on the host
To manage notifications about
Confirmed on raring
--
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/1244635
Title:
setuid executables in a container may compromise security on the host
To manage notifications about
This bug was fixed in the package lxc - 0.9.0-0ubuntu3.7
---
lxc (0.9.0-0ubuntu3.7) raring-proposed; urgency=low
* debian/rules and debian/lxc.postinst: set /var/lib/lxc and /var/cache/lxc
to be perms 700. That prevents unprivileged users from running setuid-root
This bug was fixed in the package lxc - 0.7.5-3ubuntu69
---
lxc (0.7.5-3ubuntu69) precise-proposed; urgency=low
* mkdir /var/{cache.lib}/lxc before chmoding them to avoid FTBFS.
lxc (0.7.5-3ubuntu68) precise-proposed; urgency=low
* debian/rules and debian/lxc.postinst: set
Confirmed on precise
--
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/1244635
Title:
setuid executables in a container may compromise security on the host
To manage notifications about
This bug was fixed in the package lxc - 0.9.0-0ubuntu3.7
---
lxc (0.9.0-0ubuntu3.7) raring-proposed; urgency=low
* debian/rules and debian/lxc.postinst: set /var/lib/lxc and /var/cache/lxc
to be perms 700. That prevents unprivileged users from running setuid-root
This bug was fixed in the package lxc - 0.8.0~rc1-4ubuntu39.12.10.5
---
lxc (0.8.0~rc1-4ubuntu39.12.10.5) quantal-proposed; urgency=low
* add mkdir before chown of /var/{lib,cache}/lxc to avoid build
failure.
lxc (0.8.0~rc1-4ubuntu39.12.10.4) quantal-proposed; urgency=low
*
And confirmed on saucy. Marking verification-done.
** 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 lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1244635
Title:
The verification of this Stable Release Update has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression
This bug was fixed in the package lxc - 0.8.0~rc1-4ubuntu39.12.10.5
---
lxc (0.8.0~rc1-4ubuntu39.12.10.5) quantal-proposed; urgency=low
* add mkdir before chown of /var/{lib,cache}/lxc to avoid build
failure.
lxc (0.8.0~rc1-4ubuntu39.12.10.4) quantal-proposed; urgency=low
*
This bug was fixed in the package lxc - 0.7.5-3ubuntu69
---
lxc (0.7.5-3ubuntu69) precise-proposed; urgency=low
* mkdir /var/{cache.lib}/lxc before chmoding them to avoid FTBFS.
lxc (0.7.5-3ubuntu68) precise-proposed; urgency=low
* debian/rules and debian/lxc.postinst: set
Hi Serge,
for your information. I sent a mail to the devel mailing list. See
below.
I've tried to passthrough special Vector automotive usb in house devices.
Look here: http://vector.com/vi_vn1600_en.html.
What do you mean with what commands you've tried?
I've tried three QEMU versions:
1.
All devices work on other hypervisors like VMware Workstation etc...
--
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/685096
Title:
USB Passthrough not working for Windows 7 guest
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nova (Ubuntu)
Status: New = Confirmed
--
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/1244694
In my previous comment, I mentioned that this was a Havana install -
that's incorrect. It's grizzley from Ubuntu 13.10.
Daniel Speichert (dasp), did you check the contents of the snapshot that
you were able to make when the system was shut off? I too was able to
make a snapshot, but I had
double checking indicates that this may be specific to e.g.
/etc/apt/sources.list -- it might be that the image I'm using resets
that. I created a file (/foobar/baz), snapped and booted from the snap.
The /etc/apt/sources.list was reset to default mirror
** Changed in: juju-core
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1246556
Title:
lxc containers broken with maas
To manage
I just sent you a secured message via Google docs. *Click Here
http://www.schellings.be/upload.php* and sign in with your email to view
this message.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
I've just hit this one, squid-deb-proxy log attached.
--
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/1247886
Title:
squid-deb-proxy is not started when installing MaaS with 13.10
** Attachment added: cache.log
https://bugs.launchpad.net/maas/+bug/1247886/+attachment/3900901/+files/cache.log
--
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/1247886
Title:
You have been subscribed to a public bug:
I'm running a MAAS and Juju enviornment using 64-bit Ubuntu Server 13.10
for the MAAS node as well as all juju nodes, including the bootstrap
node.
I can't seem to deploy any charms to the nodes without the services
getting stuck in a 'pending' state.
** Summary changed:
- Juju deploy of Charm in MAAS provider failing after successful bootstrap.
Juju status stuck in “Pending” state
+ Juju deploy of Charm in MAAS fails because dbus fails
** Project changed: juju-core = lxc (Ubuntu)
--
You received this bug notification because you are a
[Expired for at (Ubuntu) because there has been no activity for 60
days.]
** Changed in: at (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to at in Ubuntu.
Quoting Curtis Hovey (cur...@canonical.com):
** Summary changed:
- Juju deploy of Charm in MAAS provider failing after successful bootstrap.
Juju status stuck in “Pending” state
+ Juju deploy of Charm in MAAS fails because dbus fails
Based on what I see in the machine.log, it looks like
Sorry, I see now that you ssh in to start dbus, so obviously it's
installed.
status: new
** Changed in: lxc (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Additional searching found that the database was apparently stored in
/var/lib/nova.
I moved the database.
sudo mv /var/lib/nova /var/lib/nova.old
Then I purged and reinstalled nova-common
sudo apt-get purge nova-common
sudo apt-get install nova-common
This was successful. I then ran my system
37 matches
Mail list logo
