Description of problem: Create a deltacloud job (tested with RHEV-M), submit it. Wait for it to be running. Submit the same job again. Result: the status of the new job switches to running almost immediately because it finds the existing running instance; so both jobs refer to the _same_ image. Version-Release number of selected component (if applicable): condor-deltacloud-gahp-7.6.5-0.16 condor-7.6.5-0.16 Expected results: Subsequent request of a running machine should be not considered (hold state maybe?)
Please note that when the instance is terminated by invoking shutdown inside it, the first job terminates; the second job instead stays alive and restarts the instance. Example of job: -------------------------------------------------- universe = grid grid_resource = deltacloud http://dc.example.com:3002/api executable = rhevm_job deltacloud_username = user@domain deltacloud_password_file = user_pwd_file deltacloud_instance_name = instance_name log = /tmp/job_deltacloud_basic_$(cluster)_$(process).log notification = NEVER queue -------------------------------------------------
presently we use instance.id which appears to not be unique, per "instance". /////////////////////////////////////////////////////////// struct deltacloud_instance { char *href; /**< The full URL to this instance */ char *id; /**< The ID of this instance */ char *name; /**< The name of this instance */ char *owner_id; /**< The owner ID of this instance */ char *image_id; /**< The ID of this image this instance was launched from */ char *image_href; /**< The full URL to the image */ char *realm_id; /**< The ID of the realm this instance is in */ char *realm_href; /**< The full URL to the realm this instance is in */ char *state; /**< The current state of this instance (RUNNING, STOPPED, etc) */ char *launch_time; /**< The time that this instance was launched */ struct deltacloud_hardware_profile hwp; /**< The hardware profile this instance was launched with */ struct deltacloud_action *actions; /**< A list of actions that can be taken on this instance */ struct deltacloud_address *public_addresses; /**< A list of the public addresses assigned to this instance */ struct deltacloud_address *private_addresses; /**< A list of the private addresses assigned to this instance */ struct deltacloud_instance_auth auth; /**< The authentication method used to connect to this instance */ struct deltacloud_instance *next; }; /////////////////////////////////////////////////////////// GridJobId = "deltacloud mrgqe6v32 924095d8-98e1-4774-9781-a01a8813b8b8" is the same for both? I need to dig some more, but it's possible we may need to create a hash with the launch_time && always iterate over ->next.
(In reply to comment #3) > GridJobId = "deltacloud mrgqe6v32 924095d8-98e1-4774-9781-a01a8813b8b8" > is the same for both? Yes, it is.
MRG-Grid is in maintenance and only customer escalations will be considered. This issue can be reopened if a customer escalation associated with it occurs.