Skip to main content
NetApp Knowledge Base

Console Agent install fails on RHEL 9.6 due to Podman subnet conflict

Views:
13
Visibility:
Public
Votes:
0
Category:
cloud-manager
Specialty:
cloud
Last Updated:

Applies to

  • NetApp Console Agent v4.2.0
  • Red Hat Enterprise Linux (RHEL) 9.6
  • Microsoft Azure Virtual Machines
  • Podman container runtime

Issue

  • NetApp Console Agent v4.2.0 installation fails on a RHEL 9.6 Azure VM.
  • Service Manager remains unreachable during installation.
  • Installation logs show timeout errors when attempting to start required containers.
  • Podman fails to create container networks due to a subnet conflict.

        Console installation command output :

       [✖] Waiting for Service Manager to come online, It may take few minutes Timed out waiting for   http://localhost/service-manager/isHealthy
       connect ECONNREFUSED 127.0.0.1:80
       Installation failed, further info can be found on: /tmp/installer-2026-xx-xxT80807.log
       # systemctl status netapp-service-manager.service
       ● netapp-service-manager.service - Netapp Service Manager
            Loaded: loaded (/usr/lib/systemd/system/netapp-service-manager.service; enabled; preset: disabled)
            Active: active (running) since Fri 2026-01-09 08:08:27 UTC; 12min ago
          Main PID: 4960 (sm2)
             Tasks: 10 (limit: 203227)
            Memory: 79.9M
               CPU: 1min 22.920s
            CGroup: /system.slice/netapp-service-manager.service
                    └─4960 /opt/application/netapp/service-manager-2/sm2
       Jan 09 08:19:16 rhel-20260109 sm2[4960]:   File "/usr/lib/python3.9/site-packages/podman_compose.py", line 1571, in output
       Jan 09 08:19:16 rhel-20260109 sm2[4960]:     raise subprocess.CalledProcessError(p.returncode, " ".join(cmd_ls), stderr_data)
       Jan 09 08:19:16 rhel-20260109 sm2[4960]: subprocess.CalledProcessError: Command 'podman network create --label io.podman.compose.project=service-manager-2 --label com.docker.compose.p>
       Jan 09 08:19:16 rhel-20260109 sm2[4960]: 2026-01-09T08:19:16.235Z error: docker-compose up failed with status 1
       Jan 09 08:19:16 rhel-20260109 sm2[4960]: 2026-01-09T08:19:16.236Z error: Error: docker-compose up failed with status 1
       Jan 09 08:19:16 rhel-20260109 sm2[4960]:     at sendAuditMsgsForContainer (/snapshot/sm2dist/bundle.js)
       Jan 09 08:19:16 rhel-20260109 sm2[4960]:     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
       Jan 09 08:19:16 rhel-20260109 sm2[4960]:     at async mainLoop (/snapshot/sm2dist/bundle.js)
       Jan 09 08:19:16 rhel-20260109 sm2[4960]:     at async /snapshot/sm2dist/bundle.js
       Jan 09 08:20:00 rhel-20260109 sm2[4960]: 2026-01-09T08:20:00.104Z warn: No container found for podman runtime

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.