Bug 188189
Summary: | yumex repeatedly fails to update kernel | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Andy Burns <fedora> | ||||
Component: | yumex | Assignee: | Tim Lauridsen <tim.lauridsen> | ||||
Status: | CLOSED CANTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 5 | CC: | extras-qa, ivazqueznet | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2006-04-18 13:30:18 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Andy Burns
2006-04-06 19:34:13 UTC
Created attachment 127424 [details]
yum.log
Do you see any AVC denial messages in /var/log/audit/audit.log* pointing to yumex? grep -i yum audit.log finds nothing ... On my system the AVC messages is written to /var/log/messages. Try this as root. grep -i yumex /var/log/messages Another way to see the problem is by running 'yumex' from the console. You will see some rpm scriplet error when installing the kernal. Read about the problem here. http://linux.rasmil.dk/cms/modules/news/article.php?storyid=56 you have to update you system with 'yum update selinux-policy*' to get the latest selinux policy installed. (2.2.25-3.fc5), after installation a reboot is needed. After that you should be able to install the kernal with yumex. (In reply to comment #4) > On my system the AVC messages is written to /var/log/messages. yes I did check /var/log/messges (and even dmesg) for anything yumex related > Another way to see the problem is by running 'yumex' from the console. > You will see some rpm scriplet error when installing the kernal. I didn't try that, but it's too late now to see if any errors went to the console, I did manage to "kick" the relevnt upgrades by using yum instead of yumex, certainly in yumex's output window there were no errors, it claimed to have installed successfully. > Read about the problem here. > http://linux.rasmil.dk/cms/modules/news/article.php?storyid=56 Ok, that's good, so long as the problem is understood, is any more error checking needed in yumex so that in future it will report the error rather than mask it? It is rpm there is repost the scriptlet errors as warning on the console, but it dont return any errorcode so the yum installation api routines cant detect it as an error, so yumex thinks that everytings was installed succesfully. The RPM warnings are written directly to the stdout, so where is no way to redirect so the user can see it in the GUI, even when using the python ways to redirect stdout, dont redirect there errors. |