Uploaded image for project: 'Maistra'
  1. Maistra
  2. MAISTRA-2670

ossm 2.1 Federation single cluster service export takes more than 5 mins

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • maistra-2.1.0
    • maistra-2.1.0
    • None
    • None
    • False
    • False
    • Sprint 10, Sprint 11

    Description

      ossm 2.1 Federation single cluster install istiod-fed-export connected false

      I tested 2.1 federaion example in a single OCP 4.8 cluster. Reference:
      [1] https://github.com/maistra/istio/blob/maistra-2.1/pkg/servicemesh/federation/example/config-poc/install.sh

      In the mesh1-system status shows :

      "status": {
        "discoveryStatus": {
            "active": [
                {
                    "pod": "istiod-fed-export-bcdb77c59-tt7g4",
                    "remotes": [
                        {
                            "connected": false,
                            "lastConnected": "2021-09-14T02:57:27Z",
                            "lastDisconnect": "2021-09-14T02:58:41Z",
                            "lastEvent": "2021-09-14T02:57:56Z",
                            "lastFullSync": "2021-09-14T02:57:27Z",
                            "source": "10.131.0.62"
                        }
                    ],
                    "watch": {
                        "connected": true,
                        "lastConnected": "2021-09-14T02:57:28Z",
                        "lastDisconnectStatus": "503 Service Unavailable",
                        "lastFullSync": "2021-09-14T02:57:28Z"
                    }
                }
            ]

      And there is no result from 

       oc -n mesh2-system get importedservicesets mesh1 -o json | jq .status

      After 6 mins, I can see the export working and see services imported into mesh2.

      Attachments

        Issue Links

          is caused by

          Bug - A problem that impairs or prevents the functions of the product. MAISTRA-2682 Watch mechanism in federation does not work

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. MAISTRA-2645 Peers take a long time to stablish connection

          • 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

              mluksa@redhat.com Marko Luksa
              yuaxu@redhat.com Yuanlin Xu
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: