do-release-upgrade warning
Greetings, I've gotten the upgrade available to 22.04.03 on my ubuntu ec2 instance. when i use the command sudo do-release-upgrade, i get a screen that says: This session appears to be running under ssh. It is not recommended to perform a upgrade over ssh currently because in case of failure it is harder to recover.
Since there no other way in besides SSH, should I ignore this warning? I can take a snapsshot so if it does indeed blow up, snapshot to the rescue but I'm just wondering what the proper process with respect to keeping a EC2 instance current.
Thanks, Rick
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
You can consider EC2 Instance Connect https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/connect-linux-inst-eic.html
Your version of Ubuntu whould have it already installed https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-connect-prerequisites.html#eic-prereqs-amis
Sessions Manager is another option https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/session-manager-to-linux.html https://ubuntu.com/tutorials/how-to-use-aws-ssm-session-manager-for-accessing-ubuntu-pro-instances
Although make sure it's properly setup before you start the do-release-upgrade https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager-getting-started.html
It's always wise to take a snapshot before making any major changes, no matter what method(s) of access are available to you.
Doing a snapshot before upgrading is a good practice. During upgrade process, there may be disruptions to network. This will affect your SSH connection.
If you are running a Nitro instance, you can use EC2 serial console.
For more info, refer to blog Using the EC2 Serial Console to access the Microsoft Server boot manager to fix and debug boot failures
I'm not using Nitro but I was able to do this using Sessions Manager. I did the snapshot anyway as their cheap insurance. Thanks for the reply and suggestions.
Relevanter Inhalt
AWS OFFICIALAktualisiert vor einem Jahr- AWS OFFICIALAktualisiert vor 7 Monaten
- AWS OFFICIALAktualisiert vor 3 Jahren
It may not be possible to use it depending on the instance type you are using with EC2, but if you are unable to use SSH, you can also troubleshoot the problem using the serial console. https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-serial-console-prerequisites.html
@steve_m, EC2 Instane will give you the same message so that's not an option but the new -n- improved Sessions Manger is a winner. Thanks for the quick response.
Yeah, thinking about it some more EC2 Instance Connect relies on SSH under the hood, so it's not a surprise the same message comes up.
Systems Manager is the way to go, with a snapshot as a fallback.