When a command or application is updating the system, it locks the dpkg file (Debian package manager). This locking is done so that two processes don’t change the content at the same time as it may lead to an unwarranted situation and a possible broken system. When such a condition occurs, the service script in this case for pf9-kube fails to execute resulting in host convergence failure.
[2020-01-08 13:01:13] All Certs generated successfully
[2020-01-08 13:01:13] E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)
[2020-01-08 13:01:13] E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
2020-01-08 13:01:13,681 - pf9_app.py WARNING - Failed to set service pf9-kube to state True
2020-01-08 13:01:14,810 - session.py INFO - Converge failed
- Platform9 Managed OpenStack - All Versions
We can see that an apt-get purge docker-ce process is running resulting in pf9-kube unable to acquire a lock on the docker installation procedure as part of the pf9-kube script service execution.
pf9@worker01$ ps aux | grep -i apt
root 9270 0.0 2.0 125412 81368 pts/0 T 12:20 0:00 apt-get -y purge docker-ce
pf9 24231 0.0 0.0 14220 936 pts/2 S+ 12:54 0:00 grep --color=auto -i apt
- Force kill the process with SIGKILL signal:
$ sudo kill -9 <process_id>
- On removal of the process, the pf9-kube service completes its execution and the host converges successfully.
2020-01-08 13:01:16,007 - session.py INFO - --- Converging ---
2020-01-08 13:01:18,884 - amqp.py WARNING - Connection closed due to Not specified, retrying in 10 seconds
2020-01-08 13:01:18,885 - pf9_app.py INFO - Setting the desired service state
2020-01-08 13:01:18,885 - pf9_app.py INFO - Setting service state pf9-kube.3.11.0-7457. Command: sudo /etc/init.d/pf9-kube start
2020-01-08 13:03:06,768 - session.py INFO - Converge succeeded