Receptor version compatibility

Get Help
,
1

Hi there,

I have a question regarding receptor version compatibility.

  • In our EE we use receptor:devel (like in awx/awx-ee), which currently points at receptor ~1.5.3
  • On our Execution Nodes (RHEL9), OS repos provide receptor 1.4.4

This combination (AWX EE running receptor:devel and Execution Node running receptor:1.4.4) seems to work fine, but is it “supported”/recommended?

The EE image is rebuilt nightly so, its receptor version stays up to date. If Execution Nodes are not constantly updated (with non-OS packages) as well there is bound to be some kind of drift.

The most careful approach might be, pinning receptor within EE (in contrast to awx/awx-ee) and moving pin forward regularly in sync with execution nodes.

What is the recommended strategy to keep everything working well together?

2

While we do our best to ensure backwards compatibility our testing suits only test mesh’s that have a common version, e.g. everything 1.4.4 or everything 1.5.3,

Mixing receptor versions is best effort on our part and not “supported”

I hope this makes sense. So far we have one receptor version that is not backwards compatible due to a known bug on the internal workunit id, so please avoid v1.5.0.

This version was never officially released in AAP so you should only get it if you manually install it.

2 Likes
3

Thank you very much for clearing that up for me. :slight_smile:

4

If anyone is interested, what I started doing in regard to receptor on each AWX Update

For our custom EE build:

  • look up and apply ansible.receptor pin for resp. AWX version
  • Pin receptor version to the latest version released at the time of above collection version

On Execution nodes:

  • Update receptor to same version