I think this needs to be removed from the package, or it will break the ONE setup?
Using 16.04 LTS, installed 5.3.90 and distributed the oneadmin SSH key to all nodes. Now that the final version is out, I tried updating the package from the opennebula repo and I found that on the nodes, when setting up “opennebula-common”, it tries to regenerate the oneadmin SSH key.
In my case, /var/lib/one was an NFS mount with root-squash, so it wasnt allowed to update it, but for other cases (like a local disk for /var/lib/one/.ssh) it will break SSH authentiation for the oneadmin user of the frontend server, right?
Setting up opennebula-common (5.4.0-1) ...
usermod: no changes
Generating public/private rsa key pair.
/var/lib/one/.ssh/id_rsa already exists.
Overwrite (y/n)? y
Your identification has been saved in /var/lib/one/.ssh/id_rsa.
Your public key has been saved in /var/lib/one/.ssh/id_rsa.pub.
oneadmin@hostname
cp: failed to access '/var/lib/one/.ssh/authorized_keys': Permission denied
dpkg: error processing package opennebula-common (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of opennebula-node:
opennebula-node depends on opennebula-common (= 5.4.0-1); however:
Package opennebula-common is not configured yet.
In my case, not overwriting the SSH key (so, answering no) resulted in a broken upgrade of the package, answering yes resulted in “access denied” because of root-squash and NFS.
Shouldnt this SSH key regeneration be removed from the package or am I screwing something up?
Anyone else got this message too? (on ubuntu xenial)
cheers,
Roland