[Upgrades] remove "redhat-8.2.yml" from tripleo-ansible "tripleo_podman" role

[Cédric Jeanneret]

When running an upgrade from osp-16.1 (running rhel-8.2, container-tools:2.0) to osp-16.2 (running rhel-8.4, container-tools:3.0), we end in the following situation:
- running rhel-8.2
- container-tools:3.0 is enabled
- podman-3.x is available, and no podman-1.6.4

Since we have a task ensuring we have the correct stream ("Ensure DNF modules have the right stream"), we can safely remove that package pin.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/tripleo-ansible/+/789884

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/tripleo-ansible/+/789884
Committed: https://opendev.org/openstack/tripleo-ansible/commit/3304f4ab3591a87e5dd273a0f1559ed0f828342f
Submitter: "Zuul (22348)"
Branch: master

commit 3304f4ab3591a87e5dd273a0f1559ed0f828342f
Author: Cédric Jeanneret <email address hidden>
Date: Wed May 5 17:18:48 2021 +0200

    Remove redhat-8.2.yml var file

    This will not work when an operator wants to upgrades from osp-16.1 to
    osp-16.2:
    16.2 is targeting rhel-8.4 with container-tools:3.0, providing a newer
    podman version.

    During the upgrade process, we end in a state where we're still running
    rhel-8.2, with container-tools:3.0 enabled - leading to an issue when it
    comes to the podman version we can get.

    Removing this file (and backporting this change down to stable/train)
    will allow a swift and smooth fix.

    As a last word, this "last security" isn't that useful anymore, since we
    have a task that ensures we have the correct module stream[1][2].

    [1] https://opendev.org/openstack/tripleo-heat-templates/src/branch/master/deployment/undercloud/undercloud-upgrade.yaml#L67
    [2] https://opendev.org/openstack/tripleo-heat-templates/src/branch/master/deployment/tripleo-packages/tripleo-packages-baremetal-puppet.yaml#L261

    Closes-Bug: #1927242
    Change-Id: Id07aa060dd90fdef9a1cd0a44ddbeaee7d561d18

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/wallaby
Review: https://review.opendev.org/c/openstack/tripleo-ansible/+/789864

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/victoria
Review: https://review.opendev.org/c/openstack/tripleo-ansible/+/789865

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/ussuri
Review: https://review.opendev.org/c/openstack/tripleo-ansible/+/789866

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/train
Review: https://review.opendev.org/c/openstack/tripleo-ansible/+/790002

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/tripleo-ansible/+/789865
Committed: https://opendev.org/openstack/tripleo-ansible/commit/ac6cc2ae0d548a04c3022402bf2ba80b57719a07
Submitter: "Zuul (22348)"
Branch: stable/victoria

commit ac6cc2ae0d548a04c3022402bf2ba80b57719a07
Author: Cédric Jeanneret <email address hidden>
Date: Wed May 5 17:18:48 2021 +0200

    Remove redhat-8.2.yml var file

    This will not work when an operator wants to upgrades from osp-16.1 to
    osp-16.2:
    16.2 is targeting rhel-8.4 with container-tools:3.0, providing a newer
    podman version.

    During the upgrade process, we end in a state where we're still running
    rhel-8.2, with container-tools:3.0 enabled - leading to an issue when it
    comes to the podman version we can get.

    Removing this file (and backporting this change down to stable/train)
    will allow a swift and smooth fix.

    As a last word, this "last security" isn't that useful anymore, since we
    have a task that ensures we have the correct module stream[1][2].

    [1] https://opendev.org/openstack/tripleo-heat-templates/src/branch/master/deployment/undercloud/undercloud-upgrade.yaml#L67
    [2] https://opendev.org/openstack/tripleo-heat-templates/src/branch/master/deployment/tripleo-packages/tripleo-packages-baremetal-puppet.yaml#L261

    Closes-Bug: #1927242
    Change-Id: Id07aa060dd90fdef9a1cd0a44ddbeaee7d561d18
    (cherry picked from commit 3304f4ab3591a87e5dd273a0f1559ed0f828342f)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/tripleo-ansible/+/789866
Committed: https://opendev.org/openstack/tripleo-ansible/commit/0cc2857843fac13303e86fb8cf268838afbd6032
Submitter: "Zuul (22348)"
Branch: stable/ussuri

