Error in one-context-force status after one-context install on Debian 10

Community Support
1

Dear All,
This is not a new problem as it has been flagged before in earlier versions, see this link

I have created a new image doing a routine installation cycle from an Debian 10.1 ISO (from debian.org).
I then installed one-context_5.8.0-1.deb, saved the disk as described in the docs. On creating a new VM from this image, I am seeing an error in the output during booting…

[FAILED]  Failed to start OpenNebula forced reconfiguration.
See 'systemctl status one-context-force.service' for details.

To get more information on the error, I added the following lines to /usr/sbin/one-context-run…

else
    echo 'Contextualization must start first as a boot service' >&2
    echo '################ problem here ################'
    echo ''
    pwd
    ls -l $(dirname ${CONTEXT_BASE}) >&2
    echo ''
    exit 1
fi

This gave the following output from systemctl status one-context-force

root@vmXXX:~# systemctl status one-context-force
● one-context-force.service - OpenNebula forced reconfiguration
   Loaded: loaded (/lib/systemd/system/one-context-force.service; disabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2019-09-30 11:10:47 IST; 1min 10s ago
  Process: 378 ExecStart=/usr/sbin/one-context-run force (code=exited, status=1/FAILURE)
 Main PID: 378 (code=exited, status=1/FAILURE)

Sep 30 11:10:47 vmaXXX systemd[1]: Starting OpenNebula forced reconfiguration...
Sep 30 11:10:47 vmaXXX one-context-run[378]: Contextualization must start first as a boot service
Sep 30 11:10:47 vmaXXX one-context-run[378]: ################ problem here ################
Sep 30 11:10:47 vmaXXX one-context-run[378]: /
Sep 30 11:10:47 vmaXXX one-context-run[378]: ls: cannot access '/var/run/one-context': No such file or directory
Sep 30 11:10:47 vmaXXX systemd[1]: one-context-force.service: Main process exited, code=exited, status=1/FAILURE
Sep 30 11:10:47 vmaXXX systemd[1]: one-context-force.service: Failed with result 'exit-code'.
Sep 30 11:10:47 vmaXXX systemd[1]: Failed to start OpenNebula forced reconfiguration

My system is…
OpenNebula 5.6.1
Frontend is…
Debian GNU/Linux 9.8 (stretch) 4.9.0-8-amd64 #1 SMP Debian 4.9.144-3.1 (2019-02-19) x86_64 GNU/Linux

Is this expected, or is there a fix available for it. I am looking to use context for simple username and network configuration,

regards,
Peter

2

Update, this problem has been resolved. Although it had a similar manifestation to a previous problem, it was caused by a systemd problem on the VM image, not related to the use of the one-context package.