Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-39101

Repeating log message in aaq-controller pod after removing the Namespace

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • CNV v4.16.0
    • None
    • CNV Virtualization
    • None
    • 0.42
    • False
    • Hide

      None

      Show
      None
    • False
    • ---
    • ---
    • No

      Description of problem:

      There is a repeating message in aaq-controller pod logs (multiple times per second) after removing the Namespace from cluster:
      
      E0307 18:48:45.016823       1 aaq-gate-controller.go:248] AaqGateController: Error with key: ssp-general-test-machinetype err: namespaces "ssp-general-test-machinetype" not found
      E0307 18:48:45.211333       1 aaq-gate-controller.go:248] AaqGateController: Error with key: ssp-general-test-machinetype err: namespaces "ssp-general-test-machinetype" not found
      E0307 18:48:45.431168       1 aaq-gate-controller.go:248] AaqGateController: Error with key: ssp-general-test-machinetype err: namespaces "ssp-general-test-machinetype" not found
       .
      E0307 23:04:30.006015       1 aaq-gate-controller.go:248] AaqGateController: Error with key: ssp-general-test-machinetype err: namespaces "ssp-general-test-machinetype" not found
      

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

      4.15

      How reproducible:

      100%

      Steps to Reproduce:

      1. enable AAQ
      2. create namespace
      3. remove namespace
      

      Actual results:

      repeating message in logs

      Expected results:

      probably this message should not appear at all when namespace is deleted

      Additional info:

       

              bmordeha@redhat.com Barak Mordehai
              dshchedr@redhat.com Denys Shchedrivyi
              Kedar Bidarkar Kedar Bidarkar
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: