Skip to main content
NetApp Knowledge Base

BlueXP Connector containers does not start after VM reboot

  1. Last updated
    Mar 11, 2025
  2. Save as PDF
Views:
12
Visibility:
Public
Votes:
0
Category:
cloud-manager
Specialty:
bluexp
Last Updated:
3/11/2025, 3:35:33 PM

Applies to

  • BlueXP
  • Connector running on RHEL 9.X

Issue

  • BlueXP Connector lost connectivity to the SaaS layer
  • After VM reboot, the containers are not started automatically at boot and when trying to start the container with command podman start --all the error below is returned:
    cannot stat `/run/systemd/resolve/resolv.conf`: No such file or directory: OCI runtime attempted to invoke a command that was not found

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.