Undocumented changes in release notes lead to critical situaiton
|Assignee:||Ruben S. Montero||% Done:|
|Target version:||Release 4.14.2|
|Affected Versions:||OpenNebula 4.14|
We've upgraded from 4.10 to 4.14 and ran into big trouble because of important undocumented changes in opennebula behavior.
The most critical change was related to #3666. We lost bridges used by iscsi client on hosts. The bridge was suppressed because there was no more VM using it but the iscsi client on host side was still using it for disk images of all running VMs ! We also had the same trouble with our NFS network bridge used by VMs AND system datastores.
We had trouble with Xen monitoring because the script started using qemu-img to monitor vm image on hosts without running sudo. In our case, the disk.x file is a symlink to /dev/mapper... block device node (we're using iscsi). This device node is owned by root:disk so we had to add user oneadmin to the disk group.
Lastly, we had to install ipset package on hosts and add /sbin/ipset to sudoers for oneadmin because we discovered the network script started using this tool. We were unable to instantiate new VMs due to this change.
A lot of stress and wasted time could have been avoided with better documentation.
Thanks for caring,