Description of problem: ====================== While adding the gluster storage domain in RHV-M , it throws error. This was seen after creating additional gluster volumes and creating storage domains for those volumes. Version-Release number of selected component (if applicable): =========================================================== rhv-release-4.2.7-4-001 How reproducible: ================ 2/2 Steps to Reproduce: ================== 1.Create additional gluster volumes via cockpit Day 2 2.While adding the new gluster storage domain it is unsuccessful. Actual results: ============== The storage domains cannot be added Expected results: ================ The storage domains should be successfully added Additional info: ===============
Please reassign the component if not accurate. Snippet from the log: ==================== 2018-10-09 17:43:00,360+05 WARN [org.ovirt.engine.core.bll.storage.domain.AddGlusterFsStorageDomainCommand] (default task-53) [b5ddffb2-d42b-434e-a722-2eb80ae91877] Validation of action 'AddGlusterFsStorageDomain' failed for user admin@internal-authz. Reasons: VAR__TYPE__STORAGE__DOMAIN,VAR__ACTION__ADD,may not be null,$message {javax.validation.constraints.NotNull.message},$payload [Ljava.lang.Class;@199300f9,$groups [Ljava.lang.Class;@3e83543c,ACTION_TYPE_FAILED_ATTRIBUTE_PATH,$path privateStorageDomain.comment,$validatedValue null
Created attachment 1492115 [details] Engine.log
Created attachment 1492131 [details] UI_Screenshot
PS: Creating gluster volumes via RHV-M and then adding the gluster storage domain also gives the same error as mentioned above.
Bipin, I think it's expecting Comment from UI. If you will provide Comment then it should work. I am not sure why it's mandatory even though it's not marked as mandatory from UI.
Gobinda, That worked. But while adding the storage domains during deployment i didn't see similar error. Was there any change?
Bipin, I could be UI issue, need to check. Auto creation SD does not use UI, it uses backend api.
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.
*** This bug has been marked as a duplicate of bug 1633232 ***