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

Revert "Ansible-runner: Fix getting status of playbook" and Revert "Set initial event number for async ansible commands" #496

Closed

Conversation

mnecas
Copy link
Member

@mnecas mnecas commented Jun 27, 2022

Reverts #468 and #499

@mnecas mnecas force-pushed the revert-468-fix_ansible_polling_status branch from 49b9fbe to 3c101d7 Compare June 28, 2022 09:55
@mnecas mnecas changed the title Revert "Ansible-runner: Fix getting status of playbook" Revert "Ansible-runner: Fix getting status of playbook" and Revert "Set initial event number for async ansible commands" Jun 28, 2022
@ahadas ahadas requested a review from liranr23 June 28, 2022 10:19
@ahadas
Copy link
Member

ahadas commented Jun 28, 2022

Reverts #468 and #499

@mnecas can you please elaborate on what's the reason for reverting those patches?

@mwperina
Copy link
Member

/ost

@liranr23
Copy link
Member

Reverts #468 and #499

@mnecas can you please elaborate on what's the reason for reverting those patches?

it didn't resolve the OST failures we saw. the failures started to appear once the initial PR was merged.

@michalskrivanek
Copy link
Member

it doesn't make sense to blindly change things or revert, added more debugging now in #502 and once we see the issue again it should give us more insight into what's going on. Then we can see what fix or revert is needed

@ahadas
Copy link
Member

ahadas commented Jun 28, 2022

Reverts #468 and #499

@mnecas can you please elaborate on what's the reason for reverting those patches?

it didn't resolve the OST failures we saw. the failures started to appear once the initial PR was merged.

I agree with Michal's comment above but I meant to elaborate within the commit message or/and the description of the PR so we'll be able to tell later on, if needed, why it was reverted

@mnecas mnecas requested a review from ljelinkova as a code owner July 20, 2022 12:06
@mnecas
Copy link
Member Author

mnecas commented Jul 21, 2022

/ost

@michalskrivanek
Copy link
Member

#546 fixed it good enough

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.

5 participants