Linux (sles 15.6) patching failed

Question

Linux (sles 15.6) patching failed

Shubham Prajapati 40

Hi,

I tried to patch the Linux (sles 15.6) VM from Azure Update manager, but it got failed. When i checked the logs, dry run it is succeeding but during the actual update it is showing the following 12 items are locked and will not be changed by any action: Available: plymouth plymouth-branding-SLE plymouth-devel plymouth-dracut plymouth-lang plymouth-plugin-label plymouth-plugin-label-ft

after that it is getting failed.

Shubham Prajapati 40 Reputation points

2026-02-18T15:37:23.04+00:00

@Suchitra Suregaunkar Thanks for the respone.

So in the other server with same version i got this error :

alert the installed libmutter-5-0-3.34.6-150200.3.12.1.x86_64 requires 'libmutter-clutter-5.so.0()(64bit)', but this requirement cannot be provided deleted providers: mutter-3.34.6-150200.3.12.1.x86_64

so in this case i run zypper patch --category security --dry-run

since those libmutter are not in security updates, but still it is giving me the error.

so not sure if excluding the category or specific kb will work here.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Shubham Prajapati 40 Reputation points

2026-02-18T15:45:31.0233333+00:00

@Suchitra Suregaunkar

This time i got other error in different machine which is having the same version.

the installed libmutter requires 'libmutter-clutter, but this requirement cannot be provided deleted providers: mutter

i run the zypper patch --category security --dry-run to exclude the other updates since these libmutter in other updates category but still i got the error.

i have not mentioned the exact version number since platform was not allowing me.
Shubham Prajapati 40 Reputation points

2026-02-18T15:46:22.2233333+00:00

@Suchitra Suregaunkar

This time i got other error in different machine which is having the same version.

the installed libmutter requires 'libmutter-clutter, but this requirement cannot be provided deleted providers: mutter

i run the zypper patch --category security --dry-run to exclude the other updates since these libmutter in other updates category but still i got the error.

i have not mentioned the exact version number since platform was not allowing me.
Suchitra Suregaunkar 9,495 Reputation points Microsoft External Staff Moderator

2026-02-20T06:23:46.68+00:00

Hello Shubham Prajapati This error is caused by zypper dependency resolution, not Azure Update Manager. libmutter requires libmutter-clutter, but the provider mutter is removed from the transaction during patch filtering, causing dependency solving to fail. Azure Update Manager invokes the native zypper package manager and correctly surfaces this OS‑level error. The supported resolution is to exclude the mutter / libmutter packages in the Update Manager deployment using Exclude KB ID / package (for example: mutter*, libmutter*).

2 answers

Your answer

Shubham Prajapati 40 Reputation points

2026-02-18T15:37:23.04+00:00

@Suchitra Suregaunkar Thanks for the respone.

So in the other server with same version i got this error :

alert the installed libmutter-5-0-3.34.6-150200.3.12.1.x86_64 requires 'libmutter-clutter-5.so.0()(64bit)', but this requirement cannot be provided deleted providers: mutter-3.34.6-150200.3.12.1.x86_64

so in this case i run zypper patch --category security --dry-run

since those libmutter are not in security updates, but still it is giving me the error.

so not sure if excluding the category or specific kb will work here.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Shubham Prajapati 40 Reputation points

2026-02-18T15:45:31.0233333+00:00

@Suchitra Suregaunkar

This time i got other error in different machine which is having the same version.

the installed libmutter requires 'libmutter-clutter, but this requirement cannot be provided deleted providers: mutter

i run the zypper patch --category security --dry-run to exclude the other updates since these libmutter in other updates category but still i got the error.

i have not mentioned the exact version number since platform was not allowing me.
Shubham Prajapati 40 Reputation points

2026-02-18T15:46:22.2233333+00:00

@Suchitra Suregaunkar

This time i got other error in different machine which is having the same version.

the installed libmutter requires 'libmutter-clutter, but this requirement cannot be provided deleted providers: mutter

i run the zypper patch --category security --dry-run to exclude the other updates since these libmutter in other updates category but still i got the error.

i have not mentioned the exact version number since platform was not allowing me.
Suchitra Suregaunkar 9,495 Reputation points Microsoft External Staff Moderator

2026-02-20T06:23:46.68+00:00

Hello Shubham Prajapati This error is caused by zypper dependency resolution, not Azure Update Manager. libmutter requires libmutter-clutter, but the provider mutter is removed from the transaction during patch filtering, causing dependency solving to fail. Azure Update Manager invokes the native zypper package manager and correctly surfaces this OS‑level error. The supported resolution is to exclude the mutter / libmutter packages in the Update Manager deployment using Exclude KB ID / package (for example: mutter*, libmutter*).

Answer 1

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more

Answer 2

Hello **Shubham Prajapati**Your Update Manager run is failing because the update operation is trying to install/upgrade packages that the OS package manager treats as not changeable in the current transaction (you see it as “items are locked and will not be changed”). Azure Update Manager relies on the VM’s native Linux package manager and will surface those package-manager errors.

Update Manager honors the update source/settings on the machine and doesn’t publish/provide updates itself, meaning package-manager constraints on the VM can block the deployment.

Please follow below suggested Microsoft-supported workaround: Exclude the locked packages in the deployment.

Azure Update Manager supports Include/Exclude KB ID / package during deployments, and for Linux you can exclude packages by name using wildcards (exactly what you need for plymouth*). Option A: One-time update (fastest)

Azure portal → Azure Update Manager → Overview → One-time update
Select the SLES VM → Next
On the Updates pane:
- Keep the appropriate classifications (ex: Security/Critical) as needed
- Under Exclude KB ID/package, add the locked packages using wildcards, for example:
- plymouth*
- (If needed) plymouth-branding*
Continue → Review + install → Install

Option B: Scheduled patching / maintenance configuration (recommended for ongoing)

Use the same Exclude KB ID/package approach when creating the scheduled deployment so every run skips plymouth*.

Update Manager runs patching through its Linux VM patch extensions and reports what the OS package manager returns.
By excluding the problematic packages, the deployment proceeds with the remaining patches instead of failing the whole run. The Microsoft deployment guidance explicitly supports excluding packages in Update Manager.

Excluded packages may still appear in assessment results (assessment vs install are different), but they won’t be installed in that deployment. The deployment doc also notes “Selected Updates” is a preview and actual installed updates can vary based on latest assessment/repo state.

Reference: https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/update-manager/deploy-updates.md

Kindly let us know if the solution provided worked for you.

If you need any further assistance, please feel free to reach out.

Thanks,

Suchitra.

Share via

Linux (sles 15.6) patching failed

2 answers

Your answer