Comment 2 for bug 1896617
Revision history for this message
| Vladimir Grevtsev (vlgrevtsev) wrote Re: Creation of image (or live snapshot) from the existing VM fails if libvirt-image-backend is configured to qcow2 | #2 |
Can confirm that this issue is NOT reproducible on Bionic/Stein, will test on Bionic/Train now.
$ juju config nova-compute-kvm openstack-origin
cloud:bionic-stein
$ juju config nova-compute-kvm libvirt-
qcow2
$ os server list -f yaml
- Flavor: m1.tiny
ID: 3612ca0d-
Image: cirros
Name: demo
Networks: internal=
Status: ACTIVE
$ os server image create --wait demo -f yaml
checksum: null
container_format: null
created_at: '2020-09-
disk_format: null
file: /v2/images/
id: ceca0c58-
min_disk: 1
min_ram: 0
name: demo
owner: 9a163a46437c441
properties:
base_image_ref: 531d4af1-
boot_roles: Admin,member,reader
image_type: snapshot
instance_uuid: 3612ca0d-
locations: []
os_hash_algo: null
os_hash_value: null
os_hidden: false
owner_
owner_user_name: admin
user_id: 6b88aca2425c452
protected: false
schema: /v2/schemas/image
size: null
status: queued
tags: []
updated_at: '2020-09-
virtual_size: null
visibility: private
ubuntu@node06:~$ dpkg -l | grep nova
ii nova-api-metadata 2:19.3.
ii nova-common 2:19.3.
ii nova-compute 2:19.3.
ii nova-compute-kvm 2:19.3.
ii nova-compute-
ii python3-nova 2:19.3.
ii python3-novaclient 2:13.0.
ubuntu@node06:~$ dpkg -l | grep libvirt
ii libvirt-clients 5.0.0-1ubuntu2.
ii libvirt-daemon 5.0.0-1ubuntu2.
ii libvirt-
ii libvirt-
ii libvirt0:amd64 5.0.0-1ubuntu2.
ii nova-compute-
ii python3-libvirt 5.0.0-1~cloud0 amd64 libvirt Python 3 bindings
ubuntu@node06:~$