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

SyncIQ Policy Module fails when a resync_prep job is running on the cluster #7

Open
rbenigno opened this issue Oct 13, 2021 · 2 comments
Labels
triage/needs-investigation More investigation is required to reproduce.

Comments

@rbenigno
Copy link

Basic use of the SyncIQ Policy Module fails when there is a resync_prep job running on the cluster. The failure occurs even when the policy being targeted is not the policy the resync_prep job is running for.

Replicate as follows:

  • Create two SyncIQ policies and sync them to the target cluster (Policy1, Policy2)
  • Set Policy2 on the target cluster to allow writes
  • Run a resync-prep for Policy2 on the source cluster
  • Immediately run a Ansible playbook that attempts to get details for Policy1 (must run while the Policy2 resync-prep is still running
- name: Get SyncIQ policy details
  dellemc_powerscale_synciqpolicy:
    onefs_host: "{{onefs_host}}"
    api_user: "{{api_user}}"
    api_password: "{{api_password}}"
    verify_ssl: "{{verify_ssl}}"
    policy_name: "Policy1"
    state: "present"
TASK [Get SyncIQ policy details] *********************************************************************************************************************************************************************************************************************************
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Get jobs on SyncIQ policy Policy1 failed with error: Invalid value for `action` (resync_prep), must be one of ['copy', 'sync']"}

The error message reflects the current step of the resync_prep job, as seen in the log file:

2021-10-13 00:44:58,593 dellemc_powerscale_synciqpolicy.py ERROR : Get jobs on SyncIQ policy Policy1 failed with error: Invalid value for action(resync_prep), must be one of ['copy', 'sync'] 2021-10-13 00:45:02,759 dellemc_powerscale_synciqpolicy.py INFO : Got python SDK instance for provisioning on PowerScale 2021-10-13 00:45:03,053 dellemc_powerscale_synciqpolicy.py ERROR : Get jobs on SyncIQ policy Policy1 failed with error: Invalid value foraction(resync_prep), must be one of ['copy', 'sync'] 2021-10-13 00:45:05,706 dellemc_powerscale_synciqpolicy.py INFO : Got python SDK instance for provisioning on PowerScale 2021-10-13 00:45:06,000 dellemc_powerscale_synciqpolicy.py ERROR : Get jobs on SyncIQ policy Policy1 failed with error: Invalid value foraction(resync_prep_domain_mark), must be one of ['copy', 'sync'] 2021-10-13 00:45:09,089 dellemc_powerscale_synciqpolicy.py INFO : Got python SDK instance for provisioning on PowerScale 2021-10-13 00:45:09,376 dellemc_powerscale_synciqpolicy.py ERROR : Get jobs on SyncIQ policy Policy1 failed with error: Invalid value foraction(resync_prep_restore), must be one of ['copy', 'sync']

@anupamaloke
Copy link
Collaborator

@rajendraindukuri, @dattaarindam, fyi

@Jennifer-John
Copy link
Collaborator

Jennifer-John commented Nov 8, 2021

Hi @rbenigno,

This issue has been captured as a known issue and is captured as part of the release notes in https://github.com/dell/ansible-powerscale/blob/master/docs/Release%20Notes.md Also attaching a screenshot of the section for your reference.

Regarding your mention on policy1 failing with this error even though there is no resync_prep job running on policy1, as per design, since there could be running and scheduled jobs on a SyncIQ policy, to handle idempotency successfully, we have used the ISI SDK's list_jobs_api which will list all running and scheduled jobs (hence the error is displayed) as the api to list the jobs running on a policy returns only the current running job and not the scheduled jobs on the policy.

We will work on validating and updating the release notes once the fix is in place.

chrome_vKX75R0l2f

FYI @anupamaloke, @rajendraindukuri, @dattaarindam

Thanks,
Jennifer.

@anupamaloke anupamaloke added the triage/needs-investigation More investigation is required to reproduce. label Sep 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage/needs-investigation More investigation is required to reproduce.
Projects
None yet
Development

No branches or pull requests

3 participants