Public bug reported:
Nova while monitoring live migration progress bases on what libvirt
reports under data_remaining property
https://github.com/openstack/nova/blob/54482fde22742bc852414c58552fe64ea59d61d5/nova/virt/libvirt/driver.py#L6189-L6193
However, data_remaining does not reflect any valu
Public bug reported:
Due to all changes in nova live migration code path there is condition
that is always evaluated to False:
https://github.com/openstack/nova/blob/5a81b00e6b2adba2a380b90e402ff391d64ea6a5/nova/virt/libvirt/driver.py#L5888
Even when using the lowest RPC microversion (4.0) migra
Public bug reported:
Nova fails all live migrations on dedicated interface due to conversion
of string to unicode (in Python 2.7).
My environment:
* nova trunk, commit 40f9b0ad16d3a5fae184bbe6d4a49cf792967089
* QEMU 2.6
* Libvirt 1.3.4
1. Set live_migration_inbound_addr to IP address of existing
** Changed in: nova
Status: In Progress => Invalid
** Changed in: nova
Assignee: Pawel Koniszewski (pawel-koniszewski) => (unassigned)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
===
1. Exact version of OpenStack you are running
Trunk of nova, commit
https://github.com/openstack/nova/commit/bebc86bf5598571a28dd47f17a05dd616fe0f550
2. Which hypervisor did you use?
QEMU/KVM + Libvirt
** Affects: nova
Importance: Undecided
Assignee: Pawel Koniszewski (pawel
Confirmed that it is a bug. Libvirt correctly uses
live_migration_inbound_addr, but QEMU still defaults to the hostname of
the other side instead of provided IP address.
** Changed in: nova
Status: Invalid => Confirmed
** Changed in: nova
Importance: Undecided => Medium
** Tags added:
Talked with danpb on IRC and looks like we can use block live migration
in such case, so #1 and #2 are invalid too.
** Changed in: nova
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Co
I believe that this bug is valid and we might corrupt volume-backed VMs
when libvirt version is <=1.2.17.
So the bug starts here
https://github.com/openstack/nova/blob/660ecaee66ccab895b282c2ed45c95c809ad6833/nova/virt/libvirt/driver.py#L5592
- for volume backed VMs dest_check_data.is_volume_backe
*** This bug is a duplicate of bug 1591240 ***
https://bugs.launchpad.net/bugs/1591240
Marking this one as a duplicate as it is fixed already -
https://review.openstack.org/#/c/331685/
** This bug has been marked a duplicate of bug 1591240
progress_watermark is not updated
--
You receive
t state of a VM.
** Affects: nova
Importance: Undecided
Assignee: Pawel Koniszewski (pawel-koniszewski)
Status: New
** Tags: live-migration
** Changed in: nova
Assignee: (unassigned) => Pawel Koniszewski (pawel-koniszewski)
--
You received this bug notification because you are
Public bug reported:
Commit
https://github.com/openstack/nova/commit/111a852e79f0d9e54228d8e2724dc4183f737397
introduced regression that causes affinity/anti-affinity policies to be
omitted while live migrating an instance.
This is because we don't pass instance_group here:
https://github.com/op
L2391
Basically because here block_migration will be None and real value will
be stored in migrate_data.block_migration
** Affects: nova
Importance: Undecided
Assignee: Pawel Koniszewski (pawel-koniszewski)
Status: In Progress
** Tags: live-migration
** Changed in: nova
Ass
Public bug reported:
I have an environment consisting of three nodes:
Controller Mitaka, commit id: 59a07f00ad3c527e3b39712220cf9de1e68cd16f
Compute Mitaka, commit id: 59a07f00ad3c527e3b39712220cf9de1e68cd16f
Compute Stable/Liberty, commit id: 184e2552490ecfded61db3cc9ba1cd8d6aac1644
I am able t
stack/data/nova/instances/572ad149-b7c5-4b77-85b5-34c1d2d37fcf/disk' (as
uid:110, gid:116): No such file or directory
Fast workaround is making sure at compute manager level that
block_migration == migrate_data.block_migration, but really we should
cleanup all this mess and send only one
In Liberty we implemented support to live migrate instances booted from
volume, it wasn't supported in Kilo -
https://review.openstack.org/#/c/195885/. This is why you can reproduce
it in Kilo, but not in Liberty. Unfortunately Kilo is security-supported
only right now, so we probably can't backpor
Public bug reported:
Let's say we have a setup with 3 compute nodes (CN1, CN2 and CN3) and 3
controllers (in HA mode). There are 2 VMs with anti-affinity policy (the
same server group) running in the environment:
* CN1 - VM A (anti-affinity)
* CN2 - VM B (anti-affinity)
* CN3 - empty
If we trigg
I went through nova-api logs and it seems to me that it is a networking
issue. You tried a lot of operations, e.g., get spice/rdp/serial console
and all of them failed because of MessagingTimeout.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you
So it is packstack related issue - please refer to
https://bugzilla.redhat.com/show_bug.cgi?id=968310
** Bug watch added: Red Hat Bugzilla #968310
https://bugzilla.redhat.com/show_bug.cgi?id=968310
** Changed in: nova
Status: Confirmed => Invalid
** Changed in: nova
Assignee: lvmx
This has been fixed in Liberty - https://review.openstack.org/214434.
Because kilo is security-supported only marking this one as invalid.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscri
This is a regression introduced in Gluster 3.4.1 as pointed here -
http://www.gluster.org/pipermail/gluster-users/2014-January/015885.html
There is a workaround for this issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1057645#c7
Marking as invalid as this is not nova bug.
** Changed in: nova
This will be implemented as part of
https://blueprints.launchpad.net/nova/+spec/refresh-abort-live-migration
similarly to https://review.openstack.org/#/c/179149/
** Changed in: nova
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
En
Nova allows to live migrate multiple VMs at a time, there's no limit for
simultaneous live migrations - everything depends on use case and setup
configuration (particularly network configuration and bandwidth).
host-evacuate-live is implemented in python-novaclient, so nothing to
fix in nova.
**
It is no longer valid so marking as invalid.
** Changed in: glance
Status: Confirmed => Won't Fix
** Changed in: glance
Status: Won't Fix => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bu
B and unhandled
exceptions.
** Affects: glance
Importance: Undecided
Assignee: Pawel Koniszewski (pawel-koniszewski)
Status: New
** Changed in: glance
Assignee: (unassigned) => Pawel Koniszewski (pawel-koniszewski)
--
You received this bug notification because you are a m
Public bug reported:
Upgrade metadefs functionality introduced issue in db export_metadefs
command - it ends with NoSuchColumnError exception:
NoSuchColumnError: "Could not locate column in row for column 'name'"
** Affects: glance
Importance: High
Assignee: Pawe
Assignee: Pawel Koniszewski (pawel-koniszewski)
Status: New
** Tags: live-migration
** Changed in: nova
Assignee: (unassigned) => Pawel Koniszewski (pawel-koniszewski)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
ies inside objects.
The problem is because "additionalProperties" option is not explicitly
set in property schema. If this option isn't set, it will be attached to
the root level of json schema (default value is False and it applies
ONLY to the same level). For property schema it works b
** 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/1396529
Title:
Nova deletes instance when compute/rabbit is dead
Public bug reported:
When e.g. nova-compute or rabbit-server dies during live migration and
somehow nova-compute is not able to report new host for migrated VM,
then after successful system recovery nova deletes VM instead of sending
host update. This is from nova log:
09:00:25.704 INFO nova.com
'vtime': timeutils.normalize_time(
timeutils.parse_isotime("1970-01-01T00:00:00Z"))}
This means that compute-trust.json should be changed to match trust
levels that are expected by Trust Filter.
** Affects: glance
Importance: Undecided
Assignee:
** Also affects: python-glanceclient
Importance: Undecided
Status: New
** Changed in: python-glanceclient
Assignee: (unassigned) => Pawel Koniszewski (pawel-koniszewski)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscri
session=session)).
** Affects: glance
Importance: Undecided
Assignee: Pawel Koniszewski (pawel-koniszewski)
Status: In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs
Public bug reported:
Current approach of loading metadata definitions to database does not
use transactions. Instead it inserts data to database without
transactions so if something fails inside a single file, e.g. inserting
properties, then user has to manually remove all related data from
databa
Public bug reported:
Currently script which loads metadeta definitions to database uses try
except block with open(file) inside. There is better solution in Python
for file streams - use 'with open(file) as...'. With this approach we
will be sure that every resource is cleaned up when the code fin
Review: https://review.openstack.org/#/c/118627/
** Project changed: glance => python-glanceclient
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1364893
Title:
New version of requests l
anceclient.
** Affects: glance
Importance: Undecided
Assignee: Pawel Koniszewski (pawel-koniszewski)
Status: In Progress
** Changed in: glance
Assignee: (unassigned) => Pawel Koniszewski (pawel-koniszewski)
** Changed in: glance
Status: New => In Progress
Raghavendrachari,
please post your question to the openstack mailing list:
(openst...@lists.openstack.org), this is a question, not a bug.
Kind regards,
Pawel
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering
** Also affects: openstack-manuals
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1343907
Title:
db_auto_create flag in documentation is no lon
Importance: Undecided
Assignee: Pawel Koniszewski (pawel-koniszewski)
Status: New
** Affects: openstack-manuals
Importance: Undecided
Status: New
** Changed in: glance
Assignee: (unassigned) => Pawel Koniszewski (pawel-koniszewski)
--
You received this bug
39 matches
Mail list logo
