regression-update: systemd init behavior change
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
init-system-helpers (Ubuntu) |
Invalid
|
Critical
|
Unassigned | ||
Xenial |
Invalid
|
Critical
|
Unassigned |
Bug Description
regression-update for 1575572.
After the time 1575572 was checked in we observed a behavior change in the systemd init.
We have been able to repro the issue and can observe that dpkg seems to start docker on “16.04.201605310 Daily”, but not “16.04.201605280 Daily”.
The problem seems to be that in 16.04.201605310
Below are the Contents of the cloud-init, with the 3 docker installation files that fail:
Contents of Cloud-Init, show relationship between Systemd files
#cloud-config
write_files:
- path: /etc/systemd/
permissions: "0644"
content: |
[Unit]
After=
Wants=
[Service]
Type=oneshot
Environment
StandardOut
StandardErr
ExecStartPr
ExecStart=
- path: /etc/systemd/
permissions: "0644"
content: |
[Service]
Restart=always
StartLimitI
RestartqSec=15
ExecStart=
ExecStart=
- path: /etc/systemd/
permissions: "0644"
content: |
[Unit]
PartOf=
[Socket]
ListenStrea
SocketMode=0660
SocketUser=root
SocketGroup
ListenStrea
BindIPv6Onl
[Install]
WantedBy=
runcmd:
- [ ln, -s, /bin/rm, /usr/bin/rm ]
- [ ln, -s, /bin/mkdir, /usr/bin/mkdir ]
- [ ln, -s, /bin/tar, /usr/bin/tar ]
- [ ln, -s, /bin/ln, /usr/bin/ln ]
- [ ln, -s, /bin/cp, /usr/bin/cp ]
- [ ln, -s, /bin/systemctl, /usr/bin/systemctl ]
- [ ln, -s, /bin/mount, /usr/bin/mount ]
- [ ln, -s, /bin/bash, /usr/bin/bash ]
- [ systemctl, stop, resolvconf.service ]
- [ systemctl, disable, resolvconf.service ]
- [ systemctl, stop, lxc-net.service ]
- [ systemctl, disable, lxc-net.service ]
- [ systemctl, mask, lxc-net.service ]
- [ systemctl, start, dcos-docker-
description: | updated |
Changed in init-system-helpers (Ubuntu): | |
assignee: | nobody → Martin Pitt (pitti) |
importance: | Undecided → Critical |
Changed in init-system-helpers (Ubuntu Xenial): | |
assignee: | nobody → Martin Pitt (pitti) |
importance: | Undecided → Critical |
tags: | removed: regression-update |
Changed in init-system-helpers (Ubuntu): | |
status: | Incomplete → Invalid |
Changed in init-system-helpers (Ubuntu Xenial): | |
status: | Incomplete → Invalid |
Changed in init-system-helpers (Ubuntu): | |
assignee: | Martin Pitt (pitti) → nobody |
Changed in init-system-helpers (Ubuntu Xenial): | |
assignee: | Martin Pitt (pitti) → nobody |
This is a direct consequence of bug 1575572. In particular this part:
runcmd: install. service ]
- [ systemctl, start, dcos-docker-
In 16.04 final this was not actually working. I. e. you asked for starting this service, but it wasn't actually started. This got fixed in bug 1575572, so that packages that you install in "packages:" or "runcmd:" (which start services) or direct start requests like your's from above now actually do what you asked it to.
So this is indeed a behaviour change, but I fail to see how it is a regression and not a bug fix? I. e. can you clarify why you would expect docker not to start despite your explicit runcmd to do so?