You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by "vladimirpetrov (via GitHub)" <gi...@apache.org> on 2023/09/18 15:40:12 UTC
[GitHub] [cloudstack] vladimirpetrov opened a new issue, #7970: After force deleting a deploy-as-is template, the VMs using it cannot start
vladimirpetrov opened a new issue, #7970:
URL: https://github.com/apache/cloudstack/issues/7970
<!--
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.
-->
~~~
API, UI
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main branch.
-->
~~~
4.18.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
-->
N/A
##### SUMMARY
<!-- Explain the problem/feature briefly -->
If a deploy-as-is template (VMWare vApp, for example) is removed using 'Force delete', the VMs using it won't be able to start properly because the details in the 'template_deploy_as_is_details' are removed.
##### 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 -->
~~~
Register a deploy-as-is template (enabling the Read VM settings from OVA ), start a VM with this template, then remove the template using 'Force delete' and stop/start the VM.
~~~
<!-- 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 VM starts normally.
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
The VM cannot start.
~~~
--
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: commits-unsubscribe@cloudstack.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] After force deleting a deploy-as-is template, the VMs using it cannot start [cloudstack]
Posted by "harikrishna-patnala (via GitHub)" <gi...@apache.org>.
harikrishna-patnala commented on issue #7970:
URL: https://github.com/apache/cloudstack/issues/7970#issuecomment-1768072089
had a discussion with @weizhouapache, going with the solution to keep the template details after it is deleted.
--
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: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] After force deleting a deploy-as-is template, the VMs using it cannot start [cloudstack]
Posted by "harikrishna-patnala (via GitHub)" <gi...@apache.org>.
harikrishna-patnala commented on issue #7970:
URL: https://github.com/apache/cloudstack/issues/7970#issuecomment-1767965936
@weizhouapache the problem is with this line
String value = property.isPassword() ? DBEncryptionUtil.decrypt(detail.getValue()) : detail.getValue();
where we are checking if the property is a password.
I'm thinking to add a new column something like "is_password" to the table "user_vm_deploy_as_is_details", this will remove the dependency on the template.
As an alternative as you said we can keep the template deploy as is details but thinking if it will keep those entries always in the database.
What you say ?
--
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: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [cloudstack] weizhouapache commented on issue #7970: After force deleting a deploy-as-is template, the VMs using it cannot start
Posted by "weizhouapache (via GitHub)" <gi...@apache.org>.
weizhouapache commented on issue #7970:
URL: https://github.com/apache/cloudstack/issues/7970#issuecomment-1724908203
> Vladi, I think if you use force delete you have the intention and thought about it. What would you expect to happen? I think for the VM to just keep working is not what the force delete functionality is for.
I think the deploy-as-it details of template should be kept.
--
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: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] After force deleting a deploy-as-is template, the VMs using it cannot start [cloudstack]
Posted by "JoaoJandre (via GitHub)" <gi...@apache.org>.
JoaoJandre closed issue #7970: After force deleting a deploy-as-is template, the VMs using it cannot start
URL: https://github.com/apache/cloudstack/issues/7970
--
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: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [cloudstack] DaanHoogland commented on issue #7970: After force deleting a deploy-as-is template, the VMs using it cannot start
Posted by "DaanHoogland (via GitHub)" <gi...@apache.org>.
DaanHoogland commented on issue #7970:
URL: https://github.com/apache/cloudstack/issues/7970#issuecomment-1724874375
Vladi, I think if you use force delete you have the intention and thought about it. What would you expect to happen? I think for the VM to just keep working is not what the force delete functionality is for.
--
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: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] After force deleting a deploy-as-is template, the VMs using it cannot start [cloudstack]
Posted by "JoaoJandre (via GitHub)" <gi...@apache.org>.
JoaoJandre commented on issue #7970:
URL: https://github.com/apache/cloudstack/issues/7970#issuecomment-1881368303
Closing as this was fixed by #8115
--
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: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org