commit 0cc2857843fac13303e86fb8cf268838afbd6032
Author: Cédric Jeanneret <email address hidden>
Date: Wed May 5 17:18:48 2021 +0200

    Remove redhat-8.2.yml var file

    This will not work when an operator wants to upgrades from osp-16.1 to
    osp-16.2:
    16.2 is targeting rhel-8.4 with container-tools:3.0, providing a newer
    podman version.

    During the upgrade process, we end in a state where we're still running
    rhel-8.2, with container-tools:3.0 enabled - leading to an issue when it
    comes to the podman version we can get.

    Removing this file (and backporting this change down to stable/train)
    will allow a swift and smooth fix.

    As a last word, this "last security" isn't that useful anymore, since we
    have a task that ensures we have the correct module stream[1][2].

    [1] https://opendev.org/openstack/tripleo-heat-templates/src/branch/master/deployment/undercloud/undercloud-upgrade.yaml#L67
    [2] https://opendev.org/openstack/tripleo-heat-templates/src/branch/master/deployment/tripleo-packages/tripleo-packages-baremetal-puppet.yaml#L261

    Closes-Bug: #1927242
    Change-Id: Id07aa060dd90fdef9a1cd0a44ddbeaee7d561d18
    (cherry picked from commit 3304f4ab3591a87e5dd273a0f1559ed0f828342f)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/tripleo-ansible/+/790002
Committed: https://opendev.org/openstack/tripleo-ansible/commit/3c614f938e010ad47679358a7e9ee407aa5792d3
Submitter: "Zuul (22348)"
Branch: stable/train

commit 3c614f938e010ad47679358a7e9ee407aa5792d3
Author: Cédric Jeanneret <email address hidden>
Date: Wed May 5 17:18:48 2021 +0200

    Remove redhat-8.2.yml var file

    This will not work when an operator wants to upgrades from osp-16.1 to
    osp-16.2:
    16.2 is targeting rhel-8.4 with container-tools:3.0, providing a newer
    podman version.

    During the upgrade process, we end in a state where we're still running
    rhel-8.2, with container-tools:3.0 enabled - leading to an issue when it
    comes to the podman version we can get.

    Removing this file (and backporting this change down to stable/train)
    will allow a swift and smooth fix.

    As a last word, this "last security" isn't that useful anymore, since we
    have a task that ensures we have the correct module stream[1][2].

    [1] https://opendev.org/openstack/tripleo-heat-templates/src/branch/master/deployment/undercloud/undercloud-upgrade.yaml#L67
    [2] https://opendev.org/openstack/tripleo-heat-templates/src/branch/master/deployment/tripleo-packages/tripleo-packages-baremetal-puppet.yaml#L261

    Closes-Bug: #1927242
    Change-Id: Id07aa060dd90fdef9a1cd0a44ddbeaee7d561d18
    (cherry picked from commit 3304f4ab3591a87e5dd273a0f1559ed0f828342f)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/tripleo-ansible/+/789864
Committed: https://opendev.org/openstack/tripleo-ansible/commit/d42023b88ab59f6fb7685ba1b83b1b90fcac834a
Submitter: "Zuul (22348)"
Branch: stable/wallaby

commit d42023b88ab59f6fb7685ba1b83b1b90fcac834a
Author: Cédric Jeanneret <email address hidden>
Date: Wed May 5 17:18:48 2021 +0200

    Remove redhat-8.2.yml var file

    This will not work when an operator wants to upgrades from osp-16.1 to
    osp-16.2:
    16.2 is targeting rhel-8.4 with container-tools:3.0, providing a newer
    podman version.

    During the upgrade process, we end in a state where we're still running
    rhel-8.2, with container-tools:3.0 enabled - leading to an issue when it
    comes to the podman version we can get.

    Removing this file (and backporting this change down to stable/train)
    will allow a swift and smooth fix.

    As a last word, this "last security" isn't that useful anymore, since we
    have a task that ensures we have the correct module stream[1][2].

    [1] https://opendev.org/openstack/tripleo-heat-templates/src/branch/master/deployment/undercloud/undercloud-upgrade.yaml#L67
    [2] https://opendev.org/openstack/tripleo-heat-templates/src/branch/master/deployment/tripleo-packages/tripleo-packages-baremetal-puppet.yaml#L261

    Closes-Bug: #1927242
    Change-Id: Id07aa060dd90fdef9a1cd0a44ddbeaee7d561d18
    (cherry picked from commit 3304f4ab3591a87e5dd273a0f1559ed0f828342f)

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-ansible 3.1.1 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-ansible 2.3.0 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-ansible 0.8.0 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-ansible 1.5.4 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-ansible 4.0.0 release.