| Summary: | rhnplugin causes PackageKit to not prompt for new GPG keys | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | o.h.weiergraeber | ||||
| Component: | PackageKit | Assignee: | Richard Hughes <rhughes> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Desktop QE <desktop-qa-list> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.1 | CC: | ryan.stanyan, slukasik, tcallawa, tpelka | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-12-06 10:18:07 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
I'm guessing the broken link to RHN is causing this. When RHN is working normally, does this problem occur? Not sure which link you are actually referring to, but... yesterday I repeated the installation once again, and ran into exactly the same problem, so in case there was some issue at RHN, it has not been solved :( yum-rhn-plugin is offered as an update, but trying to install results in a "Transaction error". At this point, I noticed a new icon in the upper panel offering a message from package manager: (something like) "Package not found: yum-rhn-plugin...." So obviously, the update program is able to recognize the availability of an update, but when trying to download, it cannot actually *find* it. Please note that this does not affact yum, and does only affect certain packages (yum-rhn-plugin and apr so far), but not others. Maybe there is some trivial issue with the packages themselves (name too long, violation of version/build number conventions, or whatever) which prevents PackageKit from finding the downloads, but does not confuse yum? Just an idea... I can reproduce. If you use yum-rhn-plugin, the GPG-required callback does not get called and gnome-packagekit will not let you continue. The workaround is to run yum manually on the command line so that you get the chance to import the GPG keys manually. This means that everything works correctly. I'm going to do some hunting now to see whether a new version of PackageKit, yum, or yum-rhn-plugin has broken something here. I'm currently thinking it's the latter. Created attachment 518699 [details]
reproducer
Okay, so I've written a little reproducer that basically models what PK does. On RHEL 6.1 you can see the following output (after removing the gpgkeys):
[hughsie@hughsie-vm-el6 yum]$ sudo ./test.py
Loaded plugins: product-id, refresh-packagekit, rhnplugin
package to find yum-rhn-plugin-0.9.1-26.el6_1.1.noarch in rhel-x86_64-workstation-6
found 1 repos
repo has 5661 packages
We didn't find the package!
but the following packages do exist:
yum-rhn-plugin-0.9.1-5.el6.noarch
yum-rhn-plugin-0.9.1-7.el6.noarch
yum-rhn-plugin-0.9.1-26.el6.noarch
yum-rhn-plugin-0.9.1-26.el6_1.1.noarch
So searchNevra never finds the correct package even tho we can manually find it in the sack. I'll reassign to the yum guys for comments. Any ideas welcome.
Reassigning, feel free to reassign this back if it's indeed a PK bug. Thanks. Cute :). Spent an hour tracing through yum code shouting WTF at a screen a lot as packages magically disappeared, and then eventually saw: if len(pkgs) == 0: print "We found the package!" else: print "We didn't find the package!" ...I'm guessing you want "!=" here? As to an actual bug, my first reaction would be to check the repos/sacks you are using ... because the 6.1 update to rhnplugin decided it'd be a good idea to create fake Repos in init_hook and then swap then out for the real repos in prereposetup_hook. That might not be the problem, but... (In reply to comment #7) > ...I'm guessing you want "!=" here? Urgh, sorry. > As to an actual bug, my first reaction would be to check the repos/sacks you > are using How do you mean "check"? > ... because the 6.1 update to rhnplugin decided it'd be a good idea > to create fake Repos in init_hook and then swap then out for the real repos in > prereposetup_hook. That might not be the problem, but... Are there any docs on how rhnplugin works that I can read? Thanks. This one has been a real head pounder for me because I've never seen it any other distro I've used. One thing I've noticed is that gnome-packagekit works the way it should when I did a control and ran it under a root user session in Gnome. It also worked fine after installing a package from a non-RHN repository. (In reply to comment #8) > Are there any docs on how rhnplugin works that I can read? Thanks. I found this: http://www.scribd.com/doc/59524552/24/yum-rhn-plugin It isn't much but it could be a start. Hello, I just tried another fresh installation of version 6.1. The behaviour has changed somewhat, but it still doesn't work properly. (Would like to attach a screenshot but cannot see the option :( ) Searching for updates after a default install, I find four packages: rpm, rpm-libs, rpm-python and yum-rhn-plugin. All of them are downloaded successfully, but, paradoxically, there is a message saying "Could not find rpm-4.8.0-16.el6....." ?! After that I am prompted to accept the key for installation of rpm-libs. After entering the root password, it starts doing something, only to ask the same thing again and again... So it seems there is still more than one bug affecting graphical updates. If there is more information I should provide please let me know; but since I am using a very default install, it should be trivial to reproduce. All this is getting very disappointing... Is graphical update not being used by anybody after all? One thing I would like to add to my previous post: If this tool turns out to be so buggy that it cannot be easily fixed, RedHat should seriously consider removing it from the distribution. In the current state it behaves more like a joke! After all, text-based yum is doing a perfect job for applying updates to the system. (In reply to comment #12) > After all, text-based yum is doing a perfect job for applying updates to the > system. If you're happy using yum on the command line, PackageKit is not going to replace that. The core problem in this bug is that PackageKit is using the yum API in a slightly different way to the command line client which is exposing a bug. I'm working on the problem, as this looks like it's a rhnplugin regression. It's also hard to solve due to the number of interconnected pieces. (In reply to comment #11) > After entering the root password, it starts doing something, only to ask > the same thing again and again... > So it seems there is still more than one bug affecting graphical updates. Right; so it's a different bug. Please don't mix this new bug on this old ticket. Thanks. This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux. *** Bug 715055 has been marked as a duplicate of this bug. *** Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available. The official life cycle policy can be reviewed here: http://redhat.com/rhel/lifecycle This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL: https://access.redhat.com/ |
Description of problem: Updating certain packages fails using the "Software update" tool in RHEL 6.1. In contrast, running yum from the command line works as expected. Details: After a fresh default installation of RHEL 6.1 Client, the graphical update tool offers to update "yum-rhn-plugin". However, release notes cannot be displayed ("Loading...") and after clicking "Install updates" a "Transaction error" is issued. "yum update yum-rhn-plugin" from the command line works without problems (which includes importing the keys, in case that matters). After that, the graphical tool announces several additional updates, which can be applied without problems. Immediately after finishing, it pops up again asking to update "apr". At this point I did the reboot required for the kernel update first and then re-launched the update program. It finds "apr", again without release notes, and again exits with the same Transaction error as above. And once again, yum update on the command line works as expected. Interestingly, "yum info apr" gave me: ----------------------------------------------------------------------- Loaded plugins: product-id, refresh-packagekit, rhnplugin, subscription-manager Updating Red Hat repositories. There was an error communicating with RHN. RHN channel support will be disabled. Error communicating with server. The message was: Connection refused Installed Packages Name : apr Arch : x86_64 ... ----------------------------------------------------------------------- Repeating the entire installation a few days later gave the same result, so it does not look like a transient problem with RHN availability to me. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. Install RHEL 6.1, register system with RHN 2. Launch the "Software update" application 3. Try to update the packages mentioned above Actual results: Packages "yum-rhn-plugin" and "apr" (and probably others) cannot be updated via the "Software update" application. Expected results: All updates from RHN can be applied using the "Software update" tool. Additional info: Problems like these were not observed with RHEL 6.0.