Bug 1622753 - yum command in post-install step spends hours printing hashes on RHEL4
Summary: yum command in post-install step spends hours printing hashes on RHEL4
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: general
Version: 25
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: 26.0
Assignee: Dan Callaghan
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-27 23:57 UTC by Dan Callaghan
Modified: 2018-10-08 02:16 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-08 02:16:43 UTC
Embargoed:


Attachments (Terms of Use)

Description Dan Callaghan 2018-08-27 23:57:42 UTC
Description of problem:
Seen in:
https://beaker-devel.app.eng.bos.redhat.com/recipes/25435
on dev-rx1620-01.rhts.eng.bos.redhat.com (ia64).

Version-Release number of selected component (if applicable):
25.6.git.7.f2d3ef15a

How reproducible:
unsure

Steps to Reproduce:
1. try installing RHEL4(?)

Actual results:
Installation exceeds 3 hour watchdog limit.
A large portion of the time is spent on yum writing its progress bar (made up of hash characters) as it loads the beaker-tasks repodata, which has upwards of 18,000 packages in it.

Expected results:
Installation should succeed. Ideally no time wasted printing progress bars.

Additional info:
I thought this should have been fixed by bug 765717 but maybe it's a slightly different problem.

Comment 1 Dan Callaghan 2018-08-28 00:00:33 UTC
It is probably something specific to this host, and/or conserver was being particularly slow at that time.

It has always printed the hashes on RHEL4, and we see it on other arches/machines as well, but normally it can print them all within a few minutes, it doesn't take several hours.

Comment 2 Dan Callaghan 2018-08-28 00:10:33 UTC
RHEL4 is pretty close to dead so we could just consider this WONTFIX as well.

Comment 3 Dan Callaghan 2018-08-28 00:29:04 UTC
On the very old yum we use on RHEL4, I noticed that -d 1 (that is, "debug level = 1" as opposed to the default of 2) produces reasonable output. It looks like this interactively:

# yum -d 1 install python-uuid 
Transaction Listing:
  Install: python-uuid.noarch 0:1.30-3.el4bkr - beaker-harness
Total download size: 14 k
Is this ok [y/N]: 

You still get pretty reasonable looking error output:

# yum -d 1 install python-uuidasdf
No Match for argument: python-uuidasdf

although I guess there is a chance that it would mask some potentially useful debugging information.

Comment 4 Dan Callaghan 2018-08-29 01:19:55 UTC
https://gerrit.beaker-project.org/#/c/beaker/+/6286

Comment 5 Dan Callaghan 2018-09-28 05:56:24 UTC
This bug was fixed on the release-25 branch, but the next release will be Beaker 26.0.

Comment 6 Dan Callaghan 2018-10-08 02:16:43 UTC
Beaker 26.0 has been released.


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