Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-17851

Pacemaker reported rabbitmq failure, but no problem found in rabbitmq logs

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Major Major
    • None
    • rhos-17.1.3
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • None
    • Moderate

      A problem was reported in RHOSP 17.1.3 environment with TLS-everywhere: nodes periodically fail monitoring without sign of actual problems in rabbitmq logs.

      Although this looks close to https://bugzilla.redhat.com/show_bug.cgi?id=2290861 / https://issues.redhat.com/browse/OSPRH-13633 , error pattern is different and tlsv1.2 was set in configuration.

      In /var/log/messages I can see the following message indicating that mnesia is not well:

      Jun 25 12:44:32 controller02 rabbitmq-cluster(rabbitmq)[110768]: INFO: RabbitMQ server could not get cluster status from mnesia

      But I can't find related errors in this node, or other node's rabbitmq logs.

      I want to kindly ask for expert look here

      Bug impact
      RabbitMQ crushes periodically and may break some overcloud operations

      Known workaround
      None

      Additional context
      To be provided privately

              Unassigned Unassigned
              rhn-support-astupnik Alex Stupnikov
              rhos-dfg-pidone
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: