Bug 1305641

Summary: Duplicate hostnames allowed when exposing a service
Product: OpenShift Container Platform Reporter: Alfredo Quiroga <aquiroga>
Component: NetworkingAssignee: Eric Paris <eparis>
Networking sub component: router QA Contact: zhaozhanqi <zzhao>
Status: CLOSED DUPLICATE Docs Contact:
Severity: low    
Priority: unspecified CC: aos-bugs
Version: 3.1.0   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-15 18:04:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Alfredo Quiroga 2016-02-08 19:32:31 UTC 
Description of problem:

When exposing a service, we should only be able to associate it with a hostname if it's not already bound to another service. In other words, if we ran:

oc expose service hello --hostname=hello.example.com

running it for a second time for a different service or perhaps even the same service should result in a failure since the hostname "hello.example.com" is already bound to a service.

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

3.1.1

How reproducible:


Steps to Reproduce:
1. oc expose service hello --hostname=hello.example.com
2. oc expose service world --hostname=hello.example.com

Actual results:

Both records are inserted.

Expected results:

An error message saying that the hostname is already associated with an existing service.


Additional info:
Comment 1 Eric Paris 2016-02-15 18:04:12 UTC 

*** This bug has been marked as a duplicate of bug 1243664 ***