Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1694310 - OCF:heartbeat:Route blocked
Summary: OCF:heartbeat:Route blocked
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: resource-agents
Version: 7.0
Hardware: x86_64
OS: Linux
Target Milestone: rc
: ---
Assignee: Oyvind Albrigtsen
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2019-03-30 11:50 UTC by Morteza Bashsiz
Modified: 2019-04-01 07:56 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)

Description Morteza Bashsiz 2019-03-30 11:50:34 UTC
Description of problem:

Resource Route do not move to other node in cluster and it has been blocked .

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

pcs --version

pacemakerd --version
Pacemaker 1.1.19-8.el7_6.4
Written by Andrew Beekhof

corosync -v
Corosync Cluster Engine, version '2.4.3'
Copyright (c) 2006-2009 Red Hat, Inc.

How reproducible:

When i restart network on the node which contains the main resource 

Steps to Reproduce:
1. systemctl restart network

Actual results:

[root@elk01 ~]# pcs status
Cluster name: pcs_cluster
Stack: corosync
Current DC: (version 1.1.19-8.el7_6.4-c3c624ea3d) - partition with quorum
Last updated: Sat Mar 30 16:03:21 2019
Last change: Sat Mar 30 15:45:53 2019 by hacluster via crmd on

2 nodes configured
3 resources configured

Online: [ ]

Full list of resources:

 external_vip	(ocf::heartbeat:IPaddr2):	Started
 internal_vip	(ocf::heartbeat:IPaddr2):	Started
 test_gw	(ocf::heartbeat:Route):	FAILED (blocked)

Failed Actions:
* external_vip_monitor_30000 on 'unknown error' (1): call=240, status=complete, exitreason='[findif] failed',
    last-rc-change='Sat Mar 30 15:51:36 2019', queued=0ms, exec=0ms
* internal_vip_monitor_30000 on 'unknown error' (1): call=242, status=complete, exitreason='[findif] failed',
    last-rc-change='Sat Mar 30 15:51:36 2019', queued=0ms, exec=0ms
* test_gw_stop_0 on 'not installed' (5): call=254, status=complete, exitreason='Source address appears not to be available on this system.',
    last-rc-change='Sat Mar 30 15:51:55 2019', queued=0ms, exec=71ms

Daemon Status:
  corosync: active/enabled
  pacemaker: active/enabled
  pcsd: active/enabled

Expected results:
I expect that resource relocate to elk02 based on following configuration 

[root@elk01 ~]# pcs constraint --full
Location Constraints:
Ordering Constraints:
  start external_vip then start internal_vip (kind:Optional) (id:order-external_vip-internal_vip-Optional)
  start internal_vip then start test_gw (kind:Optional) (id:order-internal_vip-test_gw-Optional)
Colocation Constraints:
  internal_vip with external_vip (score:INFINITY) (id:colocation-internal_vip-external_vip-INFINITY)
  test_gw with internal_vip (score:INFINITY) (id:colocation-test_gw-internal_vip-INFINITY)
Ticket Constraints:

Additional info:

Comment 2 Tomas Jelinek 2019-04-01 07:43:47 UTC
This seems to be a resource-agent related issue. Reassigning for further investigation.

Note You need to log in before you can comment on or make changes to this bug.