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

vmware_cluster_ha - add set of heartbeat datastores #1663

Closed
wants to merge 0 commits into from

Conversation

Nina2244
Copy link
Contributor

@Nina2244 Nina2244 commented Mar 7, 2023

SUMMARY

Add the possibility to set the heartbeat datastores of an cluster.

ISSUE TYPE
  • Feature Pull Request
COMPONENT NAME

vmware_cluster_ha

ADDITIONAL INFORMATION

@mariolenz
Copy link
Collaborator

@Nina2244 It looks like you broke idempotency somehow:

TASK [vmware_cluster_ha : assert] **********************************************
task path: /home/zuul/.ansible/collections/ansible_collections/community/vmware/tests/integration/targets/vmware_cluster_ha/tasks/main.yml:80
fatal: [testhost]: FAILED! => {
    "assertion": "not change_apd_response_again.changed",
    "changed": false,
    "evaluated_to": false,
    "msg": "Assertion failed"
}

PLAY RECAP *********************************************************************
testhost                   : ok=23   changed=11   unreachable=0    failed=1    skipped=14   rescued=0    ignored=0

ansible-test-cloud-integration-vcenter7_only-stable214

@mariolenz
Copy link
Collaborator

@Nina2244 I'm afraid your PR still breaks things:

TASK [vmware_cluster_ha : assert] **********************************************
task path: /home/zuul/.ansible/collections/ansible_collections/community/vmware/tests/integration/targets/vmware_cluster_ha/tasks/main.yml:80
fatal: [testhost]: FAILED! => {
    "assertion": "not change_apd_response_again.changed",
    "changed": false,
    "evaluated_to": false,
    "msg": "Assertion failed"
}

ansible-test-cloud-integration-vcenter7_only-stable214

@Nina2244
Copy link
Contributor Author

Nina2244 commented May 2, 2023

@mariolenz can you please trigger a recheck? So I can try to fix it. Because there the current check isn't possible to read anymore.

@mariolenz
Copy link
Collaborator

recheck

@mariolenz
Copy link
Collaborator

@Nina2244 I think the last CI run failed because of #1723

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

Successfully merging this pull request may close these issues.

2 participants