Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 592307

Summary: setup-ds.pl fails to detect unavailable port on Solaris
Product: [Retired] 389 Reporter: Endi Sukma Dewata <edewata>
Component: Install/UninstallAssignee: Nathan Kinder <nkinder>
Status: CLOSED WONTFIX QA Contact: Chandrasekar Kannan <ckannan>
Severity: medium Docs Contact:
Priority: low    
Version: 1.2.6CC: benl, jgalipea
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Other   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-20 17:06:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
0001-Bug-592307-setup-ds.pl-fails-to-detect-unavailable-p.patch none

Description Endi Sukma Dewata 2010-05-14 14:10:47 UTC 
The setup-ds.pl is supposed to check and display an error message if the port number entered is unavailable. On Solaris the setup-ds.pl accepts the port number although it is being used by another server.

How reproducible: consistently.

Steps to Reproduce:
1. Create and run a DS instance with a certain port number.
2. Create another DS instance with the same port number.
  
Actual results:
In step #2 the port number is accepted, but the new DS instance will fail to start.

Expected results:
The conflicting port number should not be accepted and user should be asked to enter a new port number.
Comment 1 Endi Sukma Dewata 2010-05-14 14:19:59 UTC 
Created attachment 414067 [details]
0001-Bug-592307-setup-ds.pl-fails-to-detect-unavailable-p.patch

The portAvailable() has been modified to use connect() instead of bind().