Bug 1378284 - [Docs][Identity] Creating Security Group rule failed with Protocol -1
Summary: [Docs][Identity] Creating Security Group rule failed with Protocol -1
Keywords:
Status: CLOSED EOL
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 9.0 (Mitaka)
Hardware: All
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Martin Lopes
QA Contact: RHOS Documentation Team
URL:
Whiteboard:
Depends On: 1376631
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-22 03:15 UTC by Deepti Navale
Modified: 2019-12-16 06:51 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1376631
Environment:
Last Closed: 2019-10-15 13:26:25 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Deepti Navale 2016-09-22 03:15:26 UTC 
+++ This bug was initially created as a clone of Bug #1376631 +++

Description of problem:
Creating security group rule failed in OSP 9 from dashboard/horizon when selected other protocol with protocol value -1. It is created successfully in OSP 8.

But creating with protocol -1 always fails from CLI in both OSP 8 and OSP 9.

The horizon field help says input -1 as wildcard entry

Version-Release number of selected component (if applicable):
Red Hat OpenStack Platform 9

How reproducible:
Always

Steps to Reproduce:
1. create a security group rule with other protocol and input protocol value as -1

Actual results:
An error message is thrown as "Not a valid IP protocol number"

Expected results:
The protocol field should not say input -1 for wildcard entry instead it should say leave it blank for wildcard entry

Additional info:

--- Additional comment from PURANDHAR SAIRAM MANNIDI on 2016-09-15 21:04 EDT ---



--- Additional comment from Martin Lopes on 2016-09-21 22:58:04 EDT ---

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