What's the tog-pegasus-devel package's scritplet doing?
it seems tog-pegasus-devel is not installed. #rpm -q tog-pegasus-devel package tog-pegasus-devel is not installed attached top and "ps -A" logs.
Created attachment 354105 [details] top log
Adding tog-pegasus maintainer ...
Not sure what provides /usr/bin/repupgrade, but that looks to be the process taking all of the time. If that's a lengthy process (or if the program has a bug that causes it to chew CPU), that could very well make anaconda look like it's hung. Unfortunately we don't get any progress information from rpm that allows us to inform the user.
/usr/bin/repupgrade is tool for upgrading the contents of a repository based on older version of schema (/var/lib/Pegasus/prev_repository) to a repository based on the new schema (/var/lib/Pegasus/repository). /var/lib/Pegasus/prev_repository is created when updating (rpm -U) tog-pegasus package, it's just a copy of /var/lib/Pegasus/repository before update. When installing for the first time (rpm -i), there should be no old repository and /usr/bin/repupgrade should not be executed at all. /usr/bin/repupgrade process take a few seconds usually. You can also check /var/lib/Pegasus/log/install.log.
Given where we are in 5.4, should we release note this, since a reasonable workaround exists and its only the devel package that most users would not be installing anyway?
This will affect all users installing @Everything package set.
The same behaviour with latest RHEL5.4-20090721.nightly
Can someone please attach the /var/lib/Pegasus/log/install.log mentioend in comment 8?
So are we saying that all @everything installs on all arches hang because of this problem?
Created attachment 354837 [details] /var/lib/Petasus/log/install.log
(In reply to comment #19) > Created an attachment (id=354837) [details] > /var/lib/Petasus/log/install.log Just timestamps from both installation %post scripts. No output from repupgrade to stderr (which is redirected to this log).
Created attachment 355282 [details] screenshot showing installation hang at tog-pegasus package
Do we agree that the problem seems to be in the tog-pegasus repupgrade tool, or in the script that uses it?
Release note added. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: The sblim-cmpi-dhcp package does not register provider modules to "root/PG_InterOp" namespace of the tog-pegasus repository. If you need these provider modules, you can register them lately with following command as root: /usr/share/sblim-cmpi-dhcp/provider-register.sh -t pegasus -v -n "root/PG_InterOp" -r /usr/share/sblim-cmpi-dhcp/Linux_DHCPRegisteredProfile.registration /usr/share/sblim-cmpi-dhcp/Linux_DHCPElementConformsToProfile.registration -m /usr/share/sblim-cmpi-dhcp/Linux_DHCPService.mof /usr/share/sblim-cmpi-dhcp/Linux_DHCPRegisteredProfile.mof /usr/share/sblim-cmpi-dhcp/Linux_DHCPElementConformsToProfile.mof Accordingly, deregister modules before update/remove of the sblim-cmpi-dhcp package with following command as root: /usr/share/sblim-cmpi-dhcp/provider-register.sh -d -t pegasus -n "root/PG_InterOp" -r /usr/share/sblim-cmpi-dhcp/Linux_DHCPRegisteredProfile.registration /usr/share/sblim-cmpi-dhcp/Linux_DHCPElementConformsToProfile.registration -m /usr/share/sblim-cmpi-dhcp/Linux_DHCPService.mof /usr/share/sblim-cmpi-dhcp/Linux_DHCPRegisteredProfile.mof /usr/share/sblim-cmpi-dhcp/Linux_DHCPElementConformsToProfile.mof
Manual installations confirm results from rhts - installations finished successfully. Also no problem when performing installation described in comment 29. Tested with RHEL5.4 RC1, sblim-cmpi-dhcp-0.5.5-35.el5, tog-pegasus-2.7.2-1.el5 on ppc. Moving to VERIFIED.
Release note updated. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,4 +1,16 @@ -The sblim-cmpi-dhcp package does not register provider modules to "root/PG_InterOp" namespace of the tog-pegasus repository. If you need these provider modules, you can register them lately with following command as root: +when the sblim-cmpi-dhcp package is installed, it modifies the +files under /var/lib/Pegasus owned by the tog-pegasus package. +Previously, when sblim was installed in the course of an "everything" +installation of Red Hat Enterprise Linux 5 on the PowerPC architecture, +the modifications that sblim made in the /var/lib/Pegasus directory +prevented the post-install scriptlet from completing the +provider-register commands. In turn, this would prevent installation +of Red Hat Enterprise Linux 5 from completing. The provider-register +commands are no longer provided in the post-install scriptlet, +therefore avoiding this situation and allowing installation of the +operating system to complete normally. Users of SBLIM who need to +register provider modules for tog-pegasus should register these +modules manually by running the following command as root: /usr/share/sblim-cmpi-dhcp/provider-register.sh -t pegasus -v -n "root/PG_InterOp" -r
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-1267.html