Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 880899

Summary: op attribute is declared as mandatory in beaker-job.rng for many elements where it is not actually mandatory
Product: [Retired] Beaker Reporter: Dan Callaghan <dcallagh>
Component: web UIAssignee: Qixiang Wan <qwan>
Status: CLOSED CURRENTRELEASE QA Contact: Dan Callaghan <dcallagh>
Severity: unspecified Docs Contact:
Priority: low    
Version: 0.9CC: asaha, dcallagh, mishin, qwan, rglasz, rmancy
Target Milestone: 0.11   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: UX
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-01-17 04:33:58 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 Dan Callaghan 2012-11-28 05:12:22 UTC 
Almost all the hostRequires elements default to == if no op attribute is given, but in the latest version of beaker-job.rng the attribute is declared as mandatory which is inconvenient. It means submitting a perfectly valid hostRequires such as:

			<hostRequires>
				<cpu>
					<flag value="sse2"/>
				</cpu>
			</hostRequires>

is met with a RELAX NG validation error.
Comment 1 Dan Callaghan 2012-12-03 23:49:26 UTC 
http://git.beaker-project.org/cgit/beaker/commit/?h=develop&id=fd5b9d04dafc188620dbadfbc585be443343c33d
Comment 4 Dan Callaghan 2013-01-17 04:33:58 UTC 
Beaker 0.11.0 has been released.