I can confirm that the patch from 1362766 does fix this issue. I will
propose the SRU on bug 1362766 so please see that bug for progress.
** Changed in: python-glanceclient (Ubuntu)
Assignee: (unassigned) => Edward Hope-Morley (hopem)
** Changed in: python-glanceclient (Ubu
I can confirm that the patch from 1362766 does fix this issue. I will
propose the SRU on bug 1362766 so please see that bug for progress.
** Changed in: python-glanceclient (Ubuntu)
Assignee: (unassigned) => Edward Hope-Morley (hopem)
** Changed in: python-glanceclient (Ubu
actually i'll propose SRU to bug 1347150 since it is the original bug
raised for the issue.
--
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/1508428
Title:
nova image-list failing with
actually i'll propose SRU to bug 1347150 since it is the original bug
raised for the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1508428
Title:
nova image-list failing with SSL enabled on
This bug is actually in python-glanceclient and should fixed by
https://bugs.launchpad.net/python-glanceclient/+bug/1362766 which landed
in 0.14.2 (Juno UCA has 0.14.0)
** Also affects: python-glanceclient (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nova (Ubuntu)
This bug is actually in python-glanceclient and should fixed by
https://bugs.launchpad.net/python-glanceclient/+bug/1362766 which landed
in 0.14.2 (Juno UCA has 0.14.0)
** Also affects: python-glanceclient (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nova (Ubuntu)
I think you are actually hitting a bug in the Juno version of
glaneclient https://bugs.launchpad.net/python-glanceclient/+bug/1442664.
I need to double check but if correct we should backport that patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I think you are actually hitting a bug in the Juno version of
glaneclient https://bugs.launchpad.net/python-glanceclient/+bug/1442664.
I need to double check but if correct we should backport that patch.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Tags added: ubuntu-sponsors
** Patch added: "lp1506257.debdiff"
https://bugs.launchpad.net/ubuntu/trusty/+source/nova/+bug/1506257/+attachment/4496906/+files/lp1506257.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Tags added: ubuntu-sponsors
** Patch added: "lp1506257.debdiff"
https://bugs.launchpad.net/ubuntu/trusty/+source/nova/+bug/1506257/+attachment/4496906/+files/lp1506257.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
+ [Impact]
+
+ Resolves issue described below by making rpc client tolerant of incompatible
+ remote agent for reserve_block_device_name() calls which can occur during
+ upgrades if compute services are upgraded after clients e.g. nova-api. The
+ proposed fix will
** Description changed:
+ [Impact]
+
+ Resolves issue described below by making rpc client tolerant of incompatible
+ remote agent for reserve_block_device_name() calls which can occur during
+ upgrades if compute services are upgraded after clients e.g. nova-api. The
+ proposed fix will
** Changed in: nova (Ubuntu Trusty)
Status: New => In Progress
** Changed in: nova (Ubuntu Trusty)
Importance: Undecided => High
** Changed in: nova (Ubuntu Trusty)
Assignee: (unassigned) => Edward Hope-Morley (hopem)
** Changed in: nova (Ubuntu)
Status: In Progre
** Changed in: nova (Ubuntu Trusty)
Status: New => In Progress
** Changed in: nova (Ubuntu Trusty)
Importance: Undecided => High
** Changed in: nova (Ubuntu Trusty)
Assignee: (unassigned) => Edward Hope-Morley (hopem)
** Changed in: nova (Ubuntu)
Status: In Progre
ntu)
Importance: High
Assignee: Edward Hope-Morley (hopem)
Status: In Progress
** Changed in: nova (Ubuntu)
Status: New => In Progress
** Changed in: nova (Ubuntu)
Importance: Undecided => High
** Changed in: nova (Ubuntu)
Assignee: (unassigned) => Edward
ntu)
Importance: High
Assignee: Edward Hope-Morley (hopem)
Status: In Progress
** Changed in: nova (Ubuntu)
Status: New => In Progress
** Changed in: nova (Ubuntu)
Importance: Undecided => High
** Changed in: nova (Ubuntu)
Assignee: (unassigned) => Edward
** Branch linked: lp:~hopem/nova/icehouse-lp1506257
--
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/1506257
Title:
rpcapi version mismatch possible on upgrade
To manage notifications
** Branch linked: lp:~hopem/nova/icehouse-lp1506257
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1506257
Title:
rpcapi version mismatch possible on upgrade
To manage notifications about this bug
** Also affects: percona-cluster (Juju Charms Collection)
Importance: Undecided
Status: New
** Changed in: percona-cluster (Juju Charms Collection)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
a-cloud-controller (Juju Charms Collection)
Importance: Undecided => High
** Changed in: swift-proxy (Juju Charms Collection)
Importance: Undecided => High
** Changed in: ceilometer (Juju Charms Collection)
Assignee: (unassigned) => Edward Hope-Morley (hopem)
** Change
a-cloud-controller (Juju Charms Collection)
Importance: Undecided => High
** Changed in: swift-proxy (Juju Charms Collection)
Importance: Undecided => High
** Changed in: ceilometer (Juju Charms Collection)
Assignee: (unassigned) => Edward Hope-Morley (hopem)
** Change
Public bug reported:
As of the Openstack Libery release, the Ubuntu Cloud Archive will carry
haproxy (starting with 1.5.*) so we will no longer need to install
haproxy from trusty-backports i.e. each charm currently has:
# NOTE(xianghui): Need to install haproxy(1.5.3) from trusty-backports
Public bug reported:
As of the Openstack Libery release, the Ubuntu Cloud Archive will carry
haproxy (starting with 1.5.*) so we will no longer need to install
haproxy from trusty-backports i.e. each charm currently has:
# NOTE(xianghui): Need to install haproxy(1.5.3) from trusty-backports
** Also affects: cloud-archive
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1430042
Title:
Virtual Machine could not be evacuated because virtual
@lmihaiescu Hi, this patch is already in stable/juno and as such will be
included in the next point release of Juno (2014.2.4) but is not yet
targeted for SRU into Juno.
** Changed in: nova (Ubuntu Trusty)
Assignee: Edward Hope-Morley (hopem) => (unassigned)
--
You received this
@lmihaiescu Hi, this patch is already in stable/juno and as such will be
included in the next point release of Juno (2014.2.4) but is not yet
targeted for SRU into Juno.
** Changed in: nova (Ubuntu Trusty)
Assignee: Edward Hope-Morley (hopem) => (unassigned)
--
You received this
Deployed Trusty Icehouse with this nova version, ran the test described
above and lgtm +1.
** 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 nova in Ubuntu.
Deployed Trusty Icehouse with this nova version, ran the test described
above and lgtm +1.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
There is a new version of Tidy (5.0.0) which has been released and which
is largely backwards compatible with the 2009 Tidy that ships right now.
See https://github.com/htacg/tidy-html5 for the source repository, and
this open issue
https://github.com/htacg/tidy-html5/issues/252
for the
This bug is fixed in tidy-html5 v5.0.0, as noted here
https://github.com/htacg/tidy-html5/issues/256
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/589574
Title:
libtidy creates invalid tags
To
** Changed in: nova (Ubuntu)
Status: New => In Progress
** Changed in: nova (Ubuntu)
Assignee: (unassigned) => Edward Hope-Morley (hopem)
** Changed in: nova (Ubuntu)
Importance: Undecided => High
** Changed in: nova (Ubuntu Trusty)
Assignee: (unassigned) =>
** Changed in: nova (Ubuntu)
Status: New => In Progress
** Changed in: nova (Ubuntu)
Assignee: (unassigned) => Edward Hope-Morley (hopem)
** Changed in: nova (Ubuntu)
Importance: Undecided => High
** Changed in: nova (Ubuntu Trusty)
Assignee: (unassigned) =>
** Changed in: nova (Ubuntu)
Status: In Progress => Fix Released
** Description changed:
[Impact]
- * Ensure attching already attached volume to second instance does not
-interfere with attached instance volume record.
+ * Ensure attching already attached volume to second
** Description changed:
+ [Impact]
+
+ * Ensure attching already attached volume to second instance does not
+interfere with attached instance volume record.
+
+ [Test Case]
+
+ * Create cinder volume vol1 and two instances vm1 and vm2
+
+ * Attach vol1 to vm1 and check that attach was
** Description changed:
+ [Impact]
+
+ * Ensure attching already attached volume to second instance does not
+interfere with attached instance volume record.
+
+ [Test Case]
+
+ * Create cinder volume vol1 and two instances vm1 and vm2
+
+ * Attach vol1 to vm1 and check that attach was
** Changed in: nova (Ubuntu)
Status: In Progress => Fix Released
** Description changed:
[Impact]
- * Ensure attching already attached volume to second instance does not
-interfere with attached instance volume record.
+ * Ensure attching already attached volume to second
Public bug reported:
The man page for the adduser utility clearly states the exit code
behavior to be expected as:
EXIT VALUES
0 The user exists as specified. This can have 2 causes: The user
was created by adduser or the user was already present on the system before
adduser was
The patch from comment #43 seems to have fixed. Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1292290
Title:
[SRU] Window manager keybindings don't work after reboot
To manage
I just accepted an auto-update on my Ubuntu 14.04 system and all
application shortcuts stopped working. I can't make them work again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1224732
Title:
Anyone found a work around for this bug on 14.04.2 LTS using repo deb
http://ubuntu-cloud.archive.canonical.com/ubuntu trusty-updates/kilo
main. I just upgraded from juno to kilo and this bug is still an
issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Anyone found a work around for this bug on 14.04.2 LTS using repo deb
http://ubuntu-cloud.archive.canonical.com/ubuntu trusty-updates/kilo
main. I just upgraded from juno to kilo and this bug is still an
issue.
--
You received this bug notification because you are a member of Ubuntu
Server
Sam, Openstack Kilo is tracked under Ubuntu Vivid so once
1:2015.1.1-0ubuntu2 has been verified and lands in vivid-updates it will
then be synced into the Kilo Cloud Archive.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in
Sam, Openstack Kilo is tracked under Ubuntu Vivid so once
1:2015.1.1-0ubuntu2 has been verified and lands in vivid-updates it will
then be synced into the Kilo Cloud Archive.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
If you are hitting this issues and you are using rabbitmq SSL with the
latest Trusty/Icehouse oslo.messaging then you will hitting the bug
from:
https://bugs.launchpad.net/ubuntu/+source/python-amqp/+bug/1472712
For which there is a fix in trusty-proposed and it will shortly land in
I have run an ssl only icehouse deployment with this and can also verify
that it does fix the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472712
Title:
[SRU] Using SSL with rabbitmq
Michael, please see comments in bug 1435283 which iiuc is the same issue
(so essentially a duplicate). Comment #11 explains one possible solution
to the problem. Essentially what we want is for Juju to pick a
port/interface on unit start and remember it (e.g. by uuid) so that if
extra
Michael, please see comments in bug 1435283 which iiuc is the same issue
(so essentially a duplicate). Comment #11 explains one possible solution
to the problem. Essentially what we want is for Juju to pick a
port/interface on unit start and remember it (e.g. by uuid) so that if
extra
Public bug reported:
missing
QT_IM_MODULE=gcin
in /usr/share/im-config/data/26_gcin.rc
QT5 needs this.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: im-config 0.29-1ubuntu2 [modified: usr/share/im-config/data/26_gcin.rc]
ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
Finally got to the bottom of this. The issue lies in python-amqp rather
than python-oslo.messaging. The current trusty version of python-amqp
(1.3.3) has a bug that is fixed in 1.4.4 (see
http://amqp.readthedocs.org/en/latest/changelog.html#version-1-4-4). I
tried backporting the Juno/Utopic
Finally got to the bottom of this. The issue lies in python-amqp rather
than python-oslo.messaging. The current trusty version of python-amqp
(1.3.3) has a bug that is fixed in 1.4.4 (see
http://amqp.readthedocs.org/en/latest/changelog.html#version-1-4-4). I
tried backporting the Juno/Utopic
** Description changed:
+ [Impact]
+
+ Current oslo.messaging and python-amqp results in repeated connection
+ timeouts in the amqp transport layer (SSLError) and thus excessive
+ reconnect attempts. This is a known issues that was fixed in python-amqp
+ 1.4.4.
+
+ [Test Case]
+
+ Deploy
I suspect this is caused by the same issue as bug 1472712.
** Package changed: oslo.messaging (Ubuntu) = python-oslo.messaging
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-oslo.messaging in Ubuntu.
I suspect this is caused by the same issue as bug 1472712.
** Package changed: oslo.messaging (Ubuntu) = python-oslo.messaging
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1454070
Title:
** Changed in: python-amqp (Ubuntu Trusty)
Status: New = In Progress
** Changed in: python-amqp (Ubuntu Trusty)
Importance: Undecided = High
** Changed in: python-amqp (Ubuntu Trusty)
Assignee: (unassigned) = Edward Hope-Morley (hopem)
--
You received this bug notification
** Tags removed: cts
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1403955
Title:
DHCP's Option interface-mtu 9000 is being ignored on bridge
interface br0
To manage
** Tags removed: cts
** Tags added: sts
--
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/1290920
Title:
non-default lxc-dir breaks local provider
To manage notifications about
** Tags removed: cts
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290920
Title:
non-default lxc-dir breaks local provider
To manage notifications about this bug go to:
** Description changed:
[Impact]
Current oslo.messaging and python-amqp results in repeated connection
timeouts in the amqp transport layer (SSLError) and thus excessive
reconnect attempts. This is a known issues that was fixed in python-amqp
1.4.4.
[Test Case]
Deploy
** Branch linked: lp:~hopem/ubuntu/trusty/python-amqp/lp1472712
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472712
Title:
[SRU] Using SSL with rabbitmq prevents communication between nova-
(Ubuntu)
Assignee: (unassigned) = Edward Hope-Morley (hopem)
** Changed in: python-oslo.messaging (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-oslo.messaging in Ubuntu.
https
(Ubuntu)
Assignee: (unassigned) = Edward Hope-Morley (hopem)
** Changed in: python-oslo.messaging (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472712
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472712
Title:
Using SSL with rabbitmq prevents communication between nova-compute
and conductor after latest nova updates
To
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-oslo.messaging in Ubuntu.
https://bugs.launchpad.net/bugs/1472712
Title:
Using SSL with rabbitmq prevents communication between nova-compute
and conductor
A bit more info from my end. I've been trying out different scenarios
and it seems that this is constrained to Trusty Icehouse using python-
oslo.messaging version 1.3.0-0ubuntu1.2 configured to connect to
rabbitmq-server using ssl e.g. my nova.conf has:
rabbit_userid = nova
rabbit_virtual_host =
A bit more info from my end. I've been trying out different scenarios
and it seems that this is constrained to Trusty Icehouse using python-
oslo.messaging version 1.3.0-0ubuntu1.2 configured to connect to
rabbitmq-server using ssl e.g. my nova.conf has:
rabbit_userid = nova
rabbit_virtual_host =
Yes, I'm relatively sure.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1461738
Title:
iwl3945 on X61T crashes with Error sending C_POWER_TBL: time out after
500ms
To manage notifications about
** Description changed:
I have Ubuntu Precise guests running in kvm to which I attach volumes
immediately after boot. Sometimes I notice that the devices do not show
up in the guest e.g. they are not visible in /proc/partitions and dmesg
boot log shows no sign of then being noticed. Qemu
Public bug reported:
I have Ubuntu Precise guests running in kvm to which I attach volumes
immediately after boot. Sometimes I notice that the devices do not show
up in the guest e.g. they are not visible in /proc/partitions and dmesg
boot log shows no sign of then being noticed. Qemu itself
Public bug reported:
Doing an update of 14.04
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: python3-pkg-resources 3.3-1ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-44.59~14.04.1-generic 3.16.7-ckt14
Uname: Linux 3.16.0-44-generic i686
ApportVersion: 2.14.1-0ubuntu3.11
Architecture:
** Changed in: lsb (Ubuntu Trusty)
Assignee: Dimitri John Ledkov (xnox) = Hua Zhang (zhhuabj)
** Changed in: lsb (Ubuntu Trusty)
Status: Confirmed = In Progress
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: nova (Ubuntu Trusty)
Assignee: (unassigned) = Edward Hope-Morley (hopem)
** Changed in: nova (Ubuntu Trusty)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
New proposed build was successful. I have now deployed and tested that
this work as expected.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: nova (Ubuntu Trusty)
Assignee: (unassigned) = Edward Hope-Morley (hopem)
** Changed in: nova (Ubuntu Trusty)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https
New proposed build was successful. I have now deployed and tested that
this work 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 nova in Ubuntu.
Turns out the problem here a dodgy python-oslo.messaging in proposed
from bug 1362863. This has now been removed so hopefully a re-spin will
succeed.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
Turns out the problem here a dodgy python-oslo.messaging in proposed
from bug 1362863. This has now been removed so hopefully a re-spin will
succeed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1459046
Title:
[SRU] nova-* services do not start if rsyslog is not yet started
To manage notifications about this bug go to:
** Tags added: sts
--
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/1459046
Title:
[SRU] nova-* services do not start if rsyslog is not yet started
To manage notifications about this
The package uploaded to proposed has failed to build and I see a lot of
these messages in the buildlog:
Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py, line 335, in
import_object
__import__(self.modname)
File
The package uploaded to proposed has failed to build and I see a lot of
these messages in the buildlog:
Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py, line 335, in
import_object
__import__(self.modname)
File
fwiw i just tried building this myself and it succeeded so not sure why
the proposed pocket fails:
https://launchpad.net/~hopem/+archive/ubuntu/trusty-sru-testing-lp1459046/+build/7667621
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
fwiw i just tried building this myself and it succeeded so not sure why
the proposed pocket fails:
https://launchpad.net/~hopem/+archive/ubuntu/trusty-sru-testing-lp1459046/+build/7667621
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
When I try to load system-config-printer, it takes tens of seconds to
load. Any interactions take many more seconds, to the point that this
utility is unusable.
When I strace initial loading, here is what I get:
socket(PF_INET6, SOCK_STREAM, IPPROTO_IP) = 16
setsockopt(16,
I spent a lot of time configuring my system the way I wanted it, and
everything was lost on the next reboot. Highly annoying. This is the
kind of thing that prevents Linux from being generally accepted for the
desktop.
--
You received this bug notification because you are a member of Ubuntu
** Attachment added: xfce4-keyboard-shortcuts.xml
https://bugs.launchpad.net/xfwm4/+bug/1292290/+attachment/4429562/+files/xfce4-keyboard-shortcuts.xml
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Note: attaching xfce4-keyboard-shortcuts.xml. Observe that there are two
entries for workspace_1_key: PrimaryF1 which is the system default
and Primary1 which is what I changed it to.
(Aside: why doesn't the system respond to both of those shortcuts?)
This is under Ubuntu/xfce4 14.04
--
You
Still being stored as Primary in my Ubuntu/xfce4 14.04 system.
Seriously, what motivated some software engineer to rename ctrl as
Primary? What problem did this solve that couldn't be solved some
other way?
This is what should be done now: Track down all software that writes
Primary to any
** Branch linked: lp:~hopem/nova/icehouse-sru-lp1459046
** Patch removed: trusty nova patch
https://bugs.launchpad.net/nova/+bug/1196924/+attachment/4423093/+files/nova-2014.1.4-0ubuntu2.2-lp1196924.patch
** Changed in: nova (Ubuntu Trusty)
Status: New = In Progress
--
You received
** Branch linked: lp:~hopem/nova/icehouse-sru-lp1459046
** Patch removed: trusty nova patch
https://bugs.launchpad.net/nova/+bug/1196924/+attachment/4423093/+files/nova-2014.1.4-0ubuntu2.2-lp1196924.patch
** Changed in: nova (Ubuntu Trusty)
Status: New = In Progress
--
You received
** 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 nova in Ubuntu.
https://bugs.launchpad.net/bugs/1471022
Title:
[SRU] race between nova-compute and
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1471022
Title:
[SRU] race between nova-compute and neutron-ovs-cleanup
To manage
** Branch linked: lp:~hopem/nova/icehouse-sru-lp1459046
** Branch linked: lp:~hopem/nova/juno-sru-lp1459046
** No longer affects: oslo.log
** Patch removed: trusty-icehouse.debdiff
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1459046/+attachment/4425932/+files/trusty-icehouse.debdiff
** Branch linked: lp:~hopem/nova/icehouse-sru-lp1459046
** Branch linked: lp:~hopem/nova/juno-sru-lp1459046
** No longer affects: oslo.log
** Patch removed: trusty-icehouse.debdiff
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1459046/+attachment/4425932/+files/trusty-icehouse.debdiff
** Also affects: oslo.log
Importance: Undecided
Status: New
** Changed in: oslo.log
Status: New = Fix Committed
--
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/1459046
** Also affects: oslo.log
Importance: Undecided
Status: New
** Changed in: oslo.log
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1459046
Title:
[SRU]
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1455608
Title:
upstart job state switched to running before the sock file created
** Patch added: trusty.debdiff
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1273462/+attachment/4428923/+files/trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273462
Title:
** Changed in: nova (Ubuntu Trusty)
Assignee: Liang Chen (cbjchen) = Edward Hope-Morley (hopem)
** Changed in: nova (Ubuntu)
Assignee: Liang Chen (cbjchen) = Edward Hope-Morley (hopem)
** Changed in: nova
Status: In Progress = New
** Changed in: nova
Assignee: Edward Hope
T/U/V verified *-proposed builds. Deployed Openstack I/J/K with these
packages and all seems good.
--
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/1471022
Title:
[SRU] race between
** Changed in: nova (Ubuntu Trusty)
Assignee: Liang Chen (cbjchen) = Edward Hope-Morley (hopem)
** Changed in: nova (Ubuntu)
Assignee: Liang Chen (cbjchen) = Edward Hope-Morley (hopem)
** Changed in: nova
Status: In Progress = New
** Changed in: nova
Assignee: Edward Hope
901 - 1000 of 3939 matches
Mail list logo
