PowerProtect Data Manager: Upgrade Stalls on Docker Network Inspect

Upgrade Process Appears Stalled.

During the PPDM upgrade to 19.22.0-16, the upgrade halts while executing /usr/bin/docker network inspect powerprotect_backend .

• Upgrade logs end with an error indicating an InterruptedException while waiting for the starting components stage.

/var/log/brs/upgrade/upgrademgr.log:
2026-02-05T19:43:02.604Z ERROR [] [upgrademgr-task-executor-1] [][][][TRACE_ID:982ef1c7a91c5444][] com.emc.brs.upgrademgr.service.PuppetRunner - Exception while waiting for starting components stage
java.lang.InterruptedException: sleep interrupted
        at java.base/java.lang.Thread.sleep(Native Method)
        at com.emc.brs.upgrademgr.service.PuppetRunner.threadSleep(PuppetRunner.java:265)
        at com.emc.brs.upgrademgr.service.PuppetRunner.waitForStartingComponentsStage(PuppetRunner.java:279)
        at com.emc.brs.upgrademgr.service.PuppetRunner.run(PuppetRunner.java:122)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:569)
        at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:343)
        at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:699)
        at com.emc.brs.upgrademgr.service.PuppetRunner$$SpringCGLIB$$0.run(<generated>)
        at com.emc.brs.upgrademgr.service.UpgradeRunnable.run(UpgradeRunnable.java:71)
        at com.emc.brs.tracing.api.LogTracingRunnableWrapper.run(LogTracingRunnableWrapper.java:36)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
        at java.base/java.lang.Thread.run(Thread.java:840)
2026-02-05T19:43:02.604Z INFO [] [upgrademgr-task-executor-1] [][][][TRACE_ID:982ef1c7a91c5444][] com.emc.brs.upgrademgr.service.PuppetRunner - Upgrademgr may have been terminated. Stop proceeding.
2026-02-05T19:43:02.632Z INFO [] [SpringApplicationShutdownHook] [][][][][] com.dell.ppdm.iam.event.consumer.ConsumingEventObserverRegistry - Event consumer already stopped.

• The upgrade script log shows “Start waiting for docker network to be ready” with no further progress.

/var/log/brs/upgrade/upgrade_script.log：
2026-02-05T19:42:39.048Z [TRACE_ID:982ef1c7a91c5444] Copying updated schema install jar...
2026-02-05T19:42:39.075Z [TRACE_ID:982ef1c7a91c5444] Creating noop log...
2026-02-05T19:43:01.494Z [TRACE_ID:982ef1c7a91c5444] Return code is 0
2026-02-05T19:43:02.216Z [TRACE_ID:982ef1c7a91c5444] Rebooting appliance
2026-02-05T19:44:56.476Z [TRACE_ID:982ef1c7a91c5444] Start waiting for docker network to be ready

• Process list shows the Docker network inspect command running under the upgrade script.

  admin@ppdm1101:/var/log/brs/upgrade> ps -eaf | grep update
  root       3793      1  0 14:44 ?        00:00:00 /bin/bash /data01/brs/upgrade/update.sh
  root       3794      1  0 14:44 ?        00:00:00 /bin/bash /data01/brs/upgrade/log_format.sh TRACE_ID:982ef1c7a91c5444
  admin     68774  63826  0 21:08 pts/0    00:00:00 grep --color=auto update
  admin@ppdm1101:/var/log/brs/upgrade> ps -eaf | grep 3793
  root       3793      1  0 14:44 ?        00:00:00 /bin/bash /data01/brs/upgrade/update.sh
  root       3967   3793  0 14:44 ?        00:00:00 /usr/bin/docker network inspect powerprotect_backend
  admin     68783  63826  0 21:09 pts/0    00:00:00 grep --color=auto 3793

• Running the command manually returns the expected output, indicating the command itself can complete.

admin@ppdm1101:/var/log/brs/upgrade> /usr/bin/docker network inspect powerprotect_backend
[
    {
        "Name": "powerprotect_backend",
        "Id": "3b7f2cb324905914ad1a20644e100482d88b4ef9c71864e44da4e6ede06b7d4f",
        "Created": "2022-10-27T12:15:14.098168937-04:00",
        "Scope": "local",
        "Driver": "bridge",
        "EnableIPv4": true,
        "EnableIPv6": true,
        "IPAM": {
            "Driver": "default",
            "Options": {},
            "Config": [
                {
                    "Subnet": "x.x.x.x/26",
                    "Gateway": "x.x.x.x"
                },
                {
                    "Subnet": "x:x::/120",
                    "Gateway": "x:x::1"
                }
            ]
        },
        "Internal": false,
        "Attachable": true,
        "Ingress": false,
        "ConfigFrom": {
            "Network": ""
        },
        "ConfigOnly": false,
        "Containers": {},
        "Options": {
            "com.docker.network.bridge.name": "brpp0"
        },
        "Labels": {}
    }
]

Docker daemon start‑up delay causing command blockage

The upgrade process hangs while executing /usr/bin/docker network inspect powerprotect_backend . This occurs because the Docker daemon is still in a starting state, which can happen due to system slowness or network‑related delays. When the daemon has not fully initialized, the docker network inspect command blocks indefinitely, preventing the upgrade script from completing.

The permanent fix is in PPDM 19.22 Patch 1 and later.

If you cannot wait for 19.22 patch 1, contact Dell support to get the updated update.sh script. 

The new update.sh script is modified to wait for the docker daemon. Replace it with the original script /data01/brs/upgrade/update.sh and rerun the upgrade.