Description
When performing an upgrade of OpenNebula, the new packages place files with stock permissions, replacing the existing ones. Normally, this is not a problem but when serving Sunstone, on apache, certain filesystem permissions need to be set such that the apache user can run Sunstone. When the upgrade is performed, naturally "these files" will get their permission "reset" and the user will run into this problem
[Mon Feb 14 11:10:09.133702 2022] [core:error] [pid 668659:tid 140354620548864] [client 10.141.18.116:60062] AH00037: Symbolic link not allowed or link target not accessible: /usr/lib/one/sunstone/public/dist/main.js, referer:
2 tasks must be performed
[ ] detect if sunstone is being served by apache and ensure required permissions at the package install scripts level
[ ] add a note on the upgrade section for the user to make sure that this requirement is met
Use case
Having this problem effectively disables the Web interface for users with large deployments when an upgrade is performed. Automatically handling/noting this case during an upgrade will result in less panic overall.
Description When performing an upgrade of OpenNebula, the new packages place files with stock permissions, replacing the existing ones. Normally, this is not a problem but when serving Sunstone, on apache, certain filesystem permissions need to be set such that the apache user can run Sunstone. When the upgrade is performed, naturally "these files" will get their permission "reset" and the user will run into this problem
2 tasks must be performed
Use case Having this problem effectively disables the Web interface for users with large deployments when an upgrade is performed. Automatically handling/noting this case during an upgrade will result in less panic overall.
Progress Status