Erratic IPv4 validation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
In Progress
|
Low
|
Luis Eduardo Angelini Marquitti |
Bug Description
Brief Description
-----------------
Using service-parameter and setting an IPv4 address could lead into some issues.
Since IPv4, IPv6 and hostnames are accepted, there is a logic that detects which type is used. Then it validates the value. However, some invalid ranges from IPv4 will be rejected but some others will fall into domain check and pass.
Some examples to make it clearer:
IPv4 accepted: 192.168.0.1:12345
IPv4 rejected: 292.168.0.1:12345
IPv4 accepted by domain validator: 192.168.
This issue can be seen on utils.py from sysinv/
Severity
--------
Minor
Steps to Reproduce
------------------
From active controller run:
source /etc/platform/
system service-parameter add platform collectd network_
Where Host can be an IPv4, IPv6 or hostname and port any uint16 value.
Expected Behavior
------------------
Invalid ranges for IPv4 must be rejected
Actual Behavior
----------------
Reproducibility
---------------
100% reproducible
System Configuration
-------
AIO-SX, AIO-DX
Branch/Pull Time/Commit
-------
Last Pass
---------
Timestamp/Logs
--------------
Test Activity
-------------
Workaround
----------
tags: | added: stx.config |
Changed in starlingx: | |
importance: | Undecided → Low |
Changed in starlingx: | |
assignee: | nobody → Luis Eduardo Angelini Marquitti (leduard1) |
Fix proposed to branch: master /review. opendev. org/c/starlingx /config/ +/819475
Review: https:/