Please, describe the problem here and provide additional information below (if applicable) …
We are trying to test OpenNebula upgrade from v5.4.12 to v5.6 Beta (5.5.80) on our testing environment, and all the upgrade proccess seems to run smoothly, but when we try to check oneflow running services or oneflow service templates we allways get this error: [one.document.info] Error getting document [ID]
We’ve tried to edit oneflow-server.conf using almost every possible combination of localhost, the server IP address, 0.0.0.0 on bot :host: and :one_xmlrpc: fields
Versions of the related components and OS (frontend, hypervisors, VMs):
Opennebula 5.5.80 + mariadb-5.5.56-2.el7.x86_64 on same VMware VM on a CentOS 7.4 Steps to reproduce:
Migrate from a working OpenNebula v5.4.12 environment to OpenNebula v5.5.80 beta Current results:
Oneflow not working via Web UI nor CLI Expected results:
As we are doing this upgrade for testing a future upgrade on a production environment, we are going to try the workaround you propose. Could you please indicate how can we remove that LOCKED attribute?
We have found that attribute using oneflow show ID -j but we haven’t been able to update it (json format seems not to be permitted for oneflow update command).