Red Hat Bugzilla – Bug 864523
beah won't install during machine provision at random times
Last modified: 2012-11-07 02:24:19 EST
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):
Fails at random times.
Steps to Reproduce:
1. Run 100 inventory jobs, some of them will fail due to that issue.
Job fails after watchdog expires.
Results were pushed to the scheduler.
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
Can you paste the job IDs where you saw this failure?
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.