Hide Forgot
Created attachment 489191 [details] job file w/user data. Description of problem: Just after launching a Condor job condor_q -better shows: 1 reject your job because of their own requirements However the job seems to launch just fine. The instance comes up on EC2. e.g.: jvlceklt % condor_q -better -- Submitter: localhost.localdomain : <192.168.122.1:44787> : localhost.localdomain --- 017.000: Run analysis summary. Of 1 machines, 0 are rejected by your job's requirements 1 reject your job because of their own requirements ... The job file is attached. The input file to "condor_advertise UPDATE_STARTD_AD" is: % cat ec2_provider_class_ad.txt # Set up the provider (backend cloud) to Condor Name="provider_combination_1" MyType="Machine" Requirements=true # Stuff needed to match: hardwareprofile="large" image="fedora14" realm="1" # Backend info to complete this job: image_key="ami-36ec115f" hardware_profile_key="m1.large" realm_key="us-east-1a" provider_url="http://localhost:3002/api" # From AWS - Account/Credentials username="AKIAI3NLPHGQ5FUO2T5Q" # Secret Access Key: password="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" cloud_account_id="1" keypair="joev" Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. condor_advertise UPDATE_STARTD_AD /home/jvlcek/Documents_boomvang/PROJECTS/CLOUD/audrey/ec2_provider_class_ad.txt 2. condor_submit job_1.external.cnd 3. condor_q -better Actual results: jvlceklt % condor_q -better -- Submitter: localhost.localdomain : <192.168.122.1:44787> : localhost.localdomain --- 017.000: Run analysis summary. Of 1 machines, 0 are rejected by your job's requirements 1 reject your job because of their own requirements ... Expected results: To see 0 rejects Additional info:
moving bugs to cloud engine project
This almost certainly won't be an issue anymore. With the matching code moving into conductor proper, condor no longer does matching, so jobs "always" succeed. I'd suggest closing it out. Chris Lalancette
moving to on_qa
From the above comment,condor no longer does matching. [root@dhcp193-9 scripts]# condor_q -help Usage: condor_q [options] where [options] are -global Get global queue -debug Display debugging info to console -submitter <submitter> Get queue of specific submitter -help This screen -name <name> Name of schedd -pool <host> Use host as the central manager to query -long Verbose output (entire classads) -xml Display entire classads, but in XML -attributes X,Y,... Attributes to show in -xml and -long -format <fmt> <attr> Print attribute attr using format fmt -analyze Perform schedulability analysis on jobs -run Get information about running jobs -hold Get information about jobs on hold -globus Get information about Condor-G jobs -goodput Display job goodput statistics -cputime Display CPU_TIME instead of RUN_TIME -currentrun Display times only for current run -io Show information regarding I/O -dag Sort DAG jobs under their DAGMan -expert Display shorter error messages -constraint <expr> Add constraint on classads -jobads <file> File of job ads to display -machineads <file> File of machine ads for analysis -direct <schedd> Perform a direct query to the schedd -version Print the Condor Version and exit restriction list where each restriction may be one of <cluster> Get information about specific cluster <cluster>.<proc> Get information about specific job <owner> Information about jobs owned by <owner> option -better has been removed. [root@dhcp193-9 scripts]# rpm -qa | grep aeolus aeolus-configure-2.0.1-0.fc14.20110602110128git5cb9257.noarch aeolus-conductor-0.3.0-0.fc14.20110621212750git516921d.noarch aeolus-all-0.3.0-0.fc14.20110621212750git516921d.noarch rubygem-aeolus-cli-0.0.1-1.fc14.20110621212750git516921d.noarch aeolus-conductor-doc-0.3.0-0.fc14.20110621212750git516921d.noarch aeolus-conductor-daemons-0.3.0-0.fc14.20110621212750git516921d.noarch
Just to be totally clear, the -better option to condor_q has *not* been removed. That is something that has existed in condor_q for ages, and it is not something we are removing. What is important here is that condor_q -better no longer gives us (much) information that we care about. If you are not doing matching, then the only possible information you can get from condor_q is the Held (failure) reason, if any. That said, I believe that this should stay VERIFIED. Chris Lalancette
release pending...
perm close
closing out old bugs