Bug 1532308

Summary:	Cannot add Openstack glance and block storage provider in the UI
Product:	[oVirt] ovirt-engine	Reporter:	Fred Rolland <frolland>
Component:	BLL.Storage	Assignee:	Fred Rolland <frolland>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Avihai <aefrat>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.2.0	CC:	aefrat, amureini, bugs, lveyde
Target Milestone:	ovirt-4.2.1	Keywords:	Regression
Target Release:	---	Flags:	rule-engine: ovirt-4.2+ rule-engine: blocker+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.2.1.1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-02-12 11:56:24 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Fred Rolland 2018-01-08 16:00:08 UTC

Description of problem:
Cannot add Openstack glance and block storage provider in the UI.
Also editing existing such providers fails.
The "tenant" field is missing.

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


How reproducible:
100%

Steps to Reproduce:
1. Add a new Openstack glance or block storage provider in the UI


Actual results:
Fails to add/edit

Expected results:
Should work

Additional info:
Regression introduce by:
https://gerrit.ovirt.org/#/c/84546/

Comment 1 Red Hat Bugzilla Rules Engine 2018-01-08 16:13:33 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 2 Allon Mureinik 2018-01-11 12:07:31 UTC

*** Bug 1532326 has been marked as a duplicate of this bug. ***

Comment 3 Avihai 2018-01-16 15:14:45 UTC

verified on 4.2.1.1-0.1.el7

Comment 4 Sandro Bonazzola 2018-02-12 11:56:24 UTC

This bugzilla is included in oVirt 4.2.1 release, published on Feb 12th 2018.

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