There are two ways to use the command:
1. do-release-upgrade, reboot, juju-updateseries --start-agents
2. do-release-upgrade, juju-updateseries, reboot
Systemd is not really running until the reboot occurs, so starting the agents won't work. Either way is fine, just how you think would be best.
If you run after reboot, but don't use --start-agents, the agents won't be started.
regarding #19, do you have any logs you can show me? i haven't seen that behavior. Are the jujud agent files linked in /etc/systemd/system/multi-user.target.wants/ Can you start them by hand in this case?
regarding #20, is this before or after reboot? I have found that sometimes systemctl status jujud* doesn't give results, which is weird, but systemctl status jujud-machine-0 works... not sure why
@chris.macnaughton,
There are two ways to use the command:
1. do-release-upgrade, reboot, juju-updateseries --start-agents
2. do-release-upgrade, juju-updateseries, reboot
Systemd is not really running until the reboot occurs, so starting the agents won't work. Either way is fine, just how you think would be best.
If you run after reboot, but don't use --start-agents, the agents won't be started.
regarding #19, do you have any logs you can show me? i haven't seen that behavior. Are the jujud agent files linked in /etc/systemd/ system/ multi-user. target. wants/ Can you start them by hand in this case?
regarding #20, is this before or after reboot? I have found that sometimes systemctl status jujud* doesn't give results, which is weird, but systemctl status jujud-machine-0 works... not sure why