Uploaded image for project: 'Network Observability'
  1. Network Observability
  2. NETOBSERV-1798

Multitenant console with Loki: cannot set namespace filters

XMLWordPrintable

    • False
    • None
    • False
    • Hide
      Previously, for non cluster admin users having access to NetObserv, an error was showing up in the console plugin when they tried to filter for something that triggered auto-completion, such as a namespace.
      Now no error is displayed is the auto-completion returns the expected results.
      Show
      Previously, for non cluster admin users having access to NetObserv, an error was showing up in the console plugin when they tried to filter for something that triggered auto-completion, such as a namespace. Now no error is displayed is the auto-completion returns the expected results.
    • NetObserv - Sprint 257, NetObserv - Sprint 258, NetObserv - Sprint 259

      Description of problem:

      When setting up multi-tenancy (follow steps here: https://github.com/netobserv/documents/blob/main/loki_operator.md#testing-multi-tenancy ) it's not possible to set a namespace filter, as we get a 503 error:

       

      The UI would not let us validate the free text, even without auto-completion, because of this error.

       

      If namespace auto-completion is not possible to achieve in multi-tenant mode, we should at least not block setting any custom text here.

        1. Capture d’écran du 2024-08-12 16-54-52.png
          20 kB
          Joel Takvorian

            [NETOBSERV-1798] Multitenant console with Loki: cannot set namespace filters

            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: Network Observability 1.7.0 for OpenShift), 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:8014

            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: Network Observability 1.7.0 for OpenShift), 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:8014

            GitLab CEE Bot added a comment -

            CPaaS Service Account mentioned this issue in merge request !585 of netobserv-midstream / Network Observability Operator Midstream on branch network-observability-1.7.0-rhel-9_upstream_9bbe612163e4744e7ee1b5f788dac164:

            Updated 4 upstream sources

            GitLab CEE Bot added a comment - CPaaS Service Account mentioned this issue in merge request !585 of netobserv-midstream / Network Observability Operator Midstream on branch network-observability-1.7.0-rhel-9_ upstream _9bbe612163e4744e7ee1b5f788dac164 : Updated 4 upstream sources

            Amogh Rameshappa Devapura added a comment -

            okay closing all the related JIRA's for this PR then

            Amogh Rameshappa Devapura added a comment - okay closing all the related JIRA's for this PR then

            Julien Pinsonneau added a comment -

            Let's fix separately as I already abused of this PR bringing multiple fixes  

            Thanks rhn-support-aramesha !

            Julien Pinsonneau added a comment - Let's fix separately as I already abused of this PR bringing multiple fixes   Thanks rhn-support-aramesha !

            Amogh Rameshappa Devapura added a comment -

            Raised bug https://issues.redhat.com/browse/NETOBSERV-1885 for above issue. jtakvori jpinsonn@redhat.com Do you guys want to fix it in the same PR or a separate PR? I dont mind anything. If latter, I will add qe-approved label to the attached PR and you guys can work on a separate PR. Let me know

            Amogh Rameshappa Devapura added a comment - Raised bug https://issues.redhat.com/browse/NETOBSERV-1885 for above issue. jtakvori jpinsonn@redhat.com Do you guys want to fix it in the same PR or a separate PR? I dont mind anything. If latter, I will add qe-approved label to the attached PR and you guys can work on a separate PR. Let me know

            Amogh Rameshappa Devapura added a comment -

            jtakvori I dont see the error when filtering on namespace or other fields in both administrator view as well as Developer view. 

            But I do get error when I try to filter on Destination or Source Resource in prom view since there is no Resource scope available in prom view. So, I think that filter should be automatically removed when we are querying on prom view so that users dont get confused. Otherwise LGTM

            Cluster details:

            • OCP: 4.16.0-0.nightly-2024-09-18-053141
            • NetObserv operator: v1.7.0
            • Loki: v6.0.0
            • eBPF-agent: v1.7.0-47
            • FLP: v1.7.0-47
            • ConsolePlugin: e61421c

            Amogh Rameshappa Devapura added a comment - jtakvori I dont see the error when filtering on namespace or other fields in both administrator view as well as Developer view.  But I do get error when I try to filter on Destination or Source Resource in prom view since there is no Resource scope available in prom view. So, I think that filter should be automatically removed when we are querying on prom view so that users dont get confused. Otherwise LGTM Cluster details: OCP: 4.16.0-0.nightly-2024-09-18-053141 NetObserv operator: v1.7.0 Loki: v6.0.0 eBPF-agent: v1.7.0-47 FLP: v1.7.0-47 ConsolePlugin: e61421c

              jtakvori Joel Takvorian
              jtakvori Joel Takvorian
              Amogh Rameshappa Devapura Amogh Rameshappa Devapura
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: