This repository has been archived by the owner on Jun 13, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 105
Check mode not working properly for the helm module when deploying releases #280
Comments
@arcalys Thanks for reporting this issue. I will try to reproduce this at my end. |
Akasurde
added a commit
to Akasurde/community.kubernetes
that referenced
this issue
Oct 22, 2020
Fixes: ansible-collections#280 Signed-off-by: Abhijeet Kasurde <[email protected]>
resolved_by_pr #281 |
@Akasurde Cheers |
Akasurde
added a commit
to Akasurde/community.kubernetes
that referenced
this issue
Oct 22, 2020
Fixes: ansible-collections#280 Signed-off-by: Abhijeet Kasurde <[email protected]>
Akasurde
added a commit
to Akasurde/community.kubernetes
that referenced
this issue
Oct 22, 2020
Fixes: ansible-collections#280 Signed-off-by: Abhijeet Kasurde <[email protected]>
geerlingguy
pushed a commit
that referenced
this issue
Oct 22, 2020
Fixes: #280 Signed-off-by: Abhijeet Kasurde <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
SUMMARY
I am trying to install a few Helm releases into a local and staging kubernetes clusters through Ansible using the Helm module. However, when running check mode, it always fails if the release does not exist.
It seems to be related to that change: 7946b39#diff-25ae73979f193a414d8f45fc01c829eb4eb80cf46777c882108ceb7c20f2dc0d
It does not check, if in check_mode, if release_status is null/None.
ISSUE TYPE
COMPONENT NAME
community/kubernetes/plugins/modules/helm.py
ANSIBLE VERSION
CONFIGURATION
OS / ENVIRONMENT
Ubuntu 20.04
STEPS TO REPRODUCE
Hosts file:
Vars:
Playbook:
ansible.cfg:
ansible-playbook --diff playbooks/install.yaml --limit local --check
EXPECTED RESULTS
I would expect the check mode to work properly and display a changed status:
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: