Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-213

base image quay.io/operator-framework/ansible-operator. After moving to tag v1.20.0, it breaks the task to update k8s_status in an FIPS enabled cluster

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • 4.12.0
    • Operator SDK
    • Important
    • None
    • OSDK Sprint 223, OSDK 230, ODSK 231
    • 3
    • Rejected
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      a customer who has an ansible based operator using base image quay.io/operator-framework/ansible-operator. After moving to tag v1.20.0, it breaks the task to update k8s_status in an FIPS enabled cluster and the operator is unable to handle any CR, and the customer won't be able to install. The error also occurs on tag 1.19 so we are now forced to move back to v1.18.1.A similar issue has been reported at https://github.com/operator-framework/operator-sdk/issues/5723
      The ask is to have this fixed so that they can keep the base image up to date with all the security fixessince FIPS support is critical in their business offering. This should be fixed ASAP.

       

      Additional info:
      Slack thread - https://coreos.slack.com/archives/C3VS0LV41/p1660710956115889

            [OCPBUGS-213] base image quay.io/operator-framework/ansible-operator. After moving to tag v1.20.0, it breaks the task to update k8s_status in an FIPS enabled cluster

            Errata Tool added a comment -

            Since the problem described in this issue should be resolved in a recent advisory, it has been closed.

            For information on the advisory (Important: OpenShift Container Platform 4.12.3 security update), and where to find the updated files, follow the link below.

            If the solution does not work for you, open a new bug report.
            https://access.redhat.com/errata/RHSA-2023:0728

            Errata Tool added a comment - Since the problem described in this issue should be resolved in a recent advisory, it has been closed. For information on the advisory (Important: OpenShift Container Platform 4.12.3 security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2023:0728

            Keenon Lee added a comment -

            Verified.
            Tried v1.20.0 failed to reproduce

            Keenon Lee added a comment - Verified. Tried v1.20.0 failed to reproduce

            Keenon Lee added a comment -

            Verified

            Keenon Lee added a comment - Verified

            Catherine Chan-Tse added a comment - - edited

            Downgraded this to Major as a fix is available in Operator SDK 1.26.0. 

            Operator SDK 1.26.0 will be available in OpenShift as part of an upcoming OCP 4.12.z release.

            Catherine Chan-Tse added a comment - - edited Downgraded this to Major as a fix is available in Operator SDK 1.26.0.  Operator SDK 1.26.0 will be available in OpenShift as part of an upcoming OCP 4.12.z release.

            Jesus Rodriguez (Inactive) added a comment -

            Not an OCP blocker

            Jesus Rodriguez (Inactive) added a comment - Not an OCP blocker

            Harhar Rajan (Inactive) added a comment -

            amacdona hi is this bug resolved? seems like this has issue was fixed upstream with python kubernetes but doesn't appear to be released yet is that correct?

            Harhar Rajan (Inactive) added a comment - amacdona hi is this bug resolved? seems like this has issue was fixed upstream with python kubernetes but doesn't appear to be released yet is that correct?

              rh-ee-cchantse Catherine Chan-Tse
              rhn-support-bshaw Bikash Shaw
              Keenon Lee Keenon Lee
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: