You have been subscribed to a public bug:
The generic Ubuntu *-server-cloudimg-amd64-disk1.img images available
here...
http://cloud-images.ubuntu.com/utopic/current/
... do not work on a SmartOS hypervisor: they try to detect a
datasource, but ultimately fail. It appears that this is
** Package changed: ubuntu = cloud-init (Ubuntu)
--
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/1398997
Title:
Ubuntu Cloud images do not work with SmartOS hypervisor
To manage
Public bug reported:
happens often
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: squid3 3.3.8-1ubuntu6.1
ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
Uname: Linux 3.13.0-40-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CrashCounter: 1
Date: Thu Dec
StacktraceTop:
?? ()
?? ()
?? ()
?? ()
?? ()
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/1399123
Title:
pinger crashed with SIGSEGV in malloc_consolidate()
To manage
Thank you for your report!
However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:
libc6 version
** Attachment added: Stacktrace.txt
https://bugs.launchpad.net/bugs/1399123/+attachment/4274000/+files/Stacktrace.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/1399123
Title:
** Attachment added: ThreadStacktrace.txt
https://bugs.launchpad.net/bugs/1399123/+attachment/4274001/+files/ThreadStacktrace.txt
** Changed in: squid3 (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
What about supporting the real thing, ie connected standby or
InstantGO function. Isn't it yet supported by linux kernel? Without
this and without real S3 state, linux won't be really useful on a SP3
I'm afraid.
--
You received this bug notification because you are a member of Ubuntu
Server
** Changed in: nova
Assignee: Kanchan Gupta (kanchan-gupta1) = (unassigned)
--
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/1313935
Title:
tenant is required for quota-update but
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Also affects: maas (Ubuntu Vivid)
Importance: Undecided
Status: New
** Also affects: maas (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: maas (Ubuntu Utopic)
Importance:
Public bug reported:
same issue with pax package
ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: sysstat 10.3.1-1
ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
Uname: Linux 3.16.0-25-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
AptOrdering:
sysstat: Install
sysstat:
specifically a missing home dir is now fatal following
https://github.com/GrahamDumpleton/mod_wsgi/commit/545354a80b9cc20d8b6916ca30542eab36c3b8bd
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to sysstat in Ubuntu.
https://bugs.launchpad.net/bugs/1399186
Title:
package sysstat 10.3.1-1 failed to install/upgrade: subprocess
installed
** Changed in: maas
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/1399016
Title:
MAAS failed to respond once libapache2-mod-wsgi upgrade on trusty
To
Public bug reported:
For a couple of weeks I have the following messages in
/var/log/exim4/mainlog.
The temporary workaround is to run the following commands: service
exim4 stop rm -r /var/spool/exim4/db service exim4 start.
After some hours the messages appear again. I haven't found a
We are currently working on updated maas packages that will be published
shortly to resolve this issue.
** Information type changed from Public to Public Security
** Changed in: maas (Ubuntu Precise)
Importance: Undecided = Critical
** Changed in: maas (Ubuntu Trusty)
Importance:
Any progress on this?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to net-snmp in Ubuntu.
https://bugs.launchpad.net/bugs/1394636
Title:
pass_persist fails when setting string
To manage notifications about this bug go to:
** Changed in: horizon (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: horizon (Ubuntu Trusty)
Status: Fix Committed = In Progress
** Description changed:
[Impact]
When multiple regions are configured within Horizon, the region selection
dropdown box in the top
** Description changed:
- When multiple regions are configured within Horizon, the region
- selection dropdown box in the top right corner of the horizon dashboard
- is not visible due to white text on white background.
+ [Impact]
+ When multiple regions are configured within Horizon, the region
** Also affects: horizon (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: horizon (Ubuntu)
Status: Invalid = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
** Tags added: cts
--
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/1399016
Title:
MAAS failed to respond once libapache2-mod-wsgi upgrade on trusty
To manage notifications about this
Public bug reported:
don't know! happened during update
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: openvswitch-datapath-dkms 1.4.6-0ubuntu1.12.04.4
ProcVersionSignature: Ubuntu 3.13.0-40.69~precise1-generic 3.13.11.10
Uname: Linux 3.13.0-40-generic i686
ApportVersion:
** Tags removed: need-duplicate-check
--
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/1399283
Title:
openvswitch-datapath-dkms 1.4.6-0ubuntu1.12.04.4: openvswitch kernel
** Branch linked: lp:ubuntu/vivid-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/1399016
Title:
MAAS failed to respond once libapache2-mod-wsgi upgrade on trusty
To
This bug was fixed in the package maas - 1.7.0+bzr3299-0ubuntu2
---
maas (1.7.0+bzr3299-0ubuntu2) vivid; urgency=medium
* debian/maas-common.postinst: Ensure that the maas user gets its home
directory created in /var/lib/maas. (LP: #1399016)
-- Andres Rodriguez
This bug was fixed in the package maas - 1.7.0+bzr3299-0ubuntu2
---
maas (1.7.0+bzr3299-0ubuntu2) vivid; urgency=medium
* debian/maas-common.postinst: Ensure that the maas user gets its home
directory created in /var/lib/maas. (LP: #1399016)
-- Andres Rodriguez
This bug was fixed in the package maas - 1.7.0+bzr3299-0ubuntu2
---
maas (1.7.0+bzr3299-0ubuntu2) vivid; urgency=medium
* debian/maas-common.postinst: Ensure that the maas user gets its home
directory created in /var/lib/maas. (LP: #1399016)
-- Andres Rodriguez
This bug was fixed in the package maas - 1.7.0+bzr3299-0ubuntu2
---
maas (1.7.0+bzr3299-0ubuntu2) vivid; urgency=medium
* debian/maas-common.postinst: Ensure that the maas user gets its home
directory created in /var/lib/maas. (LP: #1399016)
-- Andres Rodriguez
I've removed clam (running fine on two other partitions) but ppp and
dbus-x11 are still giving me grief. Also, every update brings up the
'restart your computer...' dialogue. I also can't delete clamav-
freshclam.
--
You received this bug notification because you are a member of Ubuntu
Server
Tried to reinstall ppp produced to following errors:
E: dbus: subprocess installed post-installation script returned error exit
status 1
E: ppp: subprocess installed post-installation script returned error exit
status 1
E: dbus-x11: dependency problems - leaving unconfigured
--
You received
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1349277
Title:
AArch64 emulation ignores SPSel=0 when taking
I have tried 1.7.0+bzr3299-0ubuntu2~trusty1 which works fine from a
fresh install of maas but fails to fix the issue when upgrading maas.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
Version verified was 2.0.8-0ubuntu3~14.04.1.
** Changed in: walinuxagent (Ubuntu Trusty)
Assignee: (unassigned) = Ben Howard (utlemming)
** Changed in: walinuxagent (Ubuntu Trusty)
Importance: Undecided = High
** Changed in: walinuxagent (Ubuntu Trusty)
Status: New = Fix
** Branch linked: lp:~andreserl/maas/packaging_maas_user_1.8
** Branch linked: lp:~andreserl/maas/packaging_maas_user_1.7
--
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/1399016
Title:
** Changed in: walinuxagent (Ubuntu Trusty)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to walinuxagent in Ubuntu.
https://bugs.launchpad.net/bugs/1396724
Title:
[SRU] false kernel
** Changed in: qemu (Ubuntu)
Assignee: (unassigned) = Chris J Arges (arges)
** Changed in: qemu (Ubuntu)
Status: New = In Progress
** Changed in: qemu (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team,
This bug was fixed in the package maas - 1.5.4+bzr2294-0ubuntu1.2
---
maas (1.5.4+bzr2294-0ubuntu1.2) trusty-security; urgency=medium
* Fix compatibility with mod-wsgi security update (LP: #1399016)
- debian/patches/home-directory.patch: specify a valid home directory
for
The attachment Proposed fix seems to be a patch. If it isn't, please
remove the patch flag from the attachment, remove the patch tag, and
if you are a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
~brian-murray, for
This bug was fixed in the package maas - 1.7.0~beta8+bzr3272-0ubuntu1.2
---
maas (1.7.0~beta8+bzr3272-0ubuntu1.2) utopic-security; urgency=medium
* Fix compatibility with mod-wsgi security update (LP: #1399016)
- debian/patches/home-directory.patch: specify a valid home
This bug was fixed in the package maas - 1.2+bzr1373+dfsg-
0ubuntu1~12.04.6
---
maas (1.2+bzr1373+dfsg-0ubuntu1~12.04.6) precise-security; urgency=medium
* Fix compatibility with mod-wsgi security update (LP: #1399016)
- debian/patches/home-directory.patch: specify a valid home
** Branch linked: lp:ubuntu/precise-security/maas
** Branch linked: lp:~ubuntu-branches/ubuntu/utopic/maas/utopic-security
--
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/1399016
Title:
Blueprint changed by Corey Bryant:
Work items changed:
Work items for ubuntu-15.01:
Setup openstack-charmers mailing list on lists.ubuntu.com: TODO
review use of logging throughout charm-helpers and charms, make it useful:
TODO
move CONFIG out of global scope and construct as required
Uploaded fixed package for Vivid:
https://launchpad.net/ubuntu/+source/qemu/2.1+dfsg-7ubuntu3
Please let me know if this fixes the issue.
** Changed in: qemu (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server
** 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 qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1370199
Title:
qemu upstart job should create /dev/kvm in a
I don't think the fix is adequate since it requires an extra manual
step, rather, I think the packaging should (if possible) trigger the
upstart job to stop and then start again... Otherwise, anyone upgrading
this (or installing it on top of a system with qemu-kvm already
installed in a
** Changed in: nova
Assignee: (unassigned) = Tony Breeds (o-tony)
--
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/832507
Title:
console.log grows indefinitely
To manage
** Changed in: qemu
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1349277
Title:
AArch64 emulation ignores SPSel=0 when taking (or returning from)
** Also affects: neutron/juno
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1384555
Title:
SQL error during alembic.migration when
** Also affects: neutron/juno
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1323729
Title:
Remove Open vSwitch and Linuxbridge plugins
** Changed in: neutron/juno
Status: New = Fix Committed
** Changed in: neutron/juno
Milestone: None = 2014.2.1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1384555
** Changed in: neutron/juno
Status: New = Fix Committed
** Changed in: neutron/juno
Milestone: None = 2014.2.1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1323729
** Also affects: nova/juno
Importance: Undecided
Status: New
** Changed in: nova/juno
Status: New = Fix Committed
** Changed in: nova/juno
Milestone: None = 2014.2.1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
*** This bug is a duplicate of bug 1374011 ***
https://bugs.launchpad.net/bugs/1374011
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1374011, so it is being marked as such. Please
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as Won't Fix.
** Changed in: squid-deb-proxy (Ubuntu Quantal)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as Won't Fix.
** Changed in: cloud-init (Ubuntu Quantal)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team,
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as Won't Fix.
** Changed in: maas (Ubuntu Quantal)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as Won't Fix.
** Changed in: network-manager (Ubuntu Quantal)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as Won't Fix.
** Changed in: bind9 (Ubuntu Quantal)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as Won't Fix.
--
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/1211447
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as Won't Fix.
** Changed in: libxml2 (Ubuntu Quantal)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as Won't Fix.
** Changed in: maas (Ubuntu Quantal)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as Won't Fix.
** Changed in: cluster-agents (Ubuntu Quantal)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team,
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as Won't Fix.
** Changed in: maas (Ubuntu Quantal)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as Won't Fix.
** Changed in: lxc (Ubuntu Quantal)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team,
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as Won't Fix.
** Changed in: maas (Ubuntu Quantal)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team,
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as Won't Fix.
** Changed in: tomcat7 (Ubuntu Quantal)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team,
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as Won't Fix.
** Changed in: nagios-plugins (Ubuntu Quantal)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as Won't Fix.
** Changed in: liblockfile (Ubuntu Quantal)
Status: Fix Committed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as Won't Fix.
** Changed in: liblockfile (Ubuntu Quantal)
Status: Fix Committed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as Won't Fix.
** Changed in: samba (Ubuntu Quantal)
Status: Fix Committed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as Won't Fix.
** Changed in: maas (Ubuntu Quantal)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as Won't Fix.
** Changed in: ca-certificates-java (Ubuntu Quantal)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as Won't Fix.
** Changed in: lxc (Ubuntu Quantal)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as Won't Fix.
** Changed in: php5 (Ubuntu Quantal)
Status: Fix Committed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team,
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as Won't Fix.
** Changed in: pm-utils (Ubuntu Quantal)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as Won't Fix.
** Changed in: mongodb (Ubuntu Raring)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team,
raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as Won't Fix.
** Changed in: nova (Ubuntu Raring)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as Won't Fix.
** Changed in: lxc (Ubuntu Raring)
Status: Fix Committed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team,
raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as Won't Fix.
** Changed in: lxc (Ubuntu Raring)
Status: Fix Committed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team,
raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as Won't Fix.
** Changed in: python-novaclient (Ubuntu Raring)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server
raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as Won't Fix.
** Changed in: lxc (Ubuntu Raring)
Status: Fix Committed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team,
raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as Won't Fix.
** Changed in: boost1.53 (Ubuntu Raring)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team,
raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as Won't Fix.
** Changed in: network-manager (Ubuntu Raring)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server
raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as Won't Fix.
** Changed in: cinder (Ubuntu Raring)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as Won't Fix.
** Changed in: puppet (Ubuntu Raring)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as Won't Fix.
** Changed in: ceilometer (Ubuntu Raring)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team,
raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as Won't Fix.
** Changed in: nagios-plugins (Ubuntu Raring)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server
raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as Won't Fix.
** Changed in: openvswitch (Ubuntu Raring)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team,
raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as Won't Fix.
** Changed in: libvirt (Ubuntu Raring)
Status: Fix Committed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team,
raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as Won't Fix.
** Changed in: beanstalkd (Ubuntu Raring)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team,
raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as Won't Fix.
** Changed in: ceilometer (Ubuntu Raring)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team,
raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as Won't Fix.
** Changed in: python-novaclient (Ubuntu Raring)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server
raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as Won't Fix.
** Changed in: network-manager (Ubuntu Raring)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server
raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as Won't Fix.
** Changed in: squid-deb-proxy (Ubuntu Raring)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server
raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as Won't Fix.
** Changed in: cloud-init (Ubuntu Raring)
Status: Fix Committed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server
raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as Won't Fix.
** Changed in: cloud-init (Ubuntu Raring)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team,
raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as Won't Fix.
** Changed in: vm-builder (Ubuntu Raring)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as Won't Fix.
** Changed in: nova (Ubuntu Raring)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as Won't Fix.
** Changed in: lxc (Ubuntu Raring)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as Won't Fix.
** Changed in: maas (Ubuntu Raring)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
1 - 100 of 195 matches
Mail list logo
