Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-3427

Dev console uses cluster-scoped instead of namespace-scoped resource queries for filters

    • False
    • None
    • False
    • NEW
    • VERIFIED
    • Before this change the dev console used cluster scoped queries instead of namespace scoped queries for filters. This change uses the correct scope and displays an error message when the user has no permission over the current namespace resources.
    • Log Storage - Sprint 229

      Description of problem:

      When a non-admin user selects a filter from the dropdown that includes pods or containers, it uses the cluster scoped API. This leads to an error as most non-admin users won't have permission over broad set of resources

      Version-Release number of selected component (if applicable):

      OCP 4.12
      Logging 5.6

      How reproducible:

      Always

      Steps to Reproduce:

      1. Enable Console plugin
      2. Create test projects using normal user
      3. Login to Openshift console as a normal user
      4. Switch to Developer mode
      5. Go to 'Aggregated logs' in 'Observe' menu
      6. In the filter Dropdown select "Pods" and click on "Filter by pod"

      Actual results:

      Error if the user does not have cluster-scoped list pods permission

      Expected results:

      No error when the user has namespace-scoped permissions to list pods

       

            [LOG-3427] Dev console uses cluster-scoped instead of namespace-scoped resource queries for filters

            Verified on logging 5.6, issue is fixed.

            Giriyamma Karagere Ramaswamy (Inactive) added a comment - Verified on logging 5.6, issue is fixed.

            CPaaS Service Account mentioned this issue in merge request !529 of openshift-logging / Log Collection Midstream on branch openshift-logging-5.6-rhel-8_upstream_2b996d6e2bcb5929846ff68fdba49e03:

            Updated US source to: b6cd028 Merge pull request #48 from jgbernalp/handle-resource-fetch-errors

            GitLab CEE Bot added a comment - CPaaS Service Account mentioned this issue in merge request !529 of openshift-logging / Log Collection Midstream on branch openshift-logging-5.6-rhel-8_ upstream _2b996d6e2bcb5929846ff68fdba49e03 : Updated US source to: b6cd028 Merge pull request #48 from jgbernalp/handle-resource-fetch-errors

            CPaaS Service Account mentioned this issue in merge request !528 of openshift-logging / Log Collection Midstream on branch openshift-logging-5.5-rhel-8_upstream_4b87b507d03af1b563179cde3f98d080:

            Updated US source to: b6cd028 Merge pull request #48 from jgbernalp/handle-resource-fetch-errors

            GitLab CEE Bot added a comment - CPaaS Service Account mentioned this issue in merge request !528 of openshift-logging / Log Collection Midstream on branch openshift-logging-5.5-rhel-8_ upstream _4b87b507d03af1b563179cde3f98d080 : Updated US source to: b6cd028 Merge pull request #48 from jgbernalp/handle-resource-fetch-errors

            GitLab CEE Bot added a comment - CPaaS Service Account mentioned this issue in merge request !524 of openshift-logging / Log Collection Midstream on branch openshift-logging-5.7-rhel-8_ upstream _c557cce913ee42bced302353d57c6b58 : Updated 2 upstream sources

            Tested using latest CPaaS build.

            The screen is getting stuck after clicking on "Filter by pod", after selecting "Pods"  filter from the Dropdown. (for non-admin user)

            Note: Works fine for non-admin user with admin role (oc adm policy add-cluster-role-to-user cluster-admin testuser-1)

            Giriyamma Karagere Ramaswamy (Inactive) added a comment - - edited Tested using latest CPaaS build. The screen is getting stuck after clicking on "Filter by pod", after selecting "Pods"  filter from the Dropdown. (for non-admin user) Note: Works fine for non-admin user with admin role (oc adm policy add-cluster-role-to-user cluster-admin testuser-1)

            GitLab CEE Bot added a comment - CPaaS Service Account mentioned this issue in merge request !520 of openshift-logging / Log Collection Midstream on branch openshift-logging-5.5-rhel-8_ upstream _12eb0f930e3a73c6a3713c9699fd38f0 : Updated 2 upstream sources

            GitLab CEE Bot added a comment - CPaaS Service Account mentioned this issue in merge request !515 of openshift-logging / Log Collection Midstream on branch openshift-logging-5.6-rhel-8_ upstream _ce1e3170ddff7bf64abfa51fbb56fa67 : Updated 2 upstream sources

            CPaaS Service Account mentioned this issue in merge request !510 of openshift-logging / Log Collection Midstream on branch openshift-logging-5.7-rhel-8_upstream_c8c39cccbcb17764cf2339f005214d83:

            Updated US source to: 9e2b3b2 Merge pull request #46 from jgbernalp/use-namespace-scoped-api-dev-console

            GitLab CEE Bot added a comment - CPaaS Service Account mentioned this issue in merge request !510 of openshift-logging / Log Collection Midstream on branch openshift-logging-5.7-rhel-8_ upstream _c8c39cccbcb17764cf2339f005214d83 : Updated US source to: 9e2b3b2 Merge pull request #46 from jgbernalp/use-namespace-scoped-api-dev-console

              gbernal@redhat.com Gabriel Bernal
              gbernal@redhat.com Gabriel Bernal
              Giriyamma Karagere Ramaswamy Giriyamma Karagere Ramaswamy (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: