RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1638580 - Cluster needlessly tears down remote connections when container status is unknown
Summary: Cluster needlessly tears down remote connections when container status is unk...
Keywords:
Status: CLOSED DUPLICATE of bug 1448467
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pacemaker
Version: 7.6
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Ken Gaillot
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-10-12 01:38 UTC by Andrew Beekhof
Modified: 2018-10-12 14:19 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-12 14:19:49 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Andrew Beekhof 2018-10-12 01:38:27 UTC 
Description of problem:

A cleanup of a bundle's container causes the remote connection to be torn down before the cluster establishes the containers current state.


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


How reproducible:

100%


Steps to Reproduce:
1. create a bundle
2. erase the container's operation history

Actual results:

1. Sep 24 12:37:04 [360510] atl1-ctl02.mgmt.geix.cloud.ge.com       crmd:   notice: te_rsc_command:    Initiating monitor operation rabbitmq-bundle-docker-0_monitor_0 on atl1-ctl01 | action 35
2. Sep 24 12:37:04 [360510] atl1-ctl02.mgmt.geix.cloud.ge.com       crmd:   notice: te_rsc_command:    Initiating stop operation rabbitmq-bundle-0_stop_0 on atl1-ctl01 | action 52
3. Sep 24 12:37:04 [360510] atl1-ctl02.mgmt.geix.cloud.ge.com       crmd:  warning: status_from_rc:    Action 35 (rabbitmq-bundle-docker-0_monitor_0) on atl1-ctl01 failed (target: 7 vs. rc: 0): Error
4. Sep 24 12:37:04 [360510] atl1-ctl02.mgmt.geix.cloud.ge.com       crmd:     info: abort_transition_graph:    Transition aborted by operation rabbitmq-bundle-docker-0_monitor_0 'modify' on atl1-ctl01: Event failed | magic=0:0;35:488:7:b1378773-47a7-495a-94d7-99c8b87e85d3 cib=0.251.32 source=match_graph_event:310 complete=false
5. Sep 24 12:37:04 [360510] atl1-ctl02.mgmt.geix.cloud.ge.com       crmd:     info: match_graph_event:    Action rabbitmq-bundle-docker-0_monitor_0 (35) confirmed on atl1-ctl01 (rc=0)

Expected results:

2 should be ordered after 5, and in this case never run because of 4

1. Sep 24 12:37:04 [360510] atl1-ctl02.mgmt.geix.cloud.ge.com       crmd:   notice: te_rsc_command:    Initiating monitor operation rabbitmq-bundle-docker-0_monitor_0 on atl1-ctl01 | action 35
3. Sep 24 12:37:04 [360510] atl1-ctl02.mgmt.geix.cloud.ge.com       crmd:  warning: status_from_rc:    Action 35 (rabbitmq-bundle-docker-0_monitor_0) on atl1-ctl01 failed (target: 7 vs. rc: 0): Error
4. Sep 24 12:37:04 [360510] atl1-ctl02.mgmt.geix.cloud.ge.com       crmd:     info: abort_transition_graph:    Transition aborted by operation rabbitmq-bundle-docker-0_monitor_0 'modify' on atl1-ctl01: Event failed | magic=0:0;35:488:7:b1378773-47a7-495a-94d7-99c8b87e85d3 cib=0.251.32 source=match_graph_event:310 complete=false
5. Sep 24 12:37:04 [360510] atl1-ctl02.mgmt.geix.cloud.ge.com       crmd:     info: match_graph_event:    Action rabbitmq-bundle-docker-0_monitor_0 (35) confirmed on atl1-ctl01 (rc=0)

Additional info:

See attached scheduler input for test case
Upstream patch: https://github.com/ClusterLabs/pacemaker/commit/407f524
Comment 3 Ken Gaillot 2018-10-12 14:19:49 UTC 

*** This bug has been marked as a duplicate of bug 1448467 ***
Note You need to log in before you can comment on or make changes to this bug.