You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by GitBox <gi...@apache.org> on 2020/10/22 09:02:39 UTC
[GitHub] [cloudstack] borisstoyanov opened a new issue #4421: migratevmwithvolume api migrates both disks when you point just one of them
borisstoyanov opened a new issue #4421:
URL: https://github.com/apache/cloudstack/issues/4421
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and master 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.
-->
~~~
Migration
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on master branch.
-->
~~~
seen in 4.14 maybe older as well
~~~
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
VMware
##### SUMMARY
<!-- Explain the problem/feature briefly -->
##### 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.
-->
<!-- Paste example playbooks or commands between quotes below -->
~~~
1. Create a VM with data disk
2. Use migrateVMwithVolume api and migrate the vm to another host with just one of the volumes
~~~
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
VM migrated with just one of the volumes
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
Cloudstack migrates both the Volumes but then marks only one of them migrated
~~~
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [cloudstack] DaanHoogland closed issue #4421: migratevmwithvolume api migrates both disks when you point just one of them
Posted by GitBox <gi...@apache.org>.
DaanHoogland closed issue #4421:
URL: https://github.com/apache/cloudstack/issues/4421
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [cloudstack] borisstoyanov commented on issue #4421: migratevmwithvolume api migrates both disks when you point just one of them
Posted by GitBox <gi...@apache.org>.
borisstoyanov commented on issue #4421:
URL: https://github.com/apache/cloudstack/issues/4421#issuecomment-729539035
yes, thanks @rhtyd
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [cloudstack] harikrishna-patnala commented on issue #4421: migratevmwithvolume api migrates both disks when you point just one of them
Posted by GitBox <gi...@apache.org>.
harikrishna-patnala commented on issue #4421:
URL: https://github.com/apache/cloudstack/issues/4421#issuecomment-730138585
Figured out the issue @rhtyd , testing all the scenarios now with a fix. I'll raise a PR soon
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [cloudstack] shwstppr commented on issue #4421: migratevmwithvolume api migrates both disks when you point just one of them
Posted by GitBox <gi...@apache.org>.
shwstppr commented on issue #4421:
URL: https://github.com/apache/cloudstack/issues/4421#issuecomment-714351924
@borisstoyanov just confirming, the destination host where VM was migrated had access to storage pool of volume that shouldn't be migrated?
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [cloudstack] borisstoyanov commented on issue #4421: migratevmwithvolume api migrates both disks when you point just one of them
Posted by GitBox <gi...@apache.org>.
borisstoyanov commented on issue #4421:
URL: https://github.com/apache/cloudstack/issues/4421#issuecomment-729528651
@harikrishna-patnala this is not acceptable since we end up with inconsistency between VMware and Cloudstack. As you see in vCenter the volumes are on vvol5, but Cloudstack shows one of the volumes on vvol5 and the other on vvlo4.
I'm pretty sure if you try to do something with that volume will result in failure since cloudstack will not find it.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [cloudstack] harikrishna-patnala commented on issue #4421: migratevmwithvolume api migrates both disks when you point just one of them
Posted by GitBox <gi...@apache.org>.
harikrishna-patnala commented on issue #4421:
URL: https://github.com/apache/cloudstack/issues/4421#issuecomment-729546366
@borisroman I thought you identified some problem in choosing the storage pools by management server. I've got the issue now being inconsistency with storage pool mapping between CloudStack and vCenter. I'll have a look.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [cloudstack] Spaceman1984 commented on issue #4421: migratevmwithvolume api migrates both disks when you point just one of them
Posted by GitBox <gi...@apache.org>.
Spaceman1984 commented on issue #4421:
URL: https://github.com/apache/cloudstack/issues/4421#issuecomment-729512285
Should we close this issue as expected behavior?
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [cloudstack] rhtyd commented on issue #4421: migratevmwithvolume api migrates both disks when you point just one of them
Posted by GitBox <gi...@apache.org>.
rhtyd commented on issue #4421:
URL: https://github.com/apache/cloudstack/issues/4421#issuecomment-720325982
cc @Spaceman1984
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [cloudstack] DaanHoogland commented on issue #4421: migratevmwithvolume api migrates both disks when you point just one of them
Posted by GitBox <gi...@apache.org>.
DaanHoogland commented on issue #4421:
URL: https://github.com/apache/cloudstack/issues/4421#issuecomment-726075951
@borisstoyanov what is your expectation of the 'non'-migrated disks? should these still be attached? how about cross cluster migrations? is it even allowed to migrate with less than all disks?
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [cloudstack] shwstppr edited a comment on issue #4421: migratevmwithvolume api migrates both disks when you point just one of them
Posted by GitBox <gi...@apache.org>.
shwstppr edited a comment on issue #4421:
URL: https://github.com/apache/cloudstack/issues/4421#issuecomment-714351924
@borisstoyanov just confirming, the destination host where VM was migrated had access to the original storage pool of volume that shouldn't be migrated?
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [cloudstack] borisstoyanov commented on issue #4421: migratevmwithvolume api migrates both disks when you point just one of them
Posted by GitBox <gi...@apache.org>.
borisstoyanov commented on issue #4421:
URL: https://github.com/apache/cloudstack/issues/4421#issuecomment-714407308
Yes, I've reproduced this with hosts/storage on the same cluster, also with cluster vs zone scope storage. Doesn't seem to matter.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [cloudstack] Spaceman1984 commented on issue #4421: migratevmwithvolume api migrates both disks when you point just one of them
Posted by GitBox <gi...@apache.org>.
Spaceman1984 commented on issue #4421:
URL: https://github.com/apache/cloudstack/issues/4421#issuecomment-729494516
Taking a look
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [cloudstack] rhtyd commented on issue #4421: migratevmwithvolume api migrates both disks when you point just one of them
Posted by GitBox <gi...@apache.org>.
rhtyd commented on issue #4421:
URL: https://github.com/apache/cloudstack/issues/4421#issuecomment-730015272
@harikrishna-patnala any update on this?
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [cloudstack] harikrishna-patnala edited a comment on issue #4421: migratevmwithvolume api migrates both disks when you point just one of them
Posted by GitBox <gi...@apache.org>.
harikrishna-patnala edited a comment on issue #4421:
URL: https://github.com/apache/cloudstack/issues/4421#issuecomment-729546366
@borisstoyanov I thought you identified some problem in choosing the storage pools by management server. I've got the issue now being inconsistency with storage pool mapping between CloudStack and vCenter. I'll have a look.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [cloudstack] harikrishna-patnala commented on issue #4421: migratevmwithvolume api migrates both disks when you point just one of them
Posted by GitBox <gi...@apache.org>.
harikrishna-patnala commented on issue #4421:
URL: https://github.com/apache/cloudstack/issues/4421#issuecomment-729507142
@borisroman @DaanHoogland
I think the reason for this behaviour is the Volume is tried to migrate to a storage pool (vvol5-zone) which is at zone level.
I observed the following from and code and also tested
All the volumes will be migrated to target storage pool (even though not all volumes are selected to migrate)
1. if the target storage pool is with Zone scope
2. if the target storage pool and host is in different cluster (across cluster migration)
So I feel this is expected to keep all the volumes in same cluster storage pool or zone level pool.
If the same scenario is tried with in cluster storage pool, then only selected volume will be migrated to target storage pool (other volumes will still remain on old storage pool)
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [cloudstack] rhtyd commented on issue #4421: migratevmwithvolume api migrates both disks when you point just one of them
Posted by GitBox <gi...@apache.org>.
rhtyd commented on issue #4421:
URL: https://github.com/apache/cloudstack/issues/4421#issuecomment-729533266
@borisstoyanov do you think the severity should be bumped for this issue?
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org