Red Hat Bugzilla – Bug 601367
lvm based guest images and most likely guest OS lvm filesystem requests not being processed properly by beaker
Last modified: 2011-06-13 14:45:12 EDT
Created attachment 421923 [details] legacy rhts xml Description of problem: beaker job https://beaker.engineering.redhat.com/jobs/1908 was an attempt to queue fully automated virtualization jobs. The job failed because the guestrecipe definition defining guest image storage size/type was not processed properly and not created in the host recipe kickstart. This is first noticed in /distribution/virt/install when it attempts to use the missing lvm blk device. Additionally, it has been brought to my attention that if the guest OS needs to specify file systems to be created that are based on lvm, that they probably arent being handled either. This example does not require such an item, but when we start testing RHEL6 guests, it will be a requirement. Without this functionality, automated ISV tests in a virtualized guest cannot be tested. Manual testing is not practical. Version-Release number of selected component (if applicable): Version - 0.5.41 ?? How reproducible: see job referenced above plus the legacy rhts xml. Steps to Reproduce: 1. queue the xml attached with the --convert option since it's legacy rhts 2. 3. Actual results: Expected results: Additional info: I will attache the legacy rhts xml that beaker converts...
Regression against RHTS, can't work in Beaker -> suggesting to be a blocker.
Context: This effects all ISV in virt testing. Started doing in 5.5 to test ISV apps in guests. Need this to support RHEL6.
I have just committed this to git. I'll be testing this Tonight and Tomorrow. One thing needed still is an option to bkr job-submit to autogenerate the partition tags based on the guest kickstarts disk requirements.