Github user anshul1886 commented on the issue:
https://github.com/apache/cloudstack/pull/1900
@karuturi @koushik-das @sateesh-chodapuneedi , I had analysed those
failures and working on how to go about those. Issue here is that there are
marvin tests which are for something which was never working. But nobody has
reported any bugs for that.
When we create VM without starting it(startvm=false), then there are
issues. So in this scenario if we try to attach the uploaded volume then its
failing in this PR. But in existing code it is passing successfully i.e. DB
entries are created. Now when we start the VM then we are doing nothing for
uploaded Volume and they always remains in uploaded state and not attached to
VM on hypervisor.
This marvin test is there for ages but nobody has reported any issue
regarding this. So I am currently analysing how to go about this. Is this even
used by Users? Because if they were using this then somebody should have
reported this as this was introduced some five years back. I am thinking of
simple solution which would be to inform user that they have to start vm first
(root volume created) before trying to attach volume.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
