Bug 864523

Summary:	beah won't install during machine provision at random times
Product:	[Retired] Beaker	Reporter:	Vadim Grinco <vgrinco>
Component:	beah	Assignee:	Dan Callaghan <dcallagh>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	0.9	CC:	asaha, dcallagh, mishin, rglasz, rmancy
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	MC
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-11-07 07:24:19 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Vadim Grinco 2012-10-09 13:56:21 UTC

Description of problem:
Some times it happens that beah won't install during machine provision, failing to finish the /distribution/install task. This is causing the whole recipe set and the job to fail after watchdog expires. If you clone and re-run the same job there is a great chance that it fill finish successfully.

Version-Release number of selected component (if applicable):
beah-0.6.40-1.el5.noarch

How reproducible:
Fails at random times.

Steps to Reproduce:
1. Run 100 inventory jobs, some of them will fail due to that issue.
  
Actual results:
Job fails after watchdog expires.

Expected results:
Results were pushed to the scheduler.


Additional info:
You can actually SSH to the system after provision, ssh keys are copied, etc.
If you install beah, set it to run after reboot and reboot the machine - task finishes successfully.

Is there a reason why beah is installed in %post but not from the %packages section of the kickstart? %post log is redirected to /dev/console currently, which makes it very hard to debug on machines with console issues.
Also beah rpm could make sure the app is started on boot, so there wouldn't be need to script it. As an alternative

Comment 1 Dan Callaghan 2012-10-09 21:59:13 UTC

Can you paste the job IDs where you saw this failure?

Comment 2 Min Shin 2012-11-07 07:24:19 UTC

This bugs is closed as it is either not in the current Beaker scope or we could not find sufficient data in the bug report for consideration.
Please feel free to reopen the bug with additional information and/or business cases behind it.