/tmp/one not populated if headnode can't ssh to host node
|Assignee:||Daniel Molina||% Done:|
|Target version:||Release 2.0.1|
In the instance when a misconfigured host/worker node is added via 'onehost add blah', an attempt to redistribute the contents of /tmp/one/ doesn't occur. Here's the scenario:
1 - host node is deployed, but authorized_keys2 isn't populated, or the permissions change, or...
2 - 'onehost create <host> im_ vm_ tm' is executed on head node
3 - the problem on the host node is fixed
4 - when the head node successfully is able to ssh to the host node, the software should be redeployed to /tmp/one on the host node.
#3 Updated by Daniel Molina over 10 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
- Resolution set to fixed
We have included a new feature to OpenNebula regarding this issue, you can check it at http://dev.opennebula.org/issues/412.
OpenNebula will check the remote files existence and will copy them if needed. The onehost sync command forces OpenNebula to update the remotes even though they are present in the worker node.