** Project changed: glance = ubuntu
** Changed in: ubuntu
Status: Invalid = Confirmed
** Package changed: ubuntu = glance (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to glance in Ubuntu.
** Project changed: glance = ubuntu
** Changed in: ubuntu
Status: Invalid = Confirmed
** Package changed: ubuntu = glance (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1214947
oh, sorry - I missed your message. It's in the log and the report -
3.2.0-52-generic
--
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/1233703
Title:
openvswitch-datapath-dkms
oh, sorry - I missed your message. It's in the log and the report -
3.2.0-52-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1233703
Title:
openvswitch-datapath-dkms fails to build kernel
Public bug reported:
Setting up openvswitch-datapath-dkms (1.10.2-0ubuntu1~cloud0) ...
Creating symlink /var/lib/dkms/openvswitch/1.10.2/source -
/usr/src/openvswitch-1.10.2
DKMS: add completed.
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
** Also affects: cloud-archive
Importance: Undecided
Status: New
--
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/1233703
Title:
openvswitch-datapath-dkms fails to
Public bug reported:
Setting up openvswitch-datapath-dkms (1.10.2-0ubuntu1~cloud0) ...
Creating symlink /var/lib/dkms/openvswitch/1.10.2/source -
/usr/src/openvswitch-1.10.2
DKMS: add completed.
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
** 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/1233703
Title:
openvswitch-datapath-dkms fails to build kernel modules in
This is addressed (I believe) in debian bug #722598 and upload 79. Can
you pull and test?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/978032
Title:
partitioning step doesn't have discard as a
I've resorted to the attached. This works for us, and brings things up
in the correct order.
** Attachment added: upstart job for for quantum ovs agent
https://bugs.launchpad.net/ubuntu/+source/quantum/+bug/1058752/+attachment/3813237/+files/quantum-plugin-openvswitch-agent.conf
--
You
This is being looked at in an upstream thread at
http://lists.gnu.org/archive/html/qemu-devel/2013-07/msg01850.html
Cheers,
--
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/1100843
This is being looked at in an upstream thread at
http://lists.gnu.org/archive/html/qemu-devel/2013-07/msg01850.html
Cheers,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1100843
Title:
Live
We are reliably seeing this post live-migration on an openstack
platform.
Setup:
hypervisor == Ubuntu 12.04.3 LTS
libvirt === 1.0.2-0ubuntu11.13.04.2~cloud0
qemu-kvm === 1.0+noroms-0ubuntu14.10
storage: NFS exports
Guest VM OS: Ubuntu 12.04.1 LTS and CentOS 6.4
We have ept enabled.
Sample
We are reliably seeing this post live-migration on an openstack
platform.
Setup:
hypervisor == Ubuntu 12.04.3 LTS
libvirt === 1.0.2-0ubuntu11.13.04.2~cloud0
qemu-kvm === 1.0+noroms-0ubuntu14.10
storage: NFS exports
Guest VM OS: Ubuntu 12.04.1 LTS and CentOS 6.4
We have ept enabled.
Sample
I would quite like to see this backported to grizzly. How do I go about
doing that, or encouraging that?
** Also affects: quantum (Ubuntu)
Importance: Undecided
Status: New
** Changed in: quantum (Ubuntu)
Status: New = Fix Committed
--
You received this bug notification
Have you actually asked the SRU team about this? The version of open-
iscsi in precise has a bad hack that means that you can't use diskless
nodes as openstack compute hosts. I would have thought that fixing a
piece of software used by the UEC platform in an LTS release would
qualify as
Hello,
That seems to go against what is being said by both racb and stgraber
above. The quick hack of not starting the daemon breaks using precise,
an LTS release, as a compute node for openstack when isci is in use for
block storage. This seems a bit extreme to me.
Can you please reconsider?
presumably 'start on started rc' is too coarse for this? I don't
actually know.
It seems a bit of a regression to have to give up dependencies between
init scripts for upstart. Perhaps some coordination with the openvswitch
maintainers might be in order? I can't believe this is that hard to fix.
Adding this fix into a stable release update for precise.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/850960
Title:
iscsid tries to reconnect existing session at startup, failing to do
so and
so, the diffstat between the version I know doesn't work and the version I know
does work is:
335 files changed, 70473 insertions(+), 6135 deletions(-)
If what you're saying is, you figure it out, that sounds like work to
me, that's ok, I understand that. We have a working backport of the
new
to fix this, all that should be needed is:
start on started openvswitch-switch
Cheers,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1058752
Title:
[quantum-plugin-openvswitch-agent] Quantum
Hello,
We're still seeing iscsid not starting on a node with iscsi root. A
quick test of the version in quantal looks like it starts iscsid and
consequently handles things like target failovers properly.
We have diskless nodes that we would like to use as openstack compute
nodes. While this
Public bug reported:
Hi,
When used with quantum, python-nova does not pass in any region
information when constructing a quantum-client, making the compute
services on my multi-region setup fail when multiple endpoints are
returned by keystone.
The problem is that in
** Package changed: nova (Ubuntu) = nova
--
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/1081037
Title:
python-nova: not region aware when used with quantum
To manage notifications
Public bug reported:
Hi,
When used with quantum, python-nova does not pass in any region
information when constructing a quantum-client, making the compute
services on my multi-region setup fail when multiple endpoints are
returned by keystone.
The problem is that in
** Package changed: nova (Ubuntu) = nova
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1081037
Title:
python-nova: not region aware when used with quantum
To manage notifications about this bug go
26 matches
Mail list logo
