Bug 2233468

Summary: NmstateError for invalid prefix-length seems not accurate
Product: Red Hat Enterprise Linux 9 Reporter: qiowang
Component: nmstateAssignee: NetworkManager Development Team <nm-team>
Status: CLOSED MIGRATED QA Contact: Mingyu Shi <mshi>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 9.2CC: ferferna, jiji, jishi, network-qe, till
Target Milestone: rcKeywords: MigratedToJIRA
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-08-24 18:06:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description qiowang 2023-08-22 10:01:33 UTC
Description of problem:
nmstate error message for invalid prefix-length seems not accurate


Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux release 9.2
nmstate-2.2.13-1.el9_2.x86_64


How reproducible:
always


Steps to Reproduce:
1. apply nmstate policy with invalid ipv4 prefix-length 33
  desiredState:
    interfaces:
    - ipv4:
        address:
        - ip: 5.5.5.6
          prefix-length: 33
        enabled: true
      name: br123
      state: up
      type: linux-bridge


Actual results:
apply failed with below error:
NmstateError: InvalidArgument: Connection(MissingProperty):ipv4.addresses: this property cannot be empty for 'method=manual' 


Expected results:
apply failed with accurate error message about invalid prefix-length


Additional info:

Comment 1 Till Maas 2023-08-24 18:00:07 UTC
This bug has been scheduled for migration to Jira (https://issues.redhat.com).
Please, let me know if you face any problems once it is done (Jira login creation, etc.). 
For guidance about your Jira account or creating one if needed, use the following KB articles: KB0016394, KB0016694, KB0016774.

Comment 2 RHEL Program Management 2023-08-24 18:00:14 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 3 RHEL Program Management 2023-08-24 18:06:07 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues.