Ansible.netcommon broken with Ansible Core 2.19.0

Get Help
, ,
27

@felixfontein @mariolenz The concern is real. But we need to bump the dependency to make sure that the platform collection always resolves aka pulls in the correct version of netcommon, to support all versions of ansible-core that we are testing with that is 2.15 - 2.19 and devel, milestone.

Now,

  • Core ≤ 2.18

    • :white_check_mark: netcommon works fine up to v8.0.1
    • :white_check_mark: Platform collections (e.g., cisco.ios, cisco.nxos, arista.eos) are not impacted

  • Core = 2.19

    • :cross_mark: netcommon ≤ v8.0.1 → fails
    • :cross_mark: Platform collections depending on this netcommon also fail

  • Core = 2.19 + netcommon v8.1.0 (released)

    • :white_check_mark: netcommon itself works
    • :cross_mark: Platform collections still fail if someone is using things with/ later core 2.19.0, because they depend on the older netcommon (≤8.0.1)

  • Resolution

    • A major release is needed for the platform collections (cisco.ios, cisco.nxos, arista.eos, etc.)
    • They must bump their dependency to netcommon v8.1.0 minimum
    • After this coordinated release, everything will be consistent and fine.

We recommend doing major releases if we are dealing with breaking changes. Now, most of our customers/ community hooks into the latest releases of the collections anyways to address bug fixes and optimisation that goes in.

Regards

1 Like