Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

Latest Opensuse update results in " Instance reachability check failed"

0

I updated my Opensuse Tumbleweed via **zypper dup **and now I cannot RDP or SSH into the instance. The Instance status check shows: Instance status checks - Instance reachability check failed: Check failure at 2024/08/27 23:57 GMT-7 (20 minutes). I created a new instance and updated the Opensuse Tumbleweed via zypper and now I cannot connect (via SSH).

Here's the log errors:

[[0;1;38:5:185mDEPEND] Dependency failed for wicked DHCPv4 supplicant service.

[[0;1;38:5:185mDEPEND] Dependency failed for wicked network management service daemon.

[[0;1;38:5:185mDEPEND] Dependency failed for wicked network nanny service.

[[0;1;38:5:185mDEPEND] Dependency failed for wicked AutoIPv4 supplicant service.

[[0;1;38:5:185mDEPEND] Dependency failed for wicked DHCPv6 supplicant service.

[FAILED] Failed to start wicked managed network interfaces.

Topics
Compute
Tags
LinuxAmazon EC2
Language
English
asked a year ago151 views
2 Answers
0

Hi - Try these two knowledge articles :

https://repost.aws/knowledge-center/ec2-linux-status-check-failure-os-errors

https://repost.aws/knowledge-center/ec2-linux-fix-suse-upgrade-errors

answered a year ago
  • Tjisana
    a year ago

    Praveen, thanks for the links - I tried many of the solutions recommended but no luck. I ended up having an old snapshot of a working version of the instance and was able to rebuild my EC2 instance and bring it current. Given that impact of this issue, the best plan going forward is to have a regular snapshot of the last working version of the instance. Nuff said!

0

I’m glad you were able to restore your instance using an old snapshot. Going forward, it's a good idea to implement regular snapshots as part of your update process to ensure you always have a fallback if something goes wrong.

Here are a few key points to keep in mind:

  • Regular Snapshots: Schedule automated snapshots before making any major changes.
  • Test Updates: Always test updates in a staging environment first.
  • Backup Plan: Maintain a retention policy for snapshots to manage storage effectively.

To schedule backups, you can use either Amazon Data Lifecycle Manager or AWS Backup.

For more detailed guidance on handling safe upgrades for SUSE, check out this blog: The Safe SUSE Upgrade: Avoiding Pitfalls When Upgrading AWS Instances.

answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content