Public bug reported:
We upgraded some baremetal machines from bionic to focal. During the
d-r-u process, it got stuck when it tried to restart systemd-
networkd.service [0]. This also caused the machine to be unreachable
through ssh. The only way to work around this issue was to have an
existing ssh session on the machine during the upgrade. Then, I was able
to restart systemd-networkd.socket and systemd-networkd.service to get
things working again; this unstuck the d-r-u process. Additionally, I
had to restart sshd for that service to work as well. Other services
listening on other ports worked fine. This was a juju unit, and "juju
run --machine $num" worked to issue commands remotely on the machine.
[0]
Created symlink /etc/systemd/system/sysinit.target.wants/systemd-pstore.service
/lib/systemd/system/systemd-pstore.service.
Job for systemd-networkd.service failed because the control process exited with
error code.
See "systemctl status systemd-networkd.service" and "journalctl -xe" for
details.
** Affects: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
We upgraded some baremetal machines from bionic to focal. During the
d-r-u process, it got stuck when it tried to restart systemd-
networkd.service [0]. This also caused the machine to be unreachable
- through ssh. The only way to avoid this issue was to have an existing
- ssh session on the machine during the upgrade. Then, I was able to
- restart systemd-networkd.socket and systemd-networkd.service to get
+ through ssh. The only way to work around this issue was to have an
+ existing ssh session on the machine during the upgrade. Then, I was able
+ to restart systemd-networkd.socket and systemd-networkd.service to get
things working again; this unstuck the d-r-u process. Additionally, I
had to restart sshd for that service to work as well. Other services
listening on other ports worked fine as well. This was a juju unit, and
"juju run --machine $num" worked to issue commands remotely on the
machine.
- [0]
+ [0]
Created symlink
/etc/systemd/system/sysinit.target.wants/systemd-pstore.service
/lib/systemd/system/systemd-pstore.service.
Job for systemd-networkd.service failed because the control process exited
with error code.
See "systemctl status systemd-networkd.service" and "journalctl -xe" for
details.
** Description changed:
We upgraded some baremetal machines from bionic to focal. During the
d-r-u process, it got stuck when it tried to restart systemd-
networkd.service [0]. This also caused the machine to be unreachable
through ssh. The only way to work around this issue was to have an
existing ssh session on the machine during the upgrade. Then, I was able
to restart systemd-networkd.socket and systemd-networkd.service to get
things working again; this unstuck the d-r-u process. Additionally, I
had to restart sshd for that service to work as well. Other services
- listening on other ports worked fine as well. This was a juju unit, and
- "juju run --machine $num" worked to issue commands remotely on the
- machine.
+ listening on other ports worked fine. This was a juju unit, and "juju
+ run --machine $num" worked to issue commands remotely on the machine.
[0]
Created symlink
/etc/systemd/system/sysinit.target.wants/systemd-pstore.service
/lib/systemd/system/systemd-pstore.service.
Job for systemd-networkd.service failed because the control process exited
with error code.
See "systemctl status systemd-networkd.service" and "journalctl -xe" for
details.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929774
Title:
do-release-upgrade hangs when systemd-networkd.service fails to
restart cleanly; causes sshd issues
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1929774/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
