Hello, I’m posting here in hopes of getting some assistance.
I have a test environment where the AWS SSM Agent is installed on an Azure VM (OS: SUSE Linux Enterprise Server 15 SP4). I am attempting to apply OS patches remotely from AWS.
However, the process is failing, and the following logs are output by Patch Manager.
I believe it may be necessary to remove certain packages. In my development environment, I tested running:
zypper remove azure-cli azure-cli-core python3-azure* python311-azure*
However, this approach caused the SLES system to become unstable, so I am looking for an alternative solution.
Could you please advise if there is a better approach?
log：
04/03/2026 04:55:21 root [WARNING]: Truncating telemetry output to 500 characters
04/03/2026 04:55:21 root [WARNING]: Truncating telemetry output to 500 characters
04/03/2026 04:55:25 root [ERROR]: Encountered a known exception in the CLI Invoker: CLIInvokerError(error_message=‘Dependency check failure during commit process’, error_code=‘4’)
04/03/2026 04:55:25 root [ERROR]: Output from commit:
Refreshing service ‘Basesystem_Module_x86_64’.
Refreshing service ‘Containers_Module_x86_64’.
Refreshing service ‘Desktop_Applications_Module_x86_64’.
Refreshing service ‘Development_Tools_Module_x86_64’.
Refreshing service ‘Legacy_Module_x86_64’.
Refreshing service ‘Public_Cloud_Module_x86_64’.
Refreshing service ‘Python_3_Module_x86_64’.
Refreshing service ‘SUSE_Linux_Enterprise_Server_x86_64’.
Refreshing service ‘Server_Applications_Module_x86_64’.
Refreshing service ‘Web_and_Scripting_Module_x86_64’.
Loading repository data…
Reading installed packages…
There is an update candidate ‘amazon-ssm-agent-3.3.1611.0-150000.5.26.1.x86_64’ for ‘amazon-ssm-agent-3.3.987.0-1.x86_64’, but it does not match the specified version, architecture, or repository.
There is an update candidate for ‘amazon-ssm-agent’ from vendor ‘SUSE LLC https://www.suse.com/’, while the current vendor is ‘Amazon.com’. Use ‘zypper install amazon-ssm-agent-3.3.1611.0-150000.5.26.1.x86_64’ to install this candidate.
There is an update candidate ‘azure-cli-core-2.66.0-150400.14.9.2.noarch’ for ‘azure-cli-core-2.36.0-150200.9.3.2.noarch’, but it does not match the specified version, architecture, or repository.
There is an update candidate ‘azure-cli-2.66.0-150400.14.18.1.noarch’ for ‘azure-cli-2.36.0-150200.9.3.2.noarch’, but it does not match the specified version, architecture, or repository.
There is an update candidate ‘python3-M2Crypto-0.38.0-150400.7.64.x86_64’ for ‘python3-M2Crypto-0.35.2-150000.3.14.1.x86_64’, but it does not match the specified version, architecture, or repository.
There is an update candidate ‘python3-lxml-4.7.1-150200.3.12.1.x86_64’ for ‘python3-lxml-4.7.1-150100.6.6.1.x86_64’, but it does not match the specified version, architecture, or repository.
Resolving package dependencies…
2 Problems:
Problem: the to be installed azure-cli-2.58.0-150400.14.12.1.noarch requires ‘python311-azure-cosmos >= 3.0.2’, but this requirement cannot be provided
Problem: the to be installed azure-cli-core-2.58.0-150400.14.6.1.noarch requires ‘python311-azure-nspkg >= 3.0.0’, but this requirement cannot be provided
Problem: the to be installed azure-cli-2.58.0-150400.14.12.1.noarch requires ‘python311-azure-cosmos >= 3.0.2’, but this requirement cannot be provided
not installable providers: python311-azure-cosmos-4.5.1-150400.11.7.1.noarch[Public_Cloud_Module_x86_64:SLE-Module-Public-Cloud15-SP4-Updates]
Solution 1: Following actions will be done:
deinstallation of python3-azure-sdk-4.0.0-150200.6.3.2.noarch
deinstallation of python3-azure-functions-devops-build-0.0.22-150200.6.3.2.noarch
deinstallation of python3-opencensus-ext-azure-1.1.0-150200.5.3.2.noarch
Solution 2: do not install azure-cli-2.58.0-150400.14.12.1.noarch
Solution 3: break azure-cli-2.58.0-150400.14.12.1.noarch by ignoring some of its dependencies
Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/c/d/?] (c): c
04/03/2026 04:56:17 root [WARNING]: Truncating telemetry output to 500 characters
04/03/2026 04:56:17 root [WARNING]: Truncating telemetry output to 500 characters
04/03/2026 04:56:28 root [ERROR]: Commit subprocess had dependency check issues. Exit Code: 4
Aborting.
04/03/2026 04:56:29 root [ERROR]: Failure occurred in the operation, patching exit code is 2 and inventory exit code is 1
04/03/2026 05:00:56 root [ERROR]: Failure occurred in the operation, patching exit code is 2 and inventory exit code is 1
04/03/2026 05:00:56 root [ERROR]: Failure occurred in the operation, patching exit code is 2 and inventory exit code is 1
04/03/2026 05:00:58 root [ERROR]: To troubleshoot this execution failure using Systems Manager Automation, visit xxxx
04/03/2026 05:00:58 root [ERROR]: For common errors related to patching, visit xxxx
failed to run commands: exit status 1