Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing parameter start_time in tasks/oracle_job.yml #72

Closed
jxj191 opened this issue Mar 7, 2022 · 1 comment
Closed

Missing parameter start_time in tasks/oracle_job.yml #72

jxj191 opened this issue Mar 7, 2022 · 1 comment
Assignees

Comments

@jxj191
Copy link

jxj191 commented Mar 7, 2022

🐛 Bug Report

(A clear and concise description of what the bug is)

The oracle_job can take start_time as an input for setting the job's custom start time. The Python code library/cohesity_oracle_job.py expects the parameter start_time as part of the input params from the oracle_job task. As the argument start_time is not specified in the tasks/oracle_job.yml , the python code library/cohesity_oracle_job.py sets the default value of the start_time as null always. Can you please fix the tasks/oracle_job.yml to include start_time as an argument.

To Reproduce

(Write your steps here:)

  1. create a playbook for Oracle Protection job with start_time as a paramater
  2. When the play book is executed, the start_time that we set in the playbbok is not reflected in the Job created at Cohesity

Expected behavior

(Write what you thought would happen.)

Actual Behavior

(Write what happened. Add screenshots, if applicable.)

@naveena-maplelabs
Copy link
Contributor

We are looking into this and add a fix to the cohesity collections.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants