Forum Discussion
OK.. I've found the right eyes and this is unexpected behavior. I'd bet we'd see a new release shortly, but more soon.
- AubreyKingF5Jan 05, 2023Admin
You bet, Mike. OK.. this is absolutely unexpected. I got a pair of eyes on it and they see the issue, but we can't just fix it without a registered issue. If you could take a moment and register it on the collection's git issues, I can get someone to try to get on that asap.:
https://github.com/F5Networks/f5-ansible/issues
If you cannot get to that, let me know.
- Mike_AJan 05, 2023Nimbostratus
Here you are. Let me know if there is anything else you need from me. Thanks!
- AubreyKingF5Jan 06, 2023Admin
Thank you so much for posting it! This will help anyone else who runs into this between now and when it's fixed in the repo.
- Mike_AJan 09, 2023Nimbostratus
Aubrey, seems like someone on the F5 side has looked at the issue and is now saying that i musing the wrong version of the collection and/or Ansible version. I thouhgt someone internally had observed the issue and knew what needed to be resolved. Is this the same person who is commenting on the issue?
- AubreyKingF5Jan 10, 2023Admin
Checked back in. I must have misunderstood him on that. He was just telling me he saw the collection and who would look at it. Are you all the way up on Ansible?
- Mike_AJan 10, 2023Nimbostratus
No we are not at the latest. Im asking our automation team who manages the platform to get me a venv that I can apply to the template and run again using ansible 4.
- AubreyKingF5Jan 10, 2023Admin
I have had similar issues in the past. The last time, though, I had a horrible time getting the right package installed by the server maintainer.