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

federation: updating an ExportedServiceSet does not always work

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Major
    • None
    • None
    • Customer Impact, Maistra
    • None

    Description

      After being hit by MAISTRA-2651, I decided to change the aliased namespace of an exported service to avoid a name clash on the importing mesh. It didn't seem to apply; on the federation ingress of the exporting mesh I saw the following errors when the importing mesh tried to access the service:

      [2021-09-07T09:06:58.759Z] "- - -" 0 - - rbac_access_denied_matched_policy[ns[mesh3-system]-policy[federation-exports-mesh2]-rule[0]] "-" 1391 0 24 - "-" "-" "-" "-" "10.217.0.134:9080" outbound|9080||ratings.mesh3-bookinfo.svc.cluster.local 10.217.0.109:44322 10.217.0.109:15443 10.217.0.142:54102 outbound_.9080_._.ratings.bookinfo3.svc.mesh2-exports.local -

      Restarting istiod in the exporting mesh solved the problem.

      Attachments

        Issue Links

          relates to

          Task - Represents a small unit of work that is not end-user facing. MAISTRA-2440 Verify importing services from multiple meshes into the same name works

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              Unassigned Unassigned
              dgrimm@redhat.com Daniel Grimm
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: