Skip to content
This repository has been archived by the owner on Mar 20, 2023. It is now read-only.

Running job add with --recreate option fails to replace job #345

Open
VirtualShake opened this issue Mar 16, 2020 · 0 comments
Open

Running job add with --recreate option fails to replace job #345

VirtualShake opened this issue Mar 16, 2020 · 0 comments
Assignees
Labels

Comments

@VirtualShake
Copy link

Problem Description

When running the command batch-shipyard-3.9.1-cli-win-amd64.exe jobs add --configdir "myDir" --recreate, the process fails with error "The specified job schedule is already in completed state." I would expect the --recreate parameter to allow the same job name to be redeployed as per the description:

--recreate will recreate any completed jobs with the same id

Batch Shipyard Version

batch-shipyard 3.9.1

Steps to Reproduce

Run the jobs add command with an id matching that of one already deployed.

Expected Results

2020-03-16 18:16:20.565 INFO - Adding jobschedule oip-prp20-q to pool prp20-q-pool

Actual Results

File "site-packages\azure\batch\operations_job_schedule_operations.py", line 974, in add
azure.batch.models._models_py3.BatchErrorException: Request encountered an exception.
Code: JobScheduleCompleted
Message: {'additional_properties': {}, 'lang': 'en-US', 'value': 'The specified job schedule is already in completed state.\nRequestId:739261b3-2bdd-4129-8522-015a5aa8ceae\nTime:2020-03-16T22:31:33.5166779Z'}

@alfpark alfpark added the defect label Apr 21, 2021
@alfpark alfpark self-assigned this Apr 22, 2021
alfpark added a commit that referenced this issue Apr 26, 2021
alfpark added a commit that referenced this issue Mar 20, 2023
alfpark added a commit that referenced this issue Mar 20, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants