Foreman-plugin package blocks foreman-release upgrade

Upgrade step fails:

yum update -y

Loaded plugins: changelog, langpacks, priorities, ulninfo
Examining /var/tmp/yum-root-Sw0wGg/foreman-release.rpm: foreman-release-1.18.0-2.el7.noarch
Marking /var/tmp/yum-root-Sw0wGg/foreman-release.rpm as an update to foreman-release-1.17.1-1.el7.noarch
Resolving Dependencies
–> Running transaction check
—> Package foreman-release.noarch 0:1.17.1-1.el7 will be updated
–> Processing Dependency: foreman-release = 1.17.1-1.el7 for package: foreman-plugin-1.17.1-1.el7.noarch
—> Package foreman-release.noarch 0:1.18.0-2.el7 will be an update
–> Finished Dependency Resolution
Error: Package: foreman-plugin-1.17.1-1.el7.noarch (@foreman)
Requires: foreman-release = 1.17.1-1.el7
Removing: foreman-release-1.17.1-1.el7.noarch (@foreman)
foreman-release = 1.17.1-1.el7
Updated By: foreman-release-1.18.0-2.el7.noarch (/foreman-release)
foreman-release = 1.18.0-2.el7
Available: foreman-release-1.17.0-0.2.RC1.el7.noarch (foreman)
foreman-release = 1.17.0-0.2.RC1.el7
Available: foreman-release-1.17.0-0.3.RC1.el7.noarch (foreman)
foreman-release = 1.17.0-0.3.RC1.el7
Available: foreman-release-1.17.0-0.3.RC2.el7.noarch (foreman)
foreman-release = 1.17.0-0.3.RC2.el7
Available: foreman-release-1.17.0-1.el7.noarch (foreman)
foreman-release = 1.17.0-1.el7
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

Expected outcome:
foreman-release successfully upgraded

Foreman and Proxy versions:
any. In this example 1.17.1
Foreman and Proxy plugin versions:

Other relevant data:
[e.g. logs from Foreman and/or the Proxy, modified templates, commands issued, etc]

I wonder why you have foreman-plugin installed. Typically it’s a build dependency for plugins.

If you try to remove foreman-plugin, what would happen? It could be a valid workaround.