Bug 1577038

Summary:	Cockpit don't validate the engine vm ip prefix
Product:	[oVirt] cockpit-ovirt	Reporter:	Yihui Zhao <yzhao>
Component:	Hosted Engine	Assignee:	Phillip Bailey <phbailey>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Yihui Zhao <yzhao>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	---	CC:	bugs, cshao, huzhao, jiaczhan, phbailey, qiyuan, rbarry, sbonazzo, stirabos, weiwang, yaniwang, ycui, yturgema
Target Milestone:	ovirt-4.2.4	Flags:	rule-engine: ovirt-4.2+ yzhao: testing_ack+
Target Release:	0.11.25
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	cockpit-ovirt-0.11.25-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-06-26 08:40:17 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Integration	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1582207

Description Yihui Zhao 2018-05-11 03:47:18 UTC

Description of problem:
Cockpit don't validate the engine vm ip prefix.

Version-Release number of selected component (if applicable):
rhvh-4.2.3.0-0.20180508.0+1
ovirt-hosted-engine-setup-2.2.20-1.el7ev.noarch
cockpit-ovirt-dashboard-0.11.24-1.el7ev.noarch
ovirt-hosted-engine-ha-2.2.11-1.el7ev.noarch
rhvm-appliance-4.2-20180504.0.el7.noarch

How reproducible:
100%


Steps to Reproduce:
1. Deploy HE with static ip via cockpit
2. Input the VM ip prefix field, like input '33'

Actual results:
After step2, cockpit don't validate this field.
Expected results:
Cockpit should validate the engine vm ip prefix field.

Additional info:

Comment 1 Yihui Zhao 2018-05-30 01:39:04 UTC

Tested with cockpit-ovirt-0.11.25-1:
Now the engine vm ip prefix validate the input field (0-32)

If not range 0~32, will give the hint "Value must be between 0 and 32"

So, change the bug's status to verified.

Comment 2 Sandro Bonazzola 2018-06-26 08:40:17 UTC

This bugzilla is included in oVirt 4.2.4 release, published on June 26th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.4 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.