out of date
** Changed in: openstack-ci
Status: Triaged => Invalid
** Changed in: nova
Status: Confirmed => 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.ne
moving to opinion. It's fine if someone wants to resurect this later,
but we don't need to carry it in the tracker.
** Changed in: nova
Status: Confirmed => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack
The only place where this is still a problem is the flavor api. This
would require adding limit and paging interfaces into it's db api, then
exposing them in the interface. Pretty straight forward, and worth doing
in H.
** Summary changed:
- Database results not limited on server-side
+ Flavors l
nova now requires all database to be innodb, so I think we're ok now
(this was released in Folsom)
** Changed in: nova
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nov
fixed by bumping min SQA to 0.7.8
** Changed in: nova
Status: Confirmed => 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/bugs/1025544
Title:
[SRU] schem
So we are currently doing shorter types for MySQL, and packed types for
PG. Given that we have to handle the IPv6 case, I'm going to consider
shorter strings "solved" for now.
** Changed in: nova
Status: In Progress => Fix Committed
** Changed in: nova
Status: Fix Committed => Fix R
incomplete for 60 days with no response from bug creator
** Changed in: nova
Status: Incomplete => 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/1083054
T
** Changed in: swift
Status: In Progress => Fix Released
** Changed in: nova
Status: In Progress => 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
moving to opinion, as it's so old, it's probably out of date
** Changed in: openstack-qa
Status: In Progress => Opinion
** Changed in: nova
Status: Confirmed => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed t
As far as I can tell, this bug is no longer seen.
** Changed in: nova
Status: Confirmed => 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/bugs/1084698
Titl
Looks like this was fixed prior to March 11th but after March 8th
** Changed in: nova
Status: Confirmed => 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
This bug is too general to be acted on. I'm marking invalid and creating
specific stack trace bugs with stacktrace tag for the ones still open.
** Changed in: nova
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
I think this is out of date with the keystone split. Marking as invalid.
** Changed in: nova
Status: Confirmed => 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/
this seems to be working fine upstream now
** Changed in: nova
Status: Confirmed => 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/bugs/902398
Title:
Fir
** Changed in: tempest
Status: Fix Committed => Fix Released
** Changed in: tempest
Milestone: None => havana-1
--
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/1
*** This bug is a duplicate of bug 1185834 ***
https://bugs.launchpad.net/bugs/1185834
** This bug is no longer a duplicate of bug 1181567
tempest: test_create_server / wait_for_server_status timeout
** This bug has been marked a duplicate of bug 1185834
gate-tempest-devstack-vm-quantum
*** This bug is a duplicate of bug 1192131 ***
https://bugs.launchpad.net/bugs/1192131
** This bug is no longer a duplicate of bug 1185834
gate-tempest-devstack-vm-quantum fail with keyerror in compute log
** This bug has been marked a duplicate of bug 1192131
giant race in quantum - qua
*** This bug is a duplicate of bug 1192131 ***
https://bugs.launchpad.net/bugs/1192131
** This bug is no longer a duplicate of bug 1185834
gate-tempest-devstack-vm-quantum fail with keyerror in compute log
** This bug has been marked a duplicate of bug 1192131
giant race in quantum - qua
*** This bug is a duplicate of bug 1192131 ***
https://bugs.launchpad.net/bugs/1192131
** This bug is no longer a duplicate of bug 1185834
gate-tempest-devstack-vm-quantum fail with keyerror in compute log
** This bug has been marked a duplicate of bug 1192131
giant race in quantum - qua
This appears like it might be an issue with the ppa in pike
** Also affects: qemu
Importance: Undecided
Status: New
** Project changed: qemu => ubuntu
** Package changed: ubuntu => qemu (Ubuntu)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team
There are not strong guaruntees about scheduling, especially when you
are hitting failure domains. So while this is not ideal, I think this is
more of a wishlist item to have this function when you are at a full
packed scenario (more guests than computes trying policy based
placement).
Marking Opi
** Also affects: python-openstackclient
Importance: Undecided
Status: New
** No longer affects: nova
--
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/1609865
Titl
The original bug turned out to be a typo in a config file. Closing as
invalid, as this is going to be too confusing to change streams on what
the bug is.
If there is a second issue, please open as a second bug.
** Changed in: nova
Status: New => Won't Fix
** Changed in: nova
Status
Both Kilo and Liberty are EOL
** Changed in: nova
Status: New => Invalid
** Changed in: nova
Status: Invalid => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launch
** 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/1642419
Title:
GPU Passthrough isn't working
Status in kolla-ansible:
We don't seem to have a reproduce scenario, and the bug is on Kilo, so
marking Invalid for now. Please reopen if you have a reproduce scenario.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is su
** 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/1558807
Title:
Volume attached at different path than reported by nova/c
Liberty is EOL. And this bug has kind of wandered all over the place. I
think that if there is an issue that we can repeat in Master we should
create a new fresh bug and work from there.
** Changed in: nova
Status: New => Won't Fix
--
You received this bug notification because you are a m
This limitation should be documented in the Admin Guide
** Also affects: openstack-manuals
Importance: Undecided
Status: New
** No longer affects: nova
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (
Just making Nova wait longer doesn't seem to be a good strategy, because
then we just end up in a different deadlock scenario of waiting with no
idea when things are finished.
I think that for long provisioning situations like this we just need to
expect people to preprovision the volumes first fr
** 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/1591071
Title:
neutronclient.common.exceptions.Unauthorized
Status in O
This was fixed in I14e061a28678ad28e38bd185e3d0a35cae41a9cf yesterday.
** Changed in: nova
Status: New => 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/bug
The firewall driver only applies to the virt layer, not any of the api
services. The metadata server has some pretty specific iptables rules it
needs to work with the magic addresses, so that's not actually
configurable.
This is basically working as designed.
** Changed in: nova
Status: Ne
Kilo is EOL.
This appears that you do not have connectivity to your rabbitmq
environment. Instead of using host "controller" please us the specific
ip address of the controller
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Ya
I kind of feel this is in the class of bugs of "I hit everything with a
sledge hammer really hard without tuning, and it fell over".
Falling over is what things do with out of the box defaults that are
pushed way beyond their limits.
** Changed in: nova
Status: New => Won't Fix
--
You re
This is a long standing issue with Keystone architecture. There is no
real fix at this stage. The work around is to increase token timeouts in
keystone.
** Changed in: nova
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
** Changed in: nova
Status: New => Opinion
** Changed in: nova
Importance: Undecided => Wishlist
--
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/1602740
Title:
This is the basic issue with volumes not being scheduler aware. The
placement api in Nova is the path to solving this. Please get involved
there if you can.
** Changed in: nova
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Te
There was still no information provided about why the CPU Filter threw
out the rest of the nodes. That is the important bit here that we need
to move forward.
As such, closing as Invalid. If someone is able to put more detailed
debug into the scheduler to figure out which hosts get dumped at the
D
This is basically a libvirt bug, which is fixed upstream. It is probably
not worth trying to mitigate this in Nova given the versions of libvirt
that distros are moving to.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Apparently this is a misconfiguration issue with memcached_servers. Can
people post their nova.conf to understand what went wrong here? If we
need to add a warning on that option it would be good to know.
** Changed in: nova
Status: New => Invalid
** Changed in: nova
Status: Invalid
Until the resource providers work is done, there is no fix for this.
Under current architecture this is a Won't Fix
** Changed in: nova
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Comp
As listed, this is an issue with memcache needing to be flushed after
upgrade. This should be handled at the orchestration layer for upgrade.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subs
Known limitation
** Changed in: nova
Status: New => Won't Fix
--
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/1627005
Title:
Changing use_cow_images breaks existi
Fixed in https://review.openstack.org/#/c/306470/
** Changed in: nova/liberty
Status: Confirmed => Fix Released
** Changed in: nova/mitaka
Status: Confirmed => Fix Released
** Changed in: nova
Status: In Progress => Fix Released
--
You received this bug notification becaus
Not seen in the gate any more, the fixing patch is in merge conflict and
really old
** Changed in: nova
Status: In Progress => Invalid
** Changed in: nova
Assignee: Matt Riedemann (mriedem) => (unassigned)
--
You received this bug notification because you are a member of Yahoo!
Engi
Please never ever open bugs like this
** No longer affects: nova
** No longer affects: ceilometer
** No longer affects: heat
** No longer affects: python-novaclient
** No longer affects: tempest
** No longer affects: python-manilaclient
** No longer affects: python-keystoneclient
** No long
** No longer affects: nova
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1567295
Title:
tox -e py27 is failing due to fixtures 2.0.0 release
Status in neutron:
Fix Released
Status in
The master patch seems to have merged
** Changed in: nova
Status: In Progress => 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/bugs/1296414
Title:
quota
** Changed in: nova
Status: Triaged => Won't Fix
--
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/1631133
Title:
nova's osapi_compute_workers is not valid (must be
** Changed in: nova
Status: In Progress => 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/1283655
Title:
Adds host_ip to hypervisor show API
Status i
Andreaf fixed this this week
** Changed in: devstack
Status: Confirmed => Fix Released
** Changed in: nova
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Looks like this was fixed in https://review.openstack.org/#/c/397407/
** Changed in: nova
Status: New => Confirmed
** Changed in: nova
Status: Confirmed => Fix Released
** Changed in: nova
Importance: Undecided => Medium
--
You received this bug notification because you are a
Feel free to propose fix.
** Changed in: nova
Status: New => Opinion
** Changed in: nova
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad
** Also affects: openstack-requirements
Importance: Undecided
Status: New
** No longer affects: nova
--
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/1653967
Titl
This is a bit of a deeper architecture change around permissions and
live migration. Probably should be discussed as a spec.
** Changed in: nova
Status: New => Incomplete
** Changed in: nova
Status: Incomplete => Opinion
** Changed in: nova
Importance: Undecided => Wishlist
--
Public bug reported:
x-compute-request-id and x-openstack-request-id are not documented in
our API ref, we should add those.
** Affects: nova
Importance: Medium
Status: Confirmed
** Tags: api-ref low-hanging-fruit
** Changed in: nova
Status: New => Confirmed
** Changed in
Public bug reported:
This is similar to https://bugs.launchpad.net/tempest/+bug/1357055 which
is closed (and honestly would be confusing to make this the same bug).
When trying to tear down subnets, they sometimes fail because the port
still exists. However there is no indication that the port de
Was working as designed, the right config is now in the bug
** 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/1677426
Title
The current min libvirt is 1.2.9, so I think this isn't something we're
going to fix in master
** Changed in: nova
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://b
There is no such thing as a reader role at this point, this is all
working as designed. Implementing a reader role is something that is
currently a site local change.
** Changed in: nova
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engi
zmq is really not a supported setup at this time. Patches are welcome,
but the bug isn't likely to be worked on by anyone.
** Changed in: nova
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenSta
There is no active patch here
** Changed in: nova
Assignee: Zhenyu Zheng (zhengzhenyu) => (unassigned)
** Changed in: nova
Status: New => Opinion
** Changed in: nova
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Yahoo!
Engine
Feel free to propose a patch, this doesn't really need a bug.
** Changed in: nova
Status: New => Opinion
** Changed in: nova
Importance: Low => Wishlist
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute
This is really a design decision, it's not really clear that changing
the expected behavior here is going to provide a good experience for
operators. We punt on various classes of potential DOS (like api rate
limiting).
** Changed in: nova
Status: In Progress => Won't Fix
** Changed in: no
This is really a much deeper issue that can't be handled just as a bug
** Changed in: nova
Status: New => Opinion
** Changed in: nova
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Ope
Changing the ssh port of nova computes is not supported. The nova-
compute services should not be internet accessible (if so there are many
more issues you might run into). As such the policy of moving well known
ports has no security value.
** Changed in: nova
Status: New => Won't Fix
--
It's fine that people want to change these, we're just not going to
track them very effectively as bugs.
** Changed in: nova
Status: In Progress => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (
** Changed in: nova
Status: Confirmed => Won't Fix
--
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/1211016
Title:
List availability zones fails in a cell setup
St
There is really very low exposure here
** Changed in: nova
Status: Confirmed => Opinion
--
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/1246160
Title:
shuffle met
This is not fixable for libvirt.
** Changed in: nova
Status: Confirmed => Won't Fix
--
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/1217874
Title:
cinder shows wr
This devstack bug was last updated over 180 days ago, as devstack
is a fast moving project and we'd like to get the tracker down to
currently actionable bugs, this is getting marked as Invalid. If the
issue still exists, please feel free to reopen it.
** Changed in: devstack
Status: Confirm
This devstack bug was last updated over 180 days ago, as devstack
is a fast moving project and we'd like to get the tracker down to
currently actionable bugs, this is getting marked as Invalid. If the
issue still exists, please feel free to reopen it.
** Changed in: devstack
Status: Fix Com
This bug was last updated over 180 days ago, as devstack is a fast moving
project
and we'd like to get the tracker down to currently actionable bugs, this is
getting
marked as Invalid. If the issue still exists, please feel free to reopen it.
** Changed in: devstack
Status: Triaged => In
This devstack bug was last updated over 180 days ago, as devstack
is a fast moving project and we'd like to get the tracker down to
currently actionable bugs, this is getting marked as Invalid. If the
issue still exists, please feel free to reopen it.
** Changed in: devstack
Status: Fix Com
This devstack bug was last updated over 180 days ago, as devstack
is a fast moving project and we'd like to get the tracker down to
currently actionable bugs, this is getting marked as Invalid. If the
issue still exists, please feel free to reopen it.
** Changed in: devstack
Status: In Prog
This devstack bug was last updated over 180 days ago, as devstack
is a fast moving project and we'd like to get the tracker down to
currently actionable bugs, this is getting marked as Invalid. If the
issue still exists, please feel free to reopen it.
** Changed in: devstack
Status: Confirm
This devstack bug was last updated over 180 days ago, as devstack
is a fast moving project and we'd like to get the tracker down to
currently actionable bugs, this is getting marked as Invalid. If the
issue still exists, please feel free to reopen it.
** Changed in: devstack
Status: Fix Com
This devstack bug was last updated over 180 days ago, as devstack
is a fast moving project and we'd like to get the tracker down to
currently actionable bugs, this is getting marked as Invalid. If the
issue still exists, please feel free to reopen it.
** Changed in: devstack
Status: In Prog
This devstack bug was last updated over 180 days ago, as devstack
is a fast moving project and we'd like to get the tracker down to
currently actionable bugs, this is getting marked as Invalid. If the
issue still exists, please feel free to reopen it.
** Changed in: devstack
Status: Fix Com
This devstack bug was last updated over 180 days ago, as devstack
is a fast moving project and we'd like to get the tracker down to
currently actionable bugs, this is getting marked as Invalid. If the
issue still exists, please feel free to reopen it.
** Changed in: devstack
Status: New =>
This devstack bug was last updated over 180 days ago, as devstack
is a fast moving project and we'd like to get the tracker down to
currently actionable bugs, this is getting marked as Invalid. If the
issue still exists, please feel free to reopen it.
** Changed in: devstack
Status: In Prog
This devstack bug was last updated over 180 days ago, as devstack
is a fast moving project and we'd like to get the tracker down to
currently actionable bugs, this is getting marked as Invalid. If the
issue still exists, please feel free to reopen it.
** Changed in: devstack
Status: New =>
This devstack bug was last updated over 180 days ago, as devstack
is a fast moving project and we'd like to get the tracker down to
currently actionable bugs, this is getting marked as Invalid. If the
issue still exists, please feel free to reopen it.
** Changed in: devstack
Status: New =>
This devstack bug was last updated over 180 days ago, as devstack
is a fast moving project and we'd like to get the tracker down to
currently actionable bugs, this is getting marked as Invalid. If the
issue still exists, please feel free to reopen it.
** Changed in: devstack
Status: New =>
** Changed in: devstack
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1470625
Title:
Mechanism to register and run all external neutron alem
ne fails because "ArgsAlreadyParsedError: arguments already parsed:
cannot register CLI option" [3]
Sean Dague says that it's because grenade does not upgrade keystone
script, and the script should not even be installed in a way it's now
installed (copied into /var/www/..
This grenade bug was last updated over 180 days ago, as grenade
is a fast moving project and we'd like to get the tracker down to
currently actionable bugs, this is getting marked as Invalid. If the
issue still exists, please feel free to reopen it.
** Changed in: grenade
Status: New => Inv
This grenade bug was last updated over 180 days ago, as grenade
is a fast moving project and we'd like to get the tracker down to
currently actionable bugs, this is getting marked as Invalid. If the
issue still exists, please feel free to reopen it.
** Changed in: grenade
Status: New => Inv
This grenade bug was last updated over 180 days ago, as grenade
is a fast moving project and we'd like to get the tracker down to
currently actionable bugs, this is getting marked as Invalid. If the
issue still exists, please feel free to reopen it.
** Changed in: grenade
Status: Incomplete
** Changed in: devstack
Status: Incomplete => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1645263
Title:
Unable to run stack.sh on fresh new Ubunt
This grenade bug was last updated over 180 days ago, as grenade
is a fast moving project and we'd like to get the tracker down to
currently actionable bugs, this is getting marked as Invalid. If the
issue still exists, please feel free to reopen it.
** Changed in: grenade
Status: In Progres
This devstack bug was last updated over 180 days ago, as devstack
is a fast moving project and we'd like to get the tracker down to
currently actionable bugs, this is getting marked as Invalid. If the
issue still exists, please feel free to reopen it.
** Changed in: devstack
Status: In Prog
This devstack bug was last updated over 180 days ago, as devstack
is a fast moving project and we'd like to get the tracker down to
currently actionable bugs, this is getting marked as Invalid. If the
issue still exists, please feel free to reopen it.
** Changed in: devstack
Status: New =>
This devstack bug was last updated over 180 days ago, as devstack
is a fast moving project and we'd like to get the tracker down to
currently actionable bugs, this is getting marked as Invalid. If the
issue still exists, please feel free to reopen it.
** Changed in: devstack
Status: New =>
** Changed in: nova
Status: Fix Committed => 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/bugs/1675676
Title:
Migrate VM failed when anti-affinity group
** Changed in: nova/liberty
Status: Fix Committed => 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/bugs/1580625
Title:
volume-backed resize intermittentl
** Changed in: nova/liberty
Status: Fix Committed => 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/bugs/1576048
Title:
"live_migration" call in Liberty d
** Changed in: nova/liberty
Status: Fix Committed => 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/bugs/1565466
Title:
pci detach failed with 'PciDevice'
** Changed in: nova/liberty
Status: Fix Committed => 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/bugs/1570748
Title:
Bug: resize instance after edit fl
601 - 700 of 1444 matches
Mail list logo
