ngrosc opened a new issue #5686:
URL: https://github.com/apache/cloudstack/issues/5686
##### ISSUE TYPE
* Improvement Request
##### COMPONENT NAME
~~~
cloudstack-sysvmadm
~~~
##### CLOUDSTACK VERSION
~~~
N/A
~~~
##### CONFIGURATION
N/A
##### OS / ENVIRONMENT
Cloudstack running on linux systems
##### SUMMARY
Check filesystem permission before upgrading systemvms
##### 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.
-->
Currently, when issuing the cloudstack-sysvmadm script for upgrading the
systemvms (or doing it manually), the process starts without any prechecks.
When there is somehow an issue with filesystem permissions, the new
systemvm.iso cannot be copied to the new location. It would be a nice
enhancement, when cloudstack had a health check or at least the
cloudstack-sysvmadm script a permission check.
A newly introduced health check could continuously check some relevant
cloudstack metrics, including the filesystem permissions and show a simple
go/nogo somewhere in the admin ui. Or the simple way: a script or the modified
sysvmadm script which checks first all storage paths for the correct rights.
<!-- 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? -->
~~~
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
~~~
--
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]
