Bind the install bundle to the ansible.receptor collection 2.0.8 version#16396
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
📝 WalkthroughWalkthroughUpdated the Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Branch protection rule check failed
|



SUMMARY
Bind the install bundle to the ansible.receptor collection 2.0.8 version。
As per https://github.com/ansible/receptor-collection/releases , the ansible.receptor collection 2.0.7 & 2.0.8 mainly extend support for RHEL 10 mesh nodes and comply with Certified Content requirements.
It looks like during https://redhat.atlassian.net/browse/ANSTRAT-1732 , @PabloHiro directly backported such update to AAP 2.6. From an AoC perspective, we think this is still required for AAP 2.7.
ISSUE TYPE
COMPONENT NAME
STEPS TO REPRODUCE AND EXTRA INFO
Install RHEL 10 instances as execution nodes to AAP Controller with the ansible.receptor collection 2.0.6 version without fuse-overlayfs and slirp4netns pre-installed will finally fail to run jobs/playbooks on them.
Summary by CodeRabbit