Description of problem:
The --tree option does not work when pointed at a installation tree of
RPM packages. The installation tree works fine with anaconda for
1) Mounted NFS export containing the RedHat directory on /mnt/server1
Ran 'redhat-config-packages --tree=/mnt/server1'
Get the error "The path /mnt/server1 does not look like a valid
2) Placed RedHat directory on FTP server (server1.example.com) in /pub
Tried 'redhat-config-packages --tree=ftp://server1.example.com/pub'
Got Python traceback. Will attach.
3) Tried --isodir using a directory containing the four ISOs. Works.
Version-Release number of selected component (if applicable):
Created attachment 97997 [details]
Python traceback of --tree=ftp:// output
comments on LTC-10134 IBM side
Steps to Reproduce:
2.cp -a /mnt/isodir/RedHat /target/directory/
3.repeated for all 4 cds
4.Tried to run redhat-config-packages -t /target/directory/
Installation Tree Not Found.
The path /redhat/ does not look like a valid installation source.
Also tried this with mounting nfs dir from install source server and
with same results. Is there another step to do to make install source
Do you have the .discinfo file there?
----- Additional Comments From firstname.lastname@example.org 2004-08-17 15:44 -------
please verify this with the latest ISO's 8/16.
----- Additional Comments From email@example.com 2004-08-19 11:18 -------
Sorry, Joe's out. Michelle - can you get that, pls?
----- Additional Comments From firstname.lastname@example.org 2004-08-19 11:57 -------
yes, I will try to recreate and update this with my results.
----- Additional Comments From email@example.com 2004-08-27 10:56 -------
I mounted our nfs install source (that was used to do the installation itself)
to a partition at /mnt. I then ran redhat-config-packages -t/mnt and it still
gives the error message that this doesn't look like a valid install source.
----- Additional Comments From firstname.lastname@example.org 2004-08-27 12:12 -------
Ok we recereated this - we need someone to debug here. Khoa - pls get this
----- Additional Comments From email@example.com 2004-08-31 17:53 -------
Can you give me access to the system where it's failing? I'll take a look....
IBM , still in need info...
----- Additional Comments From firstname.lastname@example.org 2004-09-07 12:40 -------
Can you recreate this on rhel4 at all? If you can, can you give me access to it?
----- Additional Comments From email@example.com 2004-09-07 15:46 -------
Mike, I am trying to recreate with RHEL_4 on ilinjck8. I will let you know
----- Additional Comments From firstname.lastname@example.org 2004-09-08 11:08 -------
I used the RHEL_4/beta isos to install ilinjck8 then mounted the install
source. I then ran redhat-config-packages -t/mnt/cd and received an error
message that the redhat-config-packages command not found.
----- Additional Comments From email@example.com 2004-09-08 16:11 -------
I reproduced this with RHEL 3 QU3 GA packages. I installed w/ nfs and mounted
the same source at /mnt, exported the DISPLAY, then ran redhat-config-packages -
t/mnt and got the error that said it was not a valid install source. My guess
is it will fail equally well with the cd's.
----- Additional Comments From firstname.lastname@example.org 2004-09-08 21:07 -------
The rhel4 version is system-config-packages. I can't get that to run, it
requires a display (which I exported) but then it does this:
[root@ilinjck8 ~]# system-config-packages
_X11TransSocketINETConnect() can't get address for redsfan8:6003: Temporary
failure in name resolution
Unable to import gtk module. This may be due to running without
$DISPLAY set. Exception was:
could not open display
Traceback (most recent call last):
File "/usr/share/system-config-packages/MainWindow.py", line 11, in ?
NameError: name 'sys' is not defined
This seems like it's basically ltc bug 9341 (rit 41702) in the service family.
I started to try the workaround there....
This is fixed up in 1.2.15 which I'm about to build.
----- Additional Comments From email@example.com 2004-10-04 13:41 EDT -------
This bug is in Modified state on the Red Hat side. We should see this in U4.
----- Additional Comments From firstname.lastname@example.org 2004-11-08 15:50 EDT -------
Problem still exists in QU4.
----- Additional Comments From email@example.com 2004-11-08 16:01 EDT -------
Ok, it looks like this should be fixed in rhel4 beta2, maybe, but not the rhel3
qu4 beta 2 that we have:
mranweil@redsfan8:/var/file-sharing/redhat/RHEL_4/beta2> find . -name
mranweil@redsfan8:/var/file-sharing/redhat/RHEL_3_QU4/beta2> find . -name
It's not clear to me, but at least we have a version # greater than what Jermey
references on rhel4....
----- Additional Comments From firstname.lastname@example.org 2004-11-08 16:02 EDT -------
Monza - so can you try this on rhel4 beta2? And is this really a block level
This bug is being used to track a problem in RHEL3-U3 and RHEL4-Beta2.
Unfortunately, bugzilla only allows you to file an issue against one product. I
suggest that if this problem exists in RHEL4, we should file a new bug against
Red Hat Enterprise Linux (nahant).
Moving this issue back to assigned as it appears the fix is not in RHEL3-U4
... because the fix was agreed to just go into the devel stream
because doing an updated package to fix an error message (on the path
that isn't the normal or recommended) was deemed far more work than
----- Additional Comments From email@example.com 2004-11-08 17:27 EDT -------
Problem exists in RHEL4 beta2 mounting nfs directory as install source.
Changing severity to high. Opened a new bug (#12362) for RHEL4 beta2.
----- Additional Comments From firstname.lastname@example.org 2004-11-08 21:09 EDT -------
Reopening this bug since it is not yet fixed in QU4 beta2.
Khoa/Pamela/Mike, when should the target milestone be?
As I understand it, this issue is tracking the --tree option for RHEL3. If this
bug exists in RHEL4, please file a seperate issue. From comment#25 from
email@example.com it appears that a new LTC bug was filed to track RHEL4. Has
this been mirrored over to Red Hat Bugzilla yet?
----- Additional Comments From firstname.lastname@example.org 2004-11-10 16:02 EDT -------
James, the bug has been mirrored to RH bugzilla as #138420.
----- Additional Comments From email@example.com 2004-11-10 17:11 EDT -------
Verified that this bug is fixed.
firstname.lastname@example.org: To confirm, you are no longer experiencing this problem on
RHEL3? What is the version of redhat-config-packages tested? Thanks.
----- Additional Comments From email@example.com 2004-11-10 20:15 EDT -------
James, my name is Monza.
Yes, the bug is verified to have been fixed in QU4.
[root@y0121p9 root]# rpm -qa|grep redhat-config-pack
Thanks Monza! Closing this issue as FIXED CURRENTRELEASE. Please re-open this
issue if a regression is detected. Please follow bug#138420 (LTC12362) for
changes to system-config-packages in RHEL4.