EyadNasr
Cadet
Cadet
  • 1,081 Views

This course is now legacy content (DO457)

Jump to solution

For the following message:

"""

This course is now legacy content

This course based on Ansible 2.5 is using an outdated version of the technology and is now considered to be Legacy content. It will be removed from our catalog on March 01, 2024. Please be sure to complete your course and finish any remaining labs before that date. We recommend moving to the version 2.3 which is based on Red Hat Ansible Automation Platform 2.3.

"""

why is it recommended to move from version 2.5 course to the version 2.3 course? I don't get it.

1 Solution

Accepted Solutions
Wasim_Raja
Moderator
Moderator
  • 1,002 Views

@EyadNasr Thank you for reaching out.

The problem is that the numbers refer to different technologies/products. 2.5 is for Ansible core and 2.3 is for Ansible Automation Platform. AAP 2.3 is more recent than Ansible core 2.5. I believe AAP 2.3 uses Ansible core 2.13. If you just look at the numbers, you might think that 2.3 is older than 2.5, but that isn't the case.

View solution in original post

7 Replies
Wasim_Raja
Moderator
Moderator
  • 1,003 Views

@EyadNasr Thank you for reaching out.

The problem is that the numbers refer to different technologies/products. 2.5 is for Ansible core and 2.3 is for Ansible Automation Platform. AAP 2.3 is more recent than Ansible core 2.5. I believe AAP 2.3 uses Ansible core 2.13. If you just look at the numbers, you might think that 2.3 is older than 2.5, but that isn't the case.

Travis
Moderator
Moderator
  • 900 Views

Thanks, @Wasim_Raja for clearing this up. This is unfortunately a result of how the RHLS identifies courses (based on version number alone) so since it does see a 2.3 it automatically assumes the new 2.3 course is lower than 2.5. It doesn't know that the older version of the course wasn't even based on AAP and currently, there isn't even an AAP 2.5 version that exists. 

The versioning becomes even more complicated when you look at upstream and the Ansible project as they track by Ansible Core versions (can be mapped to a release of AAP) and Ansible versions (which are meaningless and can't directly be mapped to supported AAP).

Travis Michette, RHCA XIII
https://rhtapps.redhat.com/verify?certId=111-134-086
SENIOR TECHNICAL INSTRUCTOR / CERTIFIED INSTRUCTOR AND EXAMINER
Red Hat Certification + Training
  • 672 Views

This tells me that I should only study version 2.3 of the course if I plan to take the ex457 exam, next month, I should not touch version 2.5 of this same

 

  • 671 Views

This tells me that I should only study version 2.3 of the course if I plan to take the ex457 exam, next month, I should not touch version 2.5 of this

Travis
Moderator
Moderator
  • 661 Views

@javierenriqueco -

That is correct. The new version of the course is 2.3 as it is based on the version of AAP in the course which is AAP 2.3. I know this is confusing, but prior to Ansible Automation Platform (AAP) we were using other items like Ansible version and things for course versions. AAP 2.3 uses a much newer version as AAP 2.2 used ansible-core 2.13.4.

https://www.ansible.com/blog/whats-new-in-red-hat-ansible-automation-platform-2.3

https://access.redhat.com/documentation/en-us/red_hat_ansible_automation_platform/2.3/html/red_hat_a...

 

Travis Michette, RHCA XIII
https://rhtapps.redhat.com/verify?certId=111-134-086
SENIOR TECHNICAL INSTRUCTOR / CERTIFIED INSTRUCTOR AND EXAMINER
Red Hat Certification + Training
Wasim_Raja
Moderator
Moderator
  • 983 Views

@bonnevil Has updated few more points on it, let me share it here. Thank you @bonnevil.

AAP 2.3 (with Ansible Core 2.14) actually isn't "latest", that's AAP 2.4 (product) with Ansible Core 2.15 (component). But it's newer than Ansible 2.5 / Red Hat Ansible Engine 2.5 (the latter is a dead product name).

The Ansible Core name came in with Ansible Core 2.11, when "Ansible" began to mean the community distribution provided through Python's pip for Ansible Core + modules and "Ansible Core" just meant core tooling and the ansible.builtin Ansible Content Collection. Ansible Core 2.11 is part of Ansible 4 which is contemporary with AAP 2.0. (Ansible Base 2.10 was an experimental release that had "Ansible 3" as its community distribution and which Red Hat never supported.)

The community Ansible 7 contained Ansible Core 2.14, which the community no longer supports...but Red Hat still supports Ansible Core 2.14 in AAP 2.3. (And AAP isn't the same as community Ansible because we ship different package sets in the EEs.) Yes, it's all potentially confusing.

Community release cycle: https://docs.ansible.com/ansible/latest/reference_appendices/release_and_maintenance.html
Red Hat Ansible Automation Platform life cycle: https://access.redhat.com/support/policy/updates/ansible-automation-platform

Upstream right now is Ansible 9.1 which contains Ansible Core 2.16. That's what's in Fedora 39. We don't have a version of AAP with that version yet.

0 Kudos
Join the discussion
You must log in to join this conversation.