Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-10052

Missing events in consumer after restarting hw-event-proxy with HTTP transport

XMLWordPrintable

    • No
    • CNF RAN Sprint 233, CNF RAN Sprint 234, CNF RAN Sprint 235, CNF RAN Sprint 236
    • 4
    • False
    • Hide

      None

      Show
      None
    • Rel Note for Telco: Not Required (4.12) - this has moved to 4.13 (see note from Yang below)

      This is a clone of issue OCPBUGS-2832. The following is the description of the original issue:

      Starting with a working BMER setup, using http sidecar and a consumer, the consumer gets the events.

      I then restart the hw-event-proxy pod, and wait until the new pod is ready to receive messages.

      I then send ten more messages, and see them received in the hw-event-proxy log.

      But they do not appear in the consumer.

      This test case worked ok with 4.11 and AMQ sidecar.

      Reproduce steps:

      1. deploy SNO cluster with BMER
      2.  Clone https://gitlab.cee.redhat.com/cnf/cnf-gotests tests
      3. Set BMC_HOSTS to redfish address, sent to developer.
      4. Set BMC_USER and BMC_PASSWORD
      5. run the test: FEATURES="ranhwevent" make test-features
      6. test will configure the application and deploys the consumer
      7. wait for the consumer to be deployed
      8. connect to the consumer logs, you can use this:  
        oc logs -n openshift-bare-metal-events $(oc get pods -n openshift-bare-metal-events|awk '/consumer.*Running/ {print $1}') -f 
      1. wait for the test to restart the hw-event-proxy pod
      2. when the test sends events again to the new pod
      3. See that the consumer gets no new events after the new pod is created.

       
      Note:

       
      A workaround is to destroy the consumer and recreate it and then new events arrive.

       

            jacding@redhat.com Jack Ding
            openshift-crt-jira-prow OpenShift Prow Bot
            Bonnie Block Bonnie Block
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: