You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Check filesystem permission before upgrading systemvms
STEPS TO REPRODUCE
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.
EXPECTED RESULTS
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered:
ISSUE TYPE
COMPONENT NAME
CLOUDSTACK VERSION
CONFIGURATION
N/A
OS / ENVIRONMENT
Cloudstack running on linux systems
SUMMARY
Check filesystem permission before upgrading systemvms
STEPS TO REPRODUCE
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.
EXPECTED RESULTS
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: