Issue upgrade from Plesk Obsidian 18.0.45 to 18.0.46

[pauls1919]

Server operating system version

CloudLinux 8.5 x86_64

Plesk version and microupdate number

Plesk Obsidian 18.0.45.0

When upgrading plesk we have this message:
No matches found for the following enable plugin patterns: amazon-id
It can go further and upgrade is done but there is still another message at the end
"
Module yaml error: Unexpected key in data: static_context [line 9 col 3]
Module yaml error: Unexpected key in data: static_context [line 9 col 3]
Module yaml error: Unexpected key in data: static_context [line 9 col 3]
"

i saw other topic related to this issue and there was mentioned to remove the line from /etc/yum.repos.d/epel.repo
exclude=awstats*
But there is no such exlcude line.

Product version: Plesk Obsidian 18.0.46.0
OS version: CloudLinux 8.5 x86_64
Build date: 2022/08/14 12:00

 

[IgorG]

The issue is caused by outdated package:

# rpm -qa | grep libmodulemd
libmodulemd1-1.8.16-0.2.9.4.2.x86_64
libmodulemd-2.9.4-2.el8.x86_64

Update it with:

# yum update libmodulemd

 

[pauls1919]

yum update libmodulemd

rpm -qa | grep libmodulemd
libmodulemd-2.9.4-2.el8.x86_64

and

yum update libmodulemd
Updating Subscription Management repositories.
Unable to read consumer identity
This system is receiving updates from CloudLinux Network server.
Last metadata expiration check: 1:11:30 ago on Thu 01 Sep 2022 07:46:29 AM CEST.
Module yaml error: Unexpected key in data: static_context [line 9 col 3]
Module yaml error: Unexpected key in data: static_context [line 9 col 3]
Module yaml error: Unexpected key in data: static_context [line 9 col 3]
Module yaml error: Unexpected key in data: static_context [line 9 col 3]
Module yaml error: Unexpected key in data: static_context [line 9 col 3]
Module yaml error: Unexpected key in data: static_context [line 9 col 3]
Module yaml error: Unexpected key in data: static_context [line 9 col 3]
Module yaml error: Unexpected key in data: static_context [line 9 col 3]
Dependencies resolved.
Nothing to do.
Complete!

 

[Azurel]

I also saw the line when installing v46 manually: "No matches found for the following enable plugin patterns: amazon-id"

# rpm -qa | grep libmodulemd
result is for AlmaLinux 8.6:
> libmodulemd-2.13.0-1.el8.x86_64
> libmodulemd1-1.8.16-0.2.13.0.1.x86_64

# yum update libmodulemd
replied with:
> Dependencies resolved.
> Nothing to do.
> Complete!

Thats maybe not the reason?

 

[IgorG]

A known redhat-based OS issue:
Yum/DNF fails with warning Module yaml error: Unexpected key in data: static_context [line 9 col 3] - Red Hat Customer Portal

 

[pauls1919]

Thank you Igor but even after i disable the epel repo.
rpm -qa | grep libmodulemd
libmodulemd-2.9.4-2.el8.x86_64

yum update libmodulemd
Updating Subscription Management repositories.
Unable to read consumer identity
This system is receiving updates from CloudLinux Network server.
Last metadata expiration check: 1:52:38 ago on Fri 02 Sep 2022 11:11:56 AM CEST.
Dependencies resolved.
Nothing to do.
Complete!

 

[JB-K]

Same issue here when trying to update Plesk.
- Awstats is not excluded
- Epel is enabled

# rpm -qa | grep libmodulemd
libmodulemd1-1.8.16-0.2.13.0.1.x86_64
libmodulemd-2.13.0-1.el8.x86_64

# dnf update libmodulemd
Last metadata expiration check: 0:07:23 ago on Thu 08 Sep 2022 07:30:20 PM CEST.
Dependencies resolved.
Nothing to do.
Complete!

@IgorG

 

[IgorG]

Please submit Reports with all necessary details. I will forward it to the developers.

 

[Rhys Hanrahan]

Hi, @IgorG do you know if there is any update to this issue? We are having the same issue and it's been a couple of weeks now.

We're a partner and I would log a case directly with Plesk but we are stuck because our current Plesk version is considered too far out of date to submit a case.

Thanks,
Rhys.

 

[pauls1919]

@IgorG any update for this issue?

 

[IgorG]

@IgorG any update for this issue?

Did you fill out the report, as I asked above? Until the problem has been sent to the developers for review, I have nothing to answer you.

 

[Rhys Hanrahan]

For any future readers, this seems like it might just work now - I did notice the CLI updater seemed to update itself to a newer version. Unfortunately I can't grab the versions from my console history.

All I did to get this working months later (on AlmaLinux) was:
- dnf update
- plesk installer --console

Good luck!