First time here? Check out the FAQ!
2018-03-19 00:48:54 -0500 | received badge | ● Famous Question (source) |
2018-03-07 04:20:02 -0500 | received badge | ● Enthusiast |
2018-03-02 08:42:37 -0500 | received badge | ● Editor (source) |
2018-03-02 05:19:48 -0500 | commented answer | Instance resizing fails when copy swap volume -config error? Thanks TijoV for the link. Unfortunately it does not contain any detailed information how I can modify the config of nova/cinder so that swap volumes are handled in the desired way. Still stuck with instance resizing |
2018-03-02 05:15:29 -0500 | received badge | ● Notable Question (source) |
2018-02-27 06:06:59 -0500 | received badge | ● Popular Question (source) |
2018-02-26 14:52:38 -0500 | answered a question | Instance resizing fails when copy swap volume -config error? Hi there, my cinder.conf look like EDIT: After some further testing around, behavior is obviously dependent of the config item of nova.conf in the libvirt section.In my config, each compute host is in parallel also holding a cinder-volume service based on lvm. My libvirt section in nova.conf looks like ie using the cinder volume group also for nova ephermal disks. This obviously causes nova to create also swap as a lvm volume. If this assumption would be right, why is nova then still searching the swap volume in /var/lib/nova/instances/<uuid> ? Still not found a way how to change that .... EDIT: Further retesting solved this now only for flavors without swap at all. (overlooked that the chosen instance ran on a flavor without swap when testing - sorry) With instances having running on a flavor with swap files, problem ist still persisting. Relevant python code in /usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py is Obviously, the entire recognition of the swap path (fname) is not working in the case of cinder-volumes for swap |
2018-02-26 06:03:22 -0500 | asked a question | Instance resizing fails when copy swap volume -config error? Hi there, running pike in a two compute node test installation with cinder volume and lvm, my installation fails to resize instances to a different flavor. When the instance is created, a cinder volume for swap is created in /dev/cinder-volumes/<uuid>_disk.swap. There is no volume or disk information created in /var/lib/nova/instances, neither for root disk nor for swap. When I then try to resize the instance via horizon, this fails with the error messages, Means: Nova searches the swap disk somewhere in /var/lib/nova/instances instead of the lvm volume group for cinder. As the instance is stopped anyway, why is the swap volume tried to be copied at all instead of recreating it on the new node when starting the instance? I experimented around with the nova config options $state_path and $instances_path and the configs underneath, but this has no effect, the error persists. What make nova-compute search for the volumes in /var/lib/nova? How can I config nova that it should use the cinder volume group and the assigned volume swap in the cinder-volume volume group? Any help is very much appreciated I am looking forward to your reply Best regards Br |
2018-02-25 05:17:05 -0500 | received badge | ● Organizer (source) |