Bug 2196641
| Summary: | Configuration file /etc/yum/pluginconf.d/__init__.conf not found (and more) | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Ben <ben.argyle> |
| Component: | katello-tracer | Assignee: | satellite6-bugs <satellite6-bugs> |
| Status: | CLOSED MIGRATED | QA Contact: | Satellite QE Team <sat-qe-bz-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.12.2 | CC: | egolov, lufu, saydas |
| Target Milestone: | Unspecified | Keywords: | MigratedToJIRA, Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2024-06-06 16:13:57 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Hi Ben, Do you have a case open for this one? If so, we can get it attached to the bugzilla and Support can help with some basic debugging. Thanks! Hi Brad, At present, no. Is that something you definitely want/need me to do? Hi Ben, Thanks for the quick reply. It isn't required, but it was recommended by our Product Experience engineer. There are times that support may have recommendations/solutions/workarounds. In addition, it also gets the case attached to the bugzilla which can raise priority. Cheers! Case #03509723 opened. Thank you for the bug report, RedHat Enterprise Linux 6 is currently end of life. katello-host-tools-tracer and the katello-host-tools suite has not been updated anymore for Red Hat Enterprise Linux 6. This article shows that Red Hat Enterprise Linux 6 is end of life: https://access.redhat.com/articles/4665701 I would upgrade your hosts to the latest version of Red Hat Enterprise Linux 7 which is still supported and then upgrade to Red Hat Enterprise Linux 8 or 9 so you have the longest support possible. We are going to close this bug as WONTFIX. If you upgrade and are still seeing this issue, then feel free to reopen the bug. This link https://access.redhat.com/support/policy/updates/errata lists the lifecycle of RHEL 7/8/9. You can't close this, Red Hat have broken previously-working functionality. And Red Hat JUST updated katello-host-tools to 4.2.3-3 with the release of Satellite 6.13. So your comment is incorrect. We CANNOT upgrade these hosts (we have 25) from RHEL 6 to RHEL 7. We have ELS subscriptions. Am I to believe this doesn't mean anything when Red Hat breaks functionality? This is a genuine issue. It's happeing as we have included these as a part of updated package katello-host-tools /usr/lib/yum-plugins/__init__.py /usr/lib/yum-plugins/__init__.pyc /usr/lib/yum-plugins/__init__.pyo /usr/lib/yum-plugins/tracer_upload.py /usr/lib/yum-plugins/tracer_upload.pyc /usr/lib/yum-plugins/tracer_upload.pyo Where as the last katello-host-tools-fact-plugin package for RHEL 6 never had them And if someone just want to get rid of those error messages while continue to use the latest package, for that just do # touch /etc/yum/pluginconf.d/__init__.conf # touch /etc/yum/pluginconf.d/tracer_upload.conf If you wish to downgrade the package back to katello-host-tools-fact-plugin , then # yum remove katello-host-tools -y # yum install katello-host-tools-fact-plugin.noarch --exclude=katello-host-tools -y You're missing the step of then also installing katello-host-tools-3.5.7-3, which isn't installed by the yum install line above. Note also that none of this puts /etc/yum.plugins.d/tracer_upload.conf back, if it was there beforehand. Ah yes, It should be # yum remove katello-host-tools -y # yum install katello-host-tools-fact-plugin.noarch --exclude=katello-host-tools -y # yum install katello-host-tools-3.5.7-3.el6sat.noarch And perhaps for RHEL 6, The tracer equivalent feature was coming from some other plugin. I know for sure that we have tracer plugin ( as well as underlying binary ) starting from RHEL 7 but perhaps not for RHEL 6. It could have had something equivalent to tracer but not exactly the tracer itself. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. |
Description of problem: Since upgrading my RHEL 6 hosts from katello-host-tools-fact-plugin.noarch 0:3.5.7-3.el6sat to katello-host-tools.noarch 0:4.2.3-3.el6sat I now get the following every time I do yum commands: [root@rhel6 ~]# yum clean all Configuration file /etc/yum/pluginconf.d/__init__.conf not found Unable to find configuration file for plugin __init__ Configuration file /etc/yum/pluginconf.d/tracer_upload.conf not found Unable to find configuration file for plugin tracer_upload Loaded plugins: enabled_repos_upload, package_upload, product-id, search- : disabled-repos, security, subscription-manager [...] Version-Release number of selected component (if applicable): katello-host-tools-4.2.3-3.el6sat.noarch How reproducible: Every yum command I believe this has broken Tracer for my hosts. Let me know if there's any other information you need. Note that I have not upgraded my Satellite from 6.12.2 to anything higher (like 6.12.4, or 6.13).