Bug 1305641 - Duplicate hostnames allowed when exposing a service
Summary: Duplicate hostnames allowed when exposing a service
Keywords:
Status: CLOSED DUPLICATE of bug 1243664
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 3.1.0
Hardware: All
OS: Linux
unspecified
low
Target Milestone: ---
: ---
Assignee: Eric Paris
QA Contact: zhaozhanqi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-08 19:32 UTC by Alfredo Quiroga
Modified: 2022-08-04 22:20 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-15 18:04:12 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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 ***


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