from the last comment it seems to me that this bug is not going to be fixed in
Nova but a workaround is in place in Cinder. Considering that and considering
that the last comment was 1+ year ago I am going to close this ticket as "Won't
fix".
Please feel free to comment here if you disagree.
**
I agree with Markus that this is not a bug.
+1 on the discussion on the ML and if there will be any interest than please
submit a blueprint and/or a spec to better discuss the proposal.
I am going to mark the bug as invalid.
** Changed in: nova
Status: In Progress => Invalid
--
You rece
return the list of migration in progress:
https://github.com/openstack/nova/blob/87dc738763d6a7a10409e14b878f5cdd39ba805e/nova/db/sqlalchemy/api.py#L4851
** Affects: nova
Importance: Low
Assignee: Andrea Rosa (andrea-rosa-m)
Status: In Progress
** Tags: libvirt live-migration
based on your last comment I am going to close this bug as it is not
"reproducible".
Please feel free to re-open it if you have a clear way to reproduce it again.
Thanks
** Changed in: nova
Status: New => Incomplete
** Changed in: nova
Status: Incomplete => Invalid
--
You receiv
I am a bit skeptical in ignoring the exception in both cases you described. For
example during the roll_back if we fail calling cinder the risk is that we
leave some open connections between the host and the cinder server, which is
not good.
The same thing could happen during the _post_live_migr
I am not sure if this is a bug, we could replace the dot(s) in the host name
with a different char, for example a "_" but then the user will lose the option
to define a hostname as a FQDN.
And according to the rfc952:
' A "name" (Net, Host, Gateway, or Domain name) is a text string up
to 24 ch
ck infra team
(#openstack-infra on freenode) for help if you need to.
commit fa002925460e70d988d1b4dd1ea594c680a43740
Author: Andrea Rosa
Date: Fri Feb 5 08:31:06 2016 +
Abort an ongoing live migration
This change adds a DELETE call on the server-migrations object to c
I had time to did more investigation and I found that the live migration for
LVM backed instances is not supported:
https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L6665
This change https://review.openstack.org/73387 was for raising the
NotImplementedError exception whe
Public bug reported:
On a multinode devstack installation I have created a new lvm device:
sudo dd if=/dev/zero of=/loopy bs=1M count=5124 # 5gb
sudo losetup /dev/loop2 /loopy
sudo sfdisk /dev/loop2 << EOF
,,8e,,
EOF
sudo pvcreate /dev/loop2
sudo vgcreate encrypted-ephemeral /dev/loop2
Please n
rn_value = theuuid
h.__enter__.return_value = h
return h
return real_open(filename, *args, **kwargs)
mock_open.side_effect = fake_open
self._test_get_guest_config_sysinfo_serial(None)
** Affects: nova
Importance: U
Affects: glance
Importance: Undecided
Assignee: Andrea Rosa (andrea-rosa-m)
Status: New
** Tags: store swift
** Changed in: glance
Assignee: (unassigned) => Andrea Rosa (andrea-rosa-m)
--
You received this bug notification because you are a member of Yahoo!
Engineer
i think this is not a bug but just a configuration issue.
There is a parameter to check the max number of items returned, something like
that:
osapi_opts = [
cfg.IntOpt('osapi_max_limit',
default=1000,
help='the maximum number of items returned in a single '
12 matches
Mail list logo
