Bug 713071

Summary: Entering ip/subnet mask in field of ip address resource in cluster.conf prevents ip address to come up
Product: Red Hat Enterprise Linux 5 Reporter: Elvir Kuric <ekuric>
Component: cmanAssignee: Lon Hohberger <lhh>
Status: CLOSED WORKSFORME QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.6CC: cluster-maint, edamato
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-05-16 13:12:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Elvir Kuric 2011-06-14 07:51:11 UTC 
Description of problem:

If by accident in cluster.conf is for ip resource specified as 

<ip address="192.168.122.11/24" monitor_link="1"/>

then no error will be reported during cluster start, and this error in configuration will be possible to propagate to cluster nodes. 

Entering above is not possible via luci interface - as there is not space, this is only possible when manually editing cluster.conf. 

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

cman-2.0.115-68.el5
rgmanager-2.0.52-9.el5


How reproducible:

Set up two node cluster, no qdisk. 

Configure service which needs ip address ( nfs/http ), edit cluster.conf per above. After changes services will be showed as running in clustat output but there will not be active ip address for them. Services will not be functional what is expected. 

In my testing I used nfs service, migrating it from one node to another was fine, mounting nfs share was also fine, but not error was reported that ip address has bad format for it. 

# ip a 

did not showed it. 


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:

There should be mechanism to prevent obvious errors in cluster.conf to be propagated to cluster. In case there is unexpected value for resource specified in cluster.conf that should be reported back, and not allow such error to be send to cluster nodes.



Additional info:
Comment 1 RHEL Program Management 2012-05-15 19:18:11 UTC 
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release.  Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products.  This request is not yet committed for inclusion in
a release.
Comment 2 Lon Hohberger 2012-05-16 13:12:55 UTC 
Added this service:

                <service name="iptest">
                        <ip address="192.168.122.240/24" monitor_link="1"/>
                </service>

...

May 16 09:10:24 rhel5-1 clurgmgrd[3643]: <notice> Initializing service:iptest
May 16 09:10:25 rhel5-1 clurgmgrd[3643]: <notice> Starting stopped service service:iptest
May 16 09:10:25 rhel5-1 clurgmgrd: [3643]: <info> Adding IPv4 address 192.168.122.240/24 to eth0
May 16 09:10:28 rhel5-1 clurgmgrd[3643]: <notice> Service service:iptest started 

...


2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 52:54:00:6f:8f:15 brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.90/24 brd 192.168.122.255 scope global eth0
    inet 192.168.122.251/24 brd 192.168.122.255 scope global secondary eth0:1
*** inet 192.168.122.240/24 scope global secondary eth0