I believe it's an issue whenever you have a Neutron service that creates
tap devices (openvswitch internal ports). I think only the l3 and dhcp
services do this currently,
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in
I believe it's an issue whenever you have a Neutron service that creates
tap devices (openvswitch internal ports). I think only the l3 and dhcp
services do this currently,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
On saucy, inside of a Xen virtual machine, libvirt-bin fails to start,
with the following error in /var/log/libvirt/libvirtd.log
2013-11-05 03:46:16.290+: 3398: info : libvirt version: 1.1.1
2013-11-05 03:46:16.290+: 3398: error : udevGetDMIData:1558 : Failed to get
I worked around this in my devstack-vm repo https://github.com/lorin
/devstack-vm by adding creating a file at
~/.local/share/python_keyring/keyringrc.cfg:
[backend]
default-keyring=keyring.backends.file.PlaintextKeyring
This is insecure (passwords are stored in plaintext), but for a devstack
I'm trying to figure out where in the process it's getting added so I
can remove it before the failures happen during hte devestack process.
I see the python-keystoneclient has keyring as requirement in test-
requirements.txt. Does DevStack install packages from test-
requirements.txt?
--
You
Public bug reported:
I attempted to import an existing qcow2 virtual machine image file
through the virt-manager GUI interface. The image was in qcow2 format,
but virt-manager created a libvirt profile with the image file
classified as raw:
disk type='file' device='disk'
driver
I'm getting this on 12.04 now, although I didn't when I originally
installed cobbler.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cobbler in Ubuntu.
https://bugs.launchpad.net/bugs/1076290
Title:
cobbler-web throws 500 internal
Follow up: on my 12.04 install, I've installed OpenStack via cloud
archive, so the version of python-django I'm running is
1.4.1-2ubuntu0.3~cloud0
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cobbler in Ubuntu.
I'm getting this on 12.04 now, although I didn't when I originally
installed cobbler.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1076290
Title:
cobbler-web throws 500 internal server error
To
Follow up: on my 12.04 install, I've installed OpenStack via cloud
archive, so the version of python-django I'm running is
1.4.1-2ubuntu0.3~cloud0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1076290
I'm running into an issue with similar symptoms on precise, but I don't
have the vhost_net kernel module loaded on my compute nodes, and adding
in the iptables rule doesn't seem to help. I'm at a loss as to how to
try to debug this, since DHCP leases work when I set:
libvirt_use_virtio_for
I'm running into an issue with similar symptoms on precise, but I don't
have the vhost_net kernel module loaded on my compute nodes, and adding
in the iptables rule doesn't seem to help. I'm at a loss as to how to
try to debug this, since DHCP leases work when I set:
libvirt_use_virtio_for
Does this bug get resolved by https://review.openstack.org/17886, which
removes the max_nbd_devices flag?
--
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/861504
Title:
nova-compute-lxc
Does this bug get resolved by https://review.openstack.org/17886, which
removes the max_nbd_devices flag?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/861504
Title:
nova-compute-lxc limited by
Public bug reported:
When nginx is not running, the status reported by service nginx status
loos like this:
root@precise32:~# service nginx status
* could not access PID file for nginx
I expected the message to say that the service was stopped or not
running.
The current reported message
The reason is that I am using an ssh-based deployment tool called
Ansible (http://ansible.github.com/) that does this.
Here's the Ansible code that checks the service status:
https://github.com/ansible/ansible/blob/devel/library/service#L76
--
You received this bug notification because you are
** Changed in: openstack-manuals
Assignee: (unassigned) = Florian Haas (fghaas)
--
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/1009974
Title:
nova live-migration fails silently
** Changed in: openstack-manuals
Assignee: (unassigned) = Florian Haas (fghaas)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1009974
Title:
nova live-migration fails silently
To manage
Added this as a doc bug, here's a copy-paste from an email from Florian:
Apologies for the noise. I had mistakenly believed that since the list
of --live_migration_flags contained spaces, it was OK to quote the
--live_migration_* options. Evidently it's not, as removing the double
quotes made the
Added this as a doc bug, here's a copy-paste from an email from Florian:
Apologies for the noise. I had mistakenly believed that since the list
of --live_migration_flags contained spaces, it was OK to quote the
--live_migration_* options. Evidently it's not, as removing the double
quotes made the
Added OpenStack Compute (nova) as an affected project, since I hit this
as an OpenStack user and had a hard time finding this bug report.
** Also affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@Dave:
I think it's eb4bd86f.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/861440
Title:
test_create_multiple_servers fails on master with venv
To manage notifications about this bug go to:
Here it is in Github: https://github.com/openstack/nova/commit/eb4bd86f
At the time, I didn't realize the Gerrit marks the bugs off as committed
when they're linked, so I just manually set this one to fix committed
when I found that it fixed the issue I was having.
--
You received this bug
23 matches
Mail list logo
