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

no_log even when task_result doesn't provide key #41414

Merged
merged 2 commits into from
Jun 12, 2018

Conversation

bcoca
Copy link
Member

@bcoca bcoca commented Jun 11, 2018

SUMMARY
  • now also checks task property
  • added reproducer to tests for unreachable status on item loop
ISSUE TYPE
  • Bugfix Pull Request
COMPONENT NAME

task result

ANSIBLE VERSION
>=2.4

 - now also checks task property
 - added reproducer to tests for unreachable status on item loop
insertafter: EOF
line: "machine {{ item.machine }} login {{ item.login }} password {{ item.password }}"
loop: "{{ logins }}"
no_log: true
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should there be an assert that checks that DO_NOT_LOG_UNREACHABLE_ITEM is not in the output of the task somehow ?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

in runme.sh, it was already part of existing tests

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah, gotcha.

@ansibot ansibot added affects_2.7 This issue/PR affects Ansible v2.7 bug This issue/PR relates to a bug. needs_triage Needs a first human triage before being processed. support:community This issue/PR relates to code supported by the Ansible community. support:core This issue/PR relates to code supported by the Ansible Engineering Team. test This PR relates to tests. labels Jun 11, 2018
@bcoca bcoca removed the needs_triage Needs a first human triage before being processed. label Jun 11, 2018
@abadger
Copy link
Contributor

abadger commented Jun 11, 2018

+1 to merge

@abadger
Copy link
Contributor

abadger commented Jun 11, 2018

Also needs backporting to stable-2.6, stable-2.5 and stable-2.4

@ansibot ansibot added the shipit This PR is ready to be merged by Core label Jun 11, 2018
@abadger
Copy link
Contributor

abadger commented Jun 12, 2018

Hmm,.. this does need a change log fragment, though. (Which will make backporting to 2.6 and 2.5 easier but will have to be changed for 2.4)

@ansibot ansibot added needs_revision This PR fails CI tests or a maintainer has requested a review/revision of the PR. and removed shipit This PR is ready to be merged by Core labels Jun 12, 2018
@abadger
Copy link
Contributor

abadger commented Jun 12, 2018

The unstable test result is unrelated merging and openin backports.

@abadger abadger merged commit 5fdd101 into ansible:devel Jun 12, 2018
@bcoca bcoca deleted the no_log_fail branch July 3, 2018 20:12
@ansible ansible locked and limited conversation to collaborators Jun 12, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
affects_2.7 This issue/PR affects Ansible v2.7 bug This issue/PR relates to a bug. needs_revision This PR fails CI tests or a maintainer has requested a review/revision of the PR. support:community This issue/PR relates to code supported by the Ansible community. support:core This issue/PR relates to code supported by the Ansible Engineering Team. test This PR relates to tests.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants