Oops, I did read it wrong, you are performing LM from westmere to
broadwell.
** Changed in: nova
Status: Invalid => New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Live migration fails because of different cpu capabilities. For
instance, Broadwell has a AVX, AVX2, TXT, TSX extensions, which are not
available in Westmere.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering
It works as it is supposed to on current master. Bug is no longer valid.
** 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).
Liberty has hit the EOL, so this one is invalid. Mitaka was removed from
affected releases, so I am closing this one.
** Changed in: nova
Status: In Progress => Won't Fix
** Changed in: nova/liberty
Status: New => Won't Fix
--
You received this bug notification because you are a
Since the Mitaka cycle we use the direct release model, which means
those bug reports should have Fix Released.
** 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
Since the Mitaka cycle we use the direct release model, which means this
bug report should be tagged Fix Released.
** 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
Can you add steps, environment details etc?
** 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/1673430
Title:
Launch
If my guess is correct this can be now closed, as the
https://review.openstack.org/415482 patch should fix it. Please correct
me if I am wrong, zhengzhenyu.
** Changed in: nova
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
This does not seem to be a bug, rather a feature request and as such,
will require a bp/spec. Please reach out to folks on #openstack-nova
channel if you want to discuss it.
** Changed in: nova
Status: In Progress => Invalid
** Changed in: python-novaclient
Status: In Progress =>
Proposed change that closes this bug was merged, but somehow infra did
not catch that. Marking as complete.
** 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
Hello, kadtab.
Please be more explicit about your configuration - for instance if the
installation was devstack, from packages or some other deployment tool
and the steps that lead to your problem, that could help reproduce this
problem.
Because of the above, I am marking this one as invalid.
While it might be true that nova compute crashes if the hostname
contains a '%' char in it, but still this is not the issue that should
be handled on our side. '%' is not a character that is allowed to appear
in a hostname string.
https://en.wikipedia.org/wiki/Hostname, section "Restrictions on
** Affects: nova
Importance: Medium
Assignee: Maciej Szankin (mszankin)
Status: In Progress
** Tags: doc
** Changed in: nova
Importance: Undecided => Medium
** Changed in: nova
Assignee: (unassigned) => Maciej Szankin (mszankin)
** Changed in: nova
Statu
** Also affects: nova
Importance: Undecided
Status: New
--
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/1229445
Title:
db type could not be determined
Status
** Changed in: nova
Status: In Progress => Won't Fix
** Changed in: nova
Status: Won't Fix => New
--
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/1640164
lyarwood - AFAIK we do not use ``Fix COmmited`` status, just ``Fix
Released``.
** 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).
Bug was merged so...
** 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/1567369
Title:
Added server
nova
Importance: Low
Assignee: Maciej Szankin (mszankin)
Status: In Progress
** Changed in: nova
Assignee: (unassigned) => Maciej Szankin (mszankin)
** Changed in: nova
Importance: Undecided => Low
--
You received this bug notification because you are a membe
** 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/1596507
Title:
XenAPI: Support neutron security
Fixed in https://review.openstack.org/#/c/382660/
** 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/1625101
** 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/1625462
Title:
The value of migration.dest_compute is
Config
options should be in the central location '/nova/conf/*'. Do not declare new
config options outside of that folder.
** Affects: nova
Importance: Undecided
Assignee: Maciej Szankin (mszankin)
Status: New
** Changed in: nova
Assignee: (unassigned) => Maciej Szan
Swap partition is a disk space that is not available for storing any
kind of data other than memory dumps. So - I think it is perfectly fine
to assume that the size of swap sums up with used space.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because
This is not a bug, in my opinion.
Resizing down works when two flavors have the same disk params. Resizing
down disk is not permitted due to creating potential filesystem fault.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of
** 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/1329755
Title:
novncproxy children progresses don't quit
** 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/1268955
Title:
OVS agent updates the wrong port when
** 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/1549854
Title:
compute host "has not been heard from in a
Cleaning up this bug as it was reopened automatically by infra due to
change in gerrit. This should be fixed now fixed given Matt's comment.
Feel free to reopen if I am mistaken.
** Changed in: nova
Status: Confirmed => Invalid
--
You received this bug notification because you are a
** Changed in: nova
Status: New => Won't Fix
** Changed in: nova
Status: Won't Fix => 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/1611888
Title:
** 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/1611892
Title:
Quickbooks Customer Support Phone Number
Importance: Undecided
Assignee: Maciej Szankin (mszankin)
Status: In Progress
** Changed in: nova
Assignee: (unassigned) => Maciej Szankin (mszankin)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenSt
Tested current master branch on 16.04 with local.conf just as in bug
description and everything works correctly.
Are you sure that console is available on the same IP as the VM? And if
not, that this IP is ping-able?
Marking as invalid until any further proof appears.
** Changed in: nova
32 matches
Mail list logo