Bug 1403318 - Better error message on host name collision
Summary: Better error message on host name collision
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: DHCP & DNS
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
medium
medium vote
Target Milestone: Unspecified
Assignee: Lukas Zapletal
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1402685
TreeView+ depends on / blocked
 
Reported: 2016-12-09 15:59 UTC by Renzo Nuccitelli
Modified: 2019-08-12 16:06 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-08-02 21:00:33 UTC
Target Upstream Version:


Attachments (Terms of Use)
dup msg (139.26 KB, image/jpeg)
2016-12-09 16:00 UTC, Renzo Nuccitelli
no flags Details
fixed address (176.49 KB, image/jpeg)
2016-12-09 16:01 UTC, Renzo Nuccitelli
no flags Details

Description Renzo Nuccitelli 2016-12-09 15:59:30 UTC
Description of problem:

Error message should point out host name collision

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

Foreman 1.14.0 develp

How reproducible:

always

Steps to Reproduce:
1. Setup infoblox-satellite integration;
2. Create a fixed address on infoblox with name bar.<your-satellite-domain> (see attached file);
3. Create a host on satelite with same name (bar).

Actual results:

 Error msg attached

Expected results:

 Better error msg explaining the collision

Additional info:

Comment 1 Renzo Nuccitelli 2016-12-09 16:00:29 UTC
Created attachment 1230032 [details]
dup msg

Comment 2 Renzo Nuccitelli 2016-12-09 16:01:14 UTC
Created attachment 1230033 [details]
fixed address

Comment 6 Bryan Kearney 2018-08-02 21:00:33 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.


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