Skip to content
This repository has been archived by the owner on Jul 2, 2024. It is now read-only.

SCMI installation with systemd manager option fails on CoreOS/Ubuntu hosts. #757

Open
jdeathe opened this issue Mar 3, 2019 · 1 comment
Labels

Comments

@jdeathe
Copy link
Owner

jdeathe commented Mar 3, 2019

This issue is only known to effect CoreOS and Ubuntu hosts it does not effect any of the EL based hosts such as CentOS-7, Centos Atomic Host.

Docker host environment details used to replicate this issue

Environment 1.

NAME="Container Linux by CoreOS"
VERSION=2023.4.0

Environment 2 (inc. Docker CE).

NAME="Ubuntu" 
VERSION="18.04.2 LTS (Bionic Beaver)"

When scmi attempts to run systemctl commands in the chroot that allows the container to run commands on the host the following error is returned.

Failed to connect to bus: No data available

To reproduce:

$ docker run --rm \
  --privileged \
  --volume /:/media/root \
  jdeathe/centos-ssh:2.5.1 \
    /usr/sbin/scmi -i -c /media/root -m systemd -t 2.5.1 -n ssh.1

Expected outcome:
Install should complete successfully with the message "Install complete"

Actual outcome:

WARNING: No swap limit support
---> Installing ssh@1.service
 ---> Installing template unit-file: /media/root/etc/systemd/system/ssh@.service
 ---> Populating drop-in: /media/root/etc/systemd/system/ssh@.service.d/10-override.conf
 ---> Removing template unit-file: /media/root/etc/systemd/system/ssh.register@.service
 ---> Removing /media/root/etc/systemd/system/ssh.register@.service.d
Failed to connect to bus: No data available
 ---> Enabling ssh@1.service
Failed to connect to bus: No data available
Failed to connect to bus: No data available
 ---> Releasing host mounted container
WARNING: No swap limit support
 ---> Restarting ssh@1.service
-- Logs begin at Thu 2019-02-28 09:04:59 UTC. --
Failed to connect to bus: No data available
Failed to connect to bus: No data available
 ---> Install error
        Review the status for additonal information: systemctl status ssh@1.service
@jdeathe jdeathe added the bug label Mar 3, 2019
@jdeathe
Copy link
Owner Author

jdeathe commented Mar 3, 2019

Work-around could be to install locally from a source image:

$ docker run --rm --detach --name scmi-src jdeathe/centos-ssh:2.5.1 sleep infinity
$ sudo docker cp scmi-src:/etc/systemd/system /etc/systemd/
$ sudo docker cp scmi-src:/usr/sbin/scmi /usr/local/sbin/
$ sudo docker cp scmi-src:/opt/scmi /opt/
$ docker rm -f scmi-src
$ sudo chmod +x /usr/local/sbin/scmi
$ sudo -E scmi -i -m systemd --register -t 2.5.1 -n ssh.1

Or, after running the scmi installation, complete the installation manually:

$ sudo systemctl daemon-reload
$ sudo systemctl enable -f ssh@1.service
$ sudo systemctl start ssh@1.service

@jdeathe jdeathe changed the title SCMI installation with systemd manager option fails on Ubuntu hosts. SCMI installation with systemd manager option fails on CoreOS/Ubuntu hosts. Mar 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant