wornet-mwo opened a new issue, #9176:
URL: https://github.com/apache/cloudstack/issues/9176

   <!--
   Verify first that your issue/request is not already reported on GitHub.
   Also test if the latest release and main branch are affected too.
   Always add information AFTER of these HTML comments, but no need to delete 
the comments.
   -->
   
   ##### ISSUE TYPE
   <!-- Pick one below and delete the rest -->
    * Bug Report
   
   ##### COMPONENT NAME
   <!--
   Categorize the issue, e.g. API, VR, VPN, UI, etc.
   -->
   ~~~
   STORAGE
   ~~~
   
   ##### CLOUDSTACK VERSION
   <!--
   New line separated list of affected versions, commit ID for issues on main 
branch.
   -->
   
   ~~~
   4.19.0.1
   ~~~
   
   ##### CONFIGURATION
   <!--
   Information about the configuration if relevant, e.g. basic network, 
advanced networking, etc.  N/A otherwise
   -->
   N/A
   
   ##### OS / ENVIRONMENT
   <!--
   Information about the environment if relevant, N/A otherwise
   -->
   * KVM/libvirt as Virtualization is used
   * linstor as primary storage is required
   
   
   ##### SUMMARY
   <!-- Explain the problem/feature briefly -->
   Volumes attached to instances created in a primary storage backed by linstor 
are set to format `QCOW2`. That leads to unmigratable Instances.
   
   ##### STEPS TO REPRODUCE
   <!--
   For bugs, show exactly how to reproduce the problem, using a minimal 
test-case. Use Screenshots if accurate.
   
   For new features, show how the feature would be used.
   -->
   * install a linstor storage as primary storage
   * create instance using a storage offering which guarantees usage of linstor 
(with tags)
   * find volume in database
   * column `format` is set to `QCOW2` instead of `RAW` (drbd devices are raw 
by definition)
   * (optional: try to migrate the instance to another storage e.g. an nfs -> 
fails because of wrong qemu-img parameters)
   
   <!-- Paste example playbooks or commands between quotes below -->
   ~~~
   
   ~~~
   
   <!-- You can also paste gist.github.com links for larger files -->
   
   ##### EXPECTED RESULTS
   <!-- What did you expect to happen when running the steps above? -->
   
   ~~~
   The correct format is used, when creating an instance.
   ~~~
   
   ##### ACTUAL RESULTS
   <!-- What actually happened? -->
   The migration of an instance from a linstor to nfs storage failed. The 
failed command pointed me to the database. Migrating an instance to the linstor 
storage works great and does not cause the issue, only creating an instance is 
affected.
   
   <!-- Paste verbatim command output between quotes below -->
   ~~~
   root@rz0-vh01:~# zgrep qemu-img 
/var/log/cloudstack/agent/agent.log.2024-06-04.gz
   2024-06-04 10:04:56,779 WARN  [utils.script.Script] 
(agentRequest-Handler-4:null) (logid:0af75212) Execution of process [28987] for 
command [qemu-img convert -O qcow2 -U --image-opts 
driver=qcow2,file.filename=/dev/drbd1001 
/mnt/f8a61f1d-8644-31f2-a519-83ac3f94c267/eaf6e6cb-50c9-4cb0-9368-e757fa488d79.qcow2
 ] failed.
   2024-06-04 10:04:56,779 WARN  [utils.script.Script] 
(agentRequest-Handler-4:null) (logid:0af75212) Process [28987] for command 
[qemu-img convert -O qcow2 -U --image-opts 
driver=qcow2,file.filename=/dev/drbd1001 
/mnt/f8a61f1d-8644-31f2-a519-83ac3f94c267/eaf6e6cb-50c9-4cb0-9368-e757fa488d79.qcow2
 ] encountered the error: [qemu-img: Could not open 
'driver=qcow2,file.filename=/dev/drbd1001': Image is not in qcow2 format].
   2024-06-04 10:04:56,780 ERROR [kvm.storage.LibvirtStorageAdaptor] 
(agentRequest-Handler-4:null) (logid:0af75212) Failed to convert /dev/drbd1001 
to 
/mnt/f8a61f1d-8644-31f2-a519-83ac3f94c267/eaf6e6cb-50c9-4cb0-9368-e757fa488d79.qcow2
 the error was: qemu-img: Could not open 
'driver=qcow2,file.filename=/dev/drbd1001': Image is not in qcow2 format
   ~~~
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to