Uploaded image for project: 'OpenShift Service Mesh'
  1. OpenShift Service Mesh
  2. OSSM-6766

OSSMC cannot update namespace or create Istio objects

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • OSSM 2.5.4, OSSM 2.6.1
    • OSSM 2.5.2, OSSM 2.6.0
    • Kiali
    • None
    • False
    • None
    • False
    • Release Notes
    • Release Notes
    • Previously, the plugin failed if the user wanted to update a namespace (e.g., enable/disable injection) or create any Istio object (e.g., create traffic policies). Now, the user can successfully update a namespace and create any Istio object.
    • Bug Fix

      Describe the bug

      An error appears when the user tries to update a namespace (e.g., enable/disable injection) or create any Istio object (e.g., create traffic policies).

      Expected Behavior

      The user should update any namespace or create any Istio object from OSSMC plugin

      What are the steps to reproduce this bug?

      1. Go to the overview page
      2. Click on the context menu of any namespace
      3. Click on enable/disable injection option
      4. Verify that an error appears and the namespace is not updated.

      Environment

      • OSSMC/Kiali version: Latest
      • OpenShift version: 4.15
      • Istio version: 1.22

            [OSSM-6766] OSSMC cannot update namespace or create Istio objects

            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 (Low: Red Hat OpenShift Service Mesh Containers for 2.5.4 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-2024:6210

            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 (Low: Red Hat OpenShift Service Mesh Containers for 2.5.4 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-2024:6210

            Gwynne Monahan added a comment -

            Thanks rh-ee-fhoyosle ! Never mind rhn-support-pmarek . I didn't realize the "Release Notes Text" field had been updated before you left your comment.

            Thank you Fernando for being on top of your Release Notes things! Much appreciated.

            Gwynne Monahan added a comment - Thanks rh-ee-fhoyosle ! Never mind rhn-support-pmarek . I didn't realize the "Release Notes Text" field had been updated before you left your comment. Thank you Fernando for being on top of your Release Notes things! Much appreciated.

            Fernando Hoyos Leyva added a comment - - edited

            rhn-support-gmonahan I already modified the release notes and status to Bug Fix after I resolved the issue. I think that's why rhn-support-pmarek says that there is no need to change release notes—they were actually updated some time ago

            Fernando Hoyos Leyva added a comment - - edited rhn-support-gmonahan I already modified the release notes and status to Bug Fix after I resolved the issue. I think that's why rhn-support-pmarek says that there is no need to change release notes—they were actually updated some time ago

            Gwynne Monahan added a comment -

            rhn-support-pmarek if it doesn't go as a Bug Fix, then it will remain a Known Issue. Is it to remain a Known Issue for 2.6.1?

            Gwynne Monahan added a comment - rhn-support-pmarek if it doesn't go as a Bug Fix, then it will remain a Known Issue. Is it to remain a Known Issue for 2.6.1?

            Pavel Marek added a comment - - edited

            Working as expected, imho no need to change release notes. cc rhn-support-gmonahan 

            Pavel Marek added a comment - - edited Working as expected, imho no need to change release notes. cc rhn-support-gmonahan  

            Gwynne Monahan added a comment -

            If this is now a "Fixed issue" for 2.6.1, please update the "Release Notes Text" field accordingly: "Previously, <X problem> caused <Y situation> (OPTIONAL: under the following <Z conditions>). Now, <fix> resolves the issue (OPTIONAL: and <agent> can <perform operation> successfully)."

            Please tag me when you have updated the "Release Notes Text" field. 

            Thanks!

            Gwynne Monahan added a comment - If this is now a "Fixed issue" for 2.6.1, please update the "Release Notes Text" field accordingly: "Previously, <X problem> caused <Y situation> (OPTIONAL: under the following <Z conditions>). Now, <fix> resolves the issue (OPTIONAL: and <agent> can <perform operation> successfully)." Please tag me when you have updated the "Release Notes Text" field.  Thanks!

            Gwynne Monahan added a comment -

            This has been moved from "Fixed issues" to "Kiali known issues" for 2.6.

            Gwynne Monahan added a comment - This has been moved from "Fixed issues" to "Kiali known issues" for 2.6.

            Pavel Marek added a comment -

            gmonahan please lets wait if we will be able to push new fix into upcoming release. All relevant updates should be mentioned in this ticket later

            Pavel Marek added a comment - gmonahan please lets wait if we will be able to push new fix into upcoming release. All relevant updates should be mentioned in this ticket later

            Fernando Hoyos Leyva added a comment -

            Hi rhn-support-pmarek,

            Although the result is the same (OSSMC cannot perform any POST requests), the original issue returned a 500 error code. The 403 Forbidden response seems to indicate some kind of security configuration issue (OSSMC does not have the rights to perform the POST request).

            Fernando Hoyos Leyva added a comment - Hi rhn-support-pmarek , Although the result is the same (OSSMC cannot perform any POST requests), the original issue returned a 500 error code. The 403 Forbidden response seems to indicate some kind of security configuration issue (OSSMC does not have the rights to perform the POST request).

            Gwynne Monahan added a comment - - edited

            Hey rhn-support-pmarek ,

            Since this bug seems to still be an issue, does it need to be removed from the "Fixed issues" section of 2.6 Release Notes?

            Gwynne Monahan added a comment - - edited Hey rhn-support-pmarek , Since this bug seems to still be an issue, does it need to be removed from the "Fixed issues" section of 2.6 Release Notes?

              rh-ee-fhoyosle Fernando Hoyos Leyva
              rh-ee-fhoyosle Fernando Hoyos Leyva
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: