Bug 458173 - up2date does not give appropriate failure message
Summary: up2date does not give appropriate failure message
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: up2date
Version: 4.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Pradeep Kilambi
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-08-06 20:51 UTC by Stephen Herr
Modified: 2012-06-20 13:29 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-20 13:29:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
screenshot1 (88.93 KB, image/png)
2008-08-06 20:51 UTC, Stephen Herr
no flags Details
screenshot2 (90.45 KB, image/png)
2008-08-06 20:51 UTC, Stephen Herr
no flags Details
screenshot3 (81.02 KB, image/png)
2008-08-06 20:52 UTC, Stephen Herr
no flags Details

Description Stephen Herr 2008-08-06 20:51:20 UTC
Created attachment 313639 [details]
screenshot1

[screenshot1]

It appears that modviersions need to be installed prior to kmod-xenpv-smp.

Retrying, the pacakges were schedule in separate events with modversion first.

[screenshot2[

root@ra-vm5:~/.vnc 
> rhn_check -v 

Name                                    Version        Rel     
---------------------------------------------------------- 
modversions                             1.0            4.el4_6.1         x86_64 
No advisory information available 



Name                                    Version        Rel     
---------------------------------------------------------- 
kmod-xenpv-smp                          0.1            10.el4            x86_64 
No advisory information available 



root@ra-vm5:~/.vnc 
> 

[screenshot3]

Since this is not working and not providing enough details, the packages will be downloaded then installed.

Comment 1 Stephen Herr 2008-08-06 20:51:43 UTC
Created attachment 313640 [details]
screenshot2

Comment 2 Stephen Herr 2008-08-06 20:52:03 UTC
Created attachment 313641 [details]
screenshot3

Comment 3 Stephen Herr 2008-08-06 20:54:50 UTC
Stephen,

The failure to install may be related to SELinux.   Found this in /var/adm/log.  The SELinux tools on 4 are not what I am used to on 5, so not 100% sure but the timing looks like it could have been in the ball park and that it is from "up2date".

Aug  6 13:24:54 ra-vm5 kernel: audit(1218043494.633:2): avc:  denied  { transition } for  pid=6601 comm="userhelper" name="up2date"
dev=dm-0 ino=105125 scontext=root:system_r:initrc_t tcontext=root:sysadm_r:unconfined_t tclass=process

spr

Comment 4 Stephen Herr 2008-08-06 20:56:11 UTC
By the way, I'm not the requester for this bug, just passing it along. sreichar is the real requester.

Comment 5 Steve Reichard 2008-08-08 13:58:16 UTC
Tried on another 4.7 virtual machine.

I failed like the other out of the box.

I set SELinux toe Permissive.  It failed

I shutdown iptables.  It failed.

All errors point to rpm failure (code 32).    On original node, package was downloaded and installed using rpm -ivh without failure (at least for the install)

root@ra-vm8:~
> rhn_check -v

Name                                    Version        Rel     
----------------------------------------------------------
modversions                             1.0            4.el4_6.1         x86_64
No advisory information available



root@ra-vm8:~
> getenforce
Permissive

root@ra-vm8:~
> rpm -qa| grep  modversions

root@ra-vm8:~
> service iptables stop
Flushing firewall rules:                                   [  OK  ]
Setting chains to policy ACCEPT: filter                    [  OK  ]
Unloading iptables modules:                                [  OK  ]

root@ra-vm8:~
> rhn_check -v

Name                                    Version        Rel     
----------------------------------------------------------
modversions                             1.0            4.el4_6.1         x86_64
No advisory information available



root@ra-vm8:~
> rpm -qa| grep  modversions

root@ra-vm8:~
>

Comment 6 Stephen Herr 2009-02-25 20:57:30 UTC
Okay, so a brief summary of the problem: installing modversions via RHN Hosted's webui fails, installing modversions via up2date fails, installing modversions via downloading the rpm and 'rpm -ivh' works. Attempting to install modversions with up2date and with debug-level verboseness turned on (up2date -vvvvv modversions) gives this message:

Testing package set / solving RPM inter-dependencies...
D: Candidates for the selected list: [['modversions', '1.0', '4.el4_6.1', '', 'i386', '20084', 'rhel-i386-as-4']]
D: Omitting package modversions in channel rhel-i386-as-4 from transaction set: it is obsoleted by package module-init-tools 
D: Checking for dependencies
D: opening  db environment /var/lib/rpm/Packages joinenv
D: opening  db index       /var/lib/rpm/Packages rdonly mode=0x0
D: closed   db index       /var/lib/rpm/Packages
D: closed   db environment /var/lib/rpm/Packages
D: Running transaction (final step)...
D: ========== recording tsort relations
D: ========== tsorting packages (order, #predecessors, #succesors, tree, depth)
########################################
D: opening  db environment /var/lib/rpm/Packages joinenv
D: opening  db index       /var/lib/rpm/Packages rdonly mode=0x0
D: closed   db index       /var/lib/rpm/Packages
D: closed   db environment /var/lib/rpm/Packages
D: ========== recording tsort relations
D: ========== tsorting packages (order, #predecessors, #succesors, tree, depth)
D: opening  db environment /var/lib/rpm/Packages joinenv
D: opening  db index       /var/lib/rpm/Packages rdonly mode=0x0
D: closed   db index       /var/lib/rpm/Packages
D: closed   db environment /var/lib/rpm/Packages
There was a fatal RPM install error. The message was:
Failed running rpm transaction
D: closed   db index       /var/lib/rpm/Providename
D: closed   db index       /var/lib/rpm/Name
D: closed   db index       /var/lib/rpm/Packages
D: closed   db environment /var/lib/rpm/Packages

Notice line 3: modversions is obsoleted by module-init-tools, so up2date refuses to install it. Steve: try using module-init-tools to do whatever you were using modversions for. 

This is still a bug however, since there was no indication whatsoever that this was the problem until we dug through debug output. The failure message should be at least a little indicative of what the problem was. Transferring to the appropriate group to fix up2date.

Comment 7 Jiri Pallich 2012-06-20 13:29:13 UTC
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.


Note You need to log in before you can comment on or make changes to this bug.