Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1635720

Summary: Cannot add a storage domain with blank comment
Product: [oVirt] ovirt-engine Reporter: Pavel Novotny <pnovotny>
Component: Frontend.WebAdminAssignee: bugs <bugs>
Status: CLOSED DUPLICATE QA Contact: Lukas Svaty <lsvaty>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.2.6.2CC: bugs, frolland, michal.skrivanek, ratamir
Target Milestone: ---Keywords: AutomationBlocker, Regression
Target Release: ---Flags: ratamir: blocker?
pnovotny: planning_ack?
pnovotny: devel_ack?
pnovotny: testing_ack+
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: 2018-10-07 07:14:15 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:
Attachments:
Description Flags
screen: adding storage without comment
none
engine.log none

Description Pavel Novotny 2018-10-03 14:34:04 UTC
Created attachment 1490119 [details]
screen: adding storage without comment

Description of problem:
Cannot add storage domain with blank Comment field.

Version-Release number of selected component (if applicable):
ovirt-engine-4.2.7.1-0.1.el7ev.noarch
ovirt-engine-webadmin-portal-4.2.7.1-0.1.el7ev.noarch

How reproducible:
always

Steps to Reproduce:
1. Add an NFS data storage, leave the Comment field blank.
2.
3.

Actual results:
~-~
Error while executing action: 
- may not be null
- Attribute: privateStorageDomain.comment
~-~
Screenshot attached.

Expected results:
No error, adding storage completes successfully.

Additional info:

The same error occurs when editing or importing a storage.

Comment 1 Pavel Novotny 2018-10-03 14:34:35 UTC
Created attachment 1490120 [details]
engine.log

Comment 2 Fred Rolland 2018-10-07 07:14:15 UTC

*** This bug has been marked as a duplicate of bug 1633232 ***