Order of submitted requirements expressions results in different defaults added to requirements string in MRG 2.0

Solution Verified - Updated -

Issue

  • Using Requirements = ( ( Target.Memory >= My.RequestMemory ) && ( RequestMemory =!= undefined ) ) in a job description file results in the job's ClassAd to have a Requirement string that includes && ( ( RequestMemory * 1024 ) >= ImageSize ) while using Requirements = ( ( RequestMemory =!= undefined ) && ( Target.Memory >= My.RequestMemory ) ) does not.

Environment

  • MRG 2.0 Grid

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content