[Yahoo-eng-team] [Bug 1026029] Re: reboot instance catches exception: libvirtError: Domain not found

I think this bug was fixed in Folsom, so change it to fix released. ** Changed in: nova Status: Triaged => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bu

[Yahoo-eng-team] [Bug 1089709] Re: floating ip association doesn't correctly assigned to interface specified

The code is correct. The flag is used as an override so that one can have heterogeneous nodes where the public_interface is different across nodes. For example: Node 1: public_interface=eth0 Node 2: public_interface=eth1 If you want to use the interface from the database do not set public_i

[Yahoo-eng-team] [Bug 1136557] [NEW] Cannot install the Openstack since the dependence error

You have been subscribed to a public bug: Installing the OpenStack by devstack, the installation stopped since the dependence error. Installed /opt/stack/horizon Processing dependencies for horizon==2013.1.a17.gce7c49a error: Installed distribution requests 1.1.0 conflicts with requirement reque

[Yahoo-eng-team] [Bug 1091939] Re: nova-network applies too liberal a SNAT rule

** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1091939 Title: nova-network applies too liberal a SNAT rule Status in O

[Yahoo-eng-team] [Bug 1086301] Re: Code logic inconsistency in quantum.db.securitygroups_db.py:SecurityGroupDbMixin._ensure_default_security_group

This has already been fixed by Aaron Rosen via commit for bug 1130927. Please close this out. ** Changed in: quantum Status: Triaged => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to quantum. https://bugs.launchpad

[Yahoo-eng-team] [Bug 988698] Re: Tenant is created successfully without any information supplied.

fix was released in folsom for v2 api. name was set as required field. see: https://github.com/openstack/keystone/commit/19b6076869f6e177febc559b191f4ef9c352e55b ** Changed in: keystone Status: Triaged => Fix Released ** Changed in: keystone Assignee: adapaka bhavaniprasad (adapaka-

[Yahoo-eng-team] [Bug 1103202] Re: grizzly scheduler can not start with import error

Please re-open this bug when you have the information. ** Changed in: nova Status: Incomplete => Won't Fix ** Changed in: nova (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to

[Yahoo-eng-team] [Bug 1118686] Re: nova-consoleauth issue with rabbitmq when trying to view console

Nope, seems to be working fine now. Have a new install since this was submitted. ** Changed in: nova (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.lau

[Yahoo-eng-team] [Bug 1029430] Re: KVM guests networking issues with no virbr0 and with vhost_net kernel modules loaded

My understanding is that this relates to non-libvirt-maintained bridges, so marking wontfix for libvirt. If we wanted a generic way to address this, perhaps /etc/init/qemu- kvm.conf, if it is modprobing vhost_net, should add the iptables rule if not already present? ** No longer affects: libvirt

[Yahoo-eng-team] [Bug 1131351] Re: Two quantum documents are missing from wiki page.

Does not really look like a Quantum Bug! The first attachment appears to have been lost in the migration from moinmoin. I'm pretty sure it's not been totally lost, but you might want to ask on the mailing list or IRC for it. The second attachment is not even related to the Quantum source tree app

[Yahoo-eng-team] [Bug 1105135] Re: live-migrate error reporting raises errors itself

This bug is same as https://bugs.launchpad.net/nova/+bug/1076308, and was fixed there. ** Changed in: nova Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https:/