Skip to content

Clean up inconsistent min_ansible_version across roles #134

@geetikakay

Description

@geetikakay

Issue

Right now in meta/main.yml across the roles in this repo, we have a mix of min_ansible_version values. I greped it from repo.

roles/sap_vm_provision/meta/main.yml:  min_ansible_version: 2.12
roles/sap_hypervisor_node_preconfigure/meta/main.yml:  min_ansible_version: "2.9"
roles/sap_vm_verify/meta/main.yml:  min_ansible_version: 2.12
roles/sap_vm_preconfigure/meta/main.yml:  min_ansible_version: 2.9
roles/sap_vm_temp_vip/meta/main.yml:  min_ansible_version: 2.12 

So, three roles require at least 2.12, two still say 2.9. The issue is that according to Ansible’s official maintenance policy, only one major version is actively supported at any tim and both 2.9 and 2.12 are already EOL. Keeping old versions gives the impression we support it, but it’s long out of support upstream.

How to resolve

I suggest we should only consider testing and supporting limited (Extended maintenance and above)version which means it will be 2.18 on wards.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions