Bug 880899 - op attribute is declared as mandatory in beaker-job.rng for many elements where it is not actually mandatory
Summary: op attribute is declared as mandatory in beaker-job.rng for many elements whe...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: web UI
Version: 0.9
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: 0.11
Assignee: Qixiang Wan
QA Contact: Dan Callaghan
URL:
Whiteboard: UX
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-28 05:12 UTC by Dan Callaghan
Modified: 2018-02-06 00:41 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-01-17 04:33:58 UTC
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.