Bug 1928515 - [Assisted-4.7] [Staging] [Advanced networking] Unclear error message when saving wrong service CIDR
Summary: [Assisted-4.7] [Staging] [Advanced networking] Unclear error message when sav...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: assisted-installer
Version: 4.7
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Ori Amizur
QA Contact: Yuri Obshansky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-14 15:21 UTC by Lital Alon
Modified: 2022-08-28 08:45 UTC (History)
3 users (show)

Fixed In Version: OCP-Metal-v1.0.18.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-28 08:45:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
example (260.23 KB, image/png)
2021-02-14 15:21 UTC, Lital Alon
no flags Details

Description Lital Alon 2021-02-14 15:21:10 UTC
Created attachment 1756952 [details]
example

Description of problem:
When tried to save Cluster Network CIDR: 10.128.0.0/1 i get:
"address must not be unspecified. Unspecified address is the address with all zeroes"

The issue is that the message is very unclear, and doesn't indicate the user about the real problem.

See attached example


Version-Release number of selected component (if applicable):
Staging, v1.0.16.1

Steps to Reproduce:
1. try to save Cluster Network CIDR: 10.128.0.0/1

Actual results:
"address must not be unspecified. Unspecified address is the address with all zeroes"

Expected results:
a suggestion: Provided cluster network CIDR is illegal

Comment 1 Lital Alon 2021-02-15 15:24:23 UTC
Note that the current message is missing an indication regarding the wrong value source (Cluster CIDR \ Service CIDR)

Comment 2 Lital Alon 2021-02-18 15:30:11 UTC
new suggested working: "The specified CIDR is invalid because its resulting routing prefix matches the unspecified address."

Comment 4 Lital Alon 2021-03-31 14:13:22 UTC
Verified in Staging V1.0.18.1


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