Where to report incompatible plugin versions in Katello repo?

Support
1

Problem:
Katello repo ships with plugin versions that are outdated at incompatible according to the plugin authors.
I want to report this to the correct team in charge of publishing updates to these repos, but do not know wether Katello team or plugin authors are responsible for this.

Expected outcome:
Katello repo ships compatible plugin versions and/or I know where to report this issue.

Foreman and Proxy versions:
1.20.1 with katello 3.9
Katello repos 3.10 and 3.11 are also affected

Foreman and Proxy plugin versions:
The plugin I discovered to be shipped in incompatible versions is tfm-rubygem-foreman_scc_manager-1.4.0-3.fm1_20.el7.noarch

Other relevant data:
According to the GitHub page, plugin version 1.4 (that is in katello repo up till 3.10) was last compatible with Katello 3.6. Katello repo 3.11 currently has 1.5, which was last compatible with Katello 3.8.

2

@m-bucher and @x9c4 have bumped it in the past. There was a PR to update it and cherry picks were requested:
https://github.com/theforeman/foreman-packaging/pull/3349

That wasn’t cherry picked. We did cherry pick 1.5.1 and built it in tfm-rubygem-foreman_scc_manager-1.5.1-1.fm1_20.el7 | Build Info | koji. However, the SCC manager is a bit of an odd case. It lives in the Katello repository (unlike plugins) where the Katello release owner has to sign and push the packages. I think @Justin_Sherrill has to do that.

cc @evgeni

3

It is to my knowlege the only ‘katello plugin’. So strange things to happen are not really surprising. But i’d love to see the situation improved.

4

Thanks for your replies so far!
I feared it would be some sort of comlicate situation after figuring out that plugin is not within the foreman-plugins repo. I guess I can revert to running the plugin from source, but this is not a satisfactory experience from a users perspective. I guess most users will, just like me, expect installed packages from the official repos to at least be the correct compatible version for each release. Installing from RPM (and beeing happy the plugin is provided in a packaged form) just to find out you still have to revert to git install (or some other way) after debugging for some ours is not really a great experience :frowning:

Seeing this situation improve would be really great! I’d really like to someday be able to revert to a yum workflow.

1 Like
5

You can download the RPM from koji until then. It’s not the prettiest, but cleaner than a git install IMHO.

I’m also submitting PRs to update to 1.6.0 as originally requested.

1 Like
6

Thanks for the tip!
I had to dig a little, since the version you linked also is not compaltible with 3.9. I ended up using this package from the 1.22 builds that seems to work.