Upgrade python distro and create symlink to stunnel5

[dankova22]

Upgrade python distros. Add symlink for stunnel5 -> stunnel to keep backwards compatibility for upgrade process where binary is expected at /usr/bin/stunnel5.

[k8s-ci-robot]

Hi @dankova22. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[andrewjamesbrown]

@dankova22 is this PR/fix somehow related to this?

[andrewjamesbrown]

Upgrade python distros. Add symlink for stunnel5 -> stunnel to keep backwards compatibility for upgrade process where binary is expected at /usr/bin/stunnel5.

For my own info, what upgrade processes depend on /usr/bin/stunnel5 versus /usr/bin/stunnel?

[andrewjamesbrown]

It looks like the efs-utils code should be using this function to find the appropriate stunnel binary (which is different on AL2)

[andrewjamesbrown]

@dankova22 https://github.com/kubernetes-sigs/aws-efs-csi-driver/tree/master/docs#important-notes-on-efs-csi-driver-v2-upgrade

[mskanth972]

@andrewjamesbrown, when there are existing mounts using Stunnel5 binary and when we upgrade to EFS CSI Driver version which is using Stunnel, the mounts are breaking due to binary configuration change and pods are unable to read/write to the existing application. We have tested this and able to reproduce this scenario, so we are creating symlink.

[mskanth972]

/ok-to-test
/lgtm

[mskanth972]

It looks like the efs-utils code should be using this function to find the appropriate stunnel binary (which is different on AL2)

Looks like driver mentions stunnel explicitly in DockerFile, Unless we create a symlink (ln -s /usr/bin/stunnel /usr/bin/stunnel5), the mount process will fail.

[andrewjamesbrown]

@mskanth972 who knew that upgrading from AL2 to AL2023 would be so challenging :-)

[dankova22]

/retest

[dankova22]

/retest

[dankova22]

/test pull-aws-efs-csi-driver-external-test-eks
/test pull-aws-efs-csi-driver-e2e

[dankova22]

/retest

[mskanth972]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dankova22, mskanth972

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [mskanth972]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment