Bug 614457 - Resource agent for psql does not work correctly with netmask
Resource agent for psql does not work correctly with netmask
Status: CLOSED CURRENTRELEASE
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: resource-agents (Show other bugs)
6.0
All Linux
low Severity medium
: rc
: ---
Assigned To: Marek Grac
Cluster QE
:
Depends On: 614456
Blocks:
  Show dependency treegraph
 
Reported: 2010-07-14 10:25 EDT by Marek Grac
Modified: 2010-11-15 09:44 EST (History)
4 users (show)

See Also:
Fixed In Version: resource-agents-3.0.12-15.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 614456
Environment:
Last Closed: 2010-11-15 09:44:06 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Marek Grac 2010-07-14 10:25:49 EDT
+++ This bug was initially created as a clone of Bug #614456 +++

Reported and proposed patch by: Hirotaka Igarashi

In a case defining postgres-8 resource under ip resource and this ip-address has net-mask, postgres-8.sh does not generate appropriate configuration file.

Example configuration:
<ip address="10.3.1.10/24 monitor_link="1"">
      <postgres-8 name="db_svr"/>
</ip>

From this kind of cluster.conf, postgres-8.sh generates postgresql.conf as follows,
----------------------
listen_addresses = '10.3.1.10/24'
----------------------
 
it causes postmaster's unsuccessful startup.

Patch:
 ---- Modified From Here-----
        for i in $ip_addressess; do
                # modified by hiro@csrl.jp so that it supports netmask
                i=`echo $i|sed -e 's/\/.*$//'`
                if [ $x -eq 1 ]; then
                        x=0
                        ip_comma=$i
                else
                        ip_comma=$ip_comma,$i
                fi 
        done
---- Modified Till Here-----
Comment 5 releng-rhel@redhat.com 2010-11-15 09:44:06 EST
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.

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