Loading...
Loading...
Azure NetWorker Virtual Edition (NVE) OS rollup fails while performing task "Pre-Actions Before Install Operating System Security Patches with selected SuSE (8 of 18)." The NVE's /data01/avamar/repo/temp/*/tmp/workflow.log reports: 2025-07-09 15:38:35 (-0400) 47017683049120 INFO: "uname -a", exit status=0 (success) 2025-07-09 15:38:35 (-0400) 47017683049120 INFO: os=unknown version=unknown update=unknown arch=x86_64 ... 2025-07-09 15:38:35 (-0400) 47017683049120 ERROR: - One or more nodes are not running SLES failed
NOTE: The NVE rollup can fail with "One or more nodes are not running SLES" for various reasons. This article focuses on a specific scenario for Azure NVE deployments. The sshd_config file on the NVE does not contain the NVE's IP address in the " Match user root address " settings, so root SSH commands fail to validate the NVEs authenticity. If this does not apply, see the Additional Information section for other known causes of this failure. Brief Summary: The IP address of the NVE has changed from its initial deployment. By default, Azure NVE blocks root SSH access if the connecting IP is not listed. This behavior comes from a conditional rule in its SSH configuration. Because the IP address has changed from the initial deployment, the IP does not match what is configured in the SSH configuration. This causes the failure observed during the rollup. Explanation: At the start of the workflow, it checks to see if the /usr/local/avamar/var/probe.xml file exists. This file is created during deployment of the NVE and contains the IP address the NVE was deployed with. This can be seen in the workflow.log : YYYY-MM-DD HH:mm:SS (TZ) 47386805131940 INFO: >>> [make_temp_script] 222 very_current_user=root, as_user=, ssh command is: (/usr/local/avamar/bin/nodedb print --nodes=all --id --addr --internal) >/usr/local/avamar/var/run_command-sysout.30096.47386805131940 2>/usr/local/avamar/var/run_command-syserr.30096.47386805131940 YYYY-MM-DD HH:mm:SS (TZ) 47386805131940 INFO: - - - - - - - BEGIN(output) - - - - - - - YYYY-MM-DD HH:mm:SS (TZ) 47386805131940 INFO: (0.0) NVE-IP-ADDRESS NOTE: On some NVE deployments, the postdeployment configuration process removes the probe.xml file. In which case the above command fails and the rollup uses loopback (127.0.0.1) instead. Later in the rollup, the NVE performs ssh actions against the IP address it got from the probe.xml file to validate the authenticity of the NVE system. YYYY-MM-DD HH:mm:SS (TZ) 47017683049120 INFO: >>> [make_temp_script] 222 very_current_user=root, as_user=root, ssh command is: (ssh -q -i /root/.ssh/rootid -x -q -o ConnectTimeout=5 -o PasswordAuthentication=no -o StrictHostKeyChecking=no -o GSSAPIAuthentication=no root@ NVE-IP-ADDRESS ls -d /etc/SuSE-release) >/usr/local/avamar/var/run_command-sysout.31592.47017683049120 2>&1 YYYY-MM-DD HH:mm:SS (TZ) 47017683049120 INFO: >>> [make_temp_script] 222 very_current_user=root, as_user=root, ssh command is: (uname -a) >/usr/local/avamar/var/run_command-sysout.31592.47017683049120 2>&1 Performing the same ssh commands from the NVE's terminal reports the message "Please login as the user admin rather than the user root." Syntax: ssh -q -i /root/.ssh/rootid -x -q -o ConnectTimeout=5 -o PasswordAuthentication=no -o StrictHostKeyChecking=no -o GSSAPIAuthentication=no root@ NVE-IP-ADDRESS uname -a Example: azure-nve:~ # ssh -q -i /root/.ssh/rootid -x -q -o ConnectTimeout=5 -o PasswordAuthentication=no -o StrictHostKeyChecking=no -o GSSAPIAuthentication=no root@192.168.0.4 uname -a Enter passphrase for key '/root/.ssh/rootid': Please login as the user admin rather than the user root. azure-nve:~ # By default, the Azure NVE contains a "Match User root Address" line in the /etc/ssh/sshd_config file. The IP address used during the rollup is not in this line. azure-nve:~ # cat /etc/ssh/sshd_config | grep -A1 "Match User root Address" Match User root Address *,!::1,!127.0.0.1,!192.168.0.10 ForceCommand echo 'Please login as the user admin rather than the user root.';sleep 5 Because the IP is not in this list, the rollup returns "Please login as the user admin rather than the user root" when it runs uname -a . This results in the error "One or more nodes are not running SLES" To further validate, using localhost in the command should return the uname -a output: ssh -q -i /root/.ssh/rootid -x -q -o ConnectTimeout=5 -o PasswordAuthentication=no -o StrictHostKeyChecking=no -o GSSAPIAuthentication=no root@localhost uname -a Example: azure-nve:~ # ssh -q -i /root/.ssh/rootid -x -q -o ConnectTimeout=5 -o PasswordAuthentication=no -o StrictHostKeyChecking=no -o GSSAPIAuthentication=no root@localhost uname -a Enter passphrase for key '/root/.ssh/rootid': Linux azure-nve 4.12.14-122.237-default #1 SMP Wed Dec 11 01:21:33 UTC 2024 (93f8c95) x86_64 x86_64 x86_64 GNU/Linux NOTE: If uname output is not returned when using localhost , then there may also be an issue with the NVE's rootid passphrase, see: NVE: NvePlatformOsRollup fails "One or more nodes are not running SLES" due to corrupted rootid passphrase
Correct the /etc/ssh/sshd_config file on the NVE. Either change the incorrect IP address, or append the correct one. NOTE: The IP address from /data01/avamar/repo/temp/*/tmp/workflow.log must be added to the sshd_config file. For example: Match User root Address *,!::1,!127.0.0.1, !192.168.0.4 ForceCommand echo 'Please login as the user admin rather than the user root.';sleep 5 Restart the SSH service: systemctl restart sshd Validate that the ssh command returns the uname -a output: Syntax: ssh -q -i /root/.ssh/rootid -x -q -o ConnectTimeout=5 -o PasswordAuthentication=no -o StrictHostKeyChecking=no -o GSSAPIAuthentication=no root@ NVE-IP-ADDRESS uname -a NOTE: The NVE-IP-ADDRESS must be the same IP address shown in the /data01/avamar/repo/temp/*/tmp/workflow.log . Example: azure-nve:~ # ssh -q -i /root/.ssh/rootid -x -q -o ConnectTimeout=5 -o PasswordAuthentication=no -o StrictHostKeyChecking=no -o GSSAPIAuthentication=no root@192.168.0.4 uname -a Enter passphrase for key '/root/.ssh/rootid': HIDDENT_ROOTID_PASSPHRASE Linux azure-nve 4.12.14-122.237-default #1 SMP Wed Dec 11 01:21:33 UTC 2024 (93f8c95) x86_64 x86_64 x86_64 GNU/Linux If the command returns the kernel details, return to the NVE Installation Manager and click Retry Current Task .
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.