Bug 1985876 - Cannot set 0.0.0.0 as gateway
Summary: Cannot set 0.0.0.0 as gateway
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: vdsm
Classification: oVirt
Component: Core
Version: 4.40.80
Hardware: Unspecified
OS: Unspecified
medium
medium vote
Target Milestone: ovirt-4.4.8
: ---
Assignee: Ales Musil
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On: 1985879
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-26 06:59 UTC by Ales Musil
Modified: 2021-08-19 06:22 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-08-19 06:22:58 UTC
oVirt Team: Network
mperina: ovirt-4.4+
pm-rhel: blocker?


Attachments (Terms of Use)

Description Ales Musil 2021-07-26 06:59:48 UTC
Description of problem:
Cannot set 0.0.0.0 as network gateway.

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

How reproducible:
100%

Steps to Reproduce:
1. Try to set gateway 0.0.0.0 for network


Actual results:
It fails with nmstate verification error

Expected results:
It should pass

Comment 3 Michael Burman 2021-08-02 11:36:18 UTC
 nmstate                                     noarch                   1.0.2-14.el8_4                                    rhel-8.4-nightly-appstream                    42 k


nmstate with the fix available for us in 4.4.8-3 
BZ 1986285 has been verified.

Comment 5 Michael Burman 2021-08-03 06:45:40 UTC
Verified on - rhvm-4.4.8.2-0.11.el8ev.noarch with:

nmstate-1.0.2-14.el8_4.noarch
NetworkManager-1.30.0-10.el8_4.x86_64
vdsm-4.40.80.3-1.el8ev.x86_64

Comment 6 RHEL Program Management 2021-08-09 03:51:59 UTC
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.

Comment 7 Sandro Bonazzola 2021-08-19 06:22:58 UTC
This bugzilla is included in oVirt 4.4.8 release, published on August 19th 2021.

Since the problem described in this bug report should be resolved in oVirt 4.4.8 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.


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