Bug 2080975

Summary: Inability to create an rgw bucket when an optional argument has null value
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: aberner
Component: cephAssignee: Matt Benjamin (redhat) <mbenjamin>
Status: CLOSED CURRENTRELEASE QA Contact: Neha Berry <nberry>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.6CC: bniver, jthottan, madam, muagarwa, ocs-bugs, odf-bz-bot
Target Milestone: ---Flags: jthottan: needinfo? (aberner)
Target Release: ---   
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: 2022-06-13 09:24:20 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description aberner 2022-05-02 13:34:28 UTC
Description of problem (please be detailed as possible and provide log
snippests):
While trying to provision an rgw bucket as part of the acceptance suite for the RGW component the yaml we tried to apply got rejected with the error message of:
"spec.additionalConfig: Invalid value: "null": spec.additionalConfig in body must be of type object: "null"" 
but this is an optional argument and such yaml has already been approved by the system (in the same version and above as well)

Version of all relevant components (if applicable):
4.6.12-206.ci

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?


Is there any workaround available to the best of your knowledge?


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
1

Can this issue reproducible?
yes, occurred on 2 runs 

Can this issue reproduce from the UI?
unknown

If this is a regression, please provide more details to justify this:
yes

Steps to Reproduce:
1. please see automation failures in runs below 
2.
3.


Actual results:
yaml gets rejected

Expected results:
yaml accepted and bucket created

Additional info:
automation runs:
https://ocs4-jenkins-csb-odf-qe.apps.ocp-c1.prod.psi.redhat.com/job/qe-deploy-ocs-cluster-prod/4045/

https://ocs4-jenkins-csb-odf-qe.apps.ocp-c1.prod.psi.redhat.com/job/qe-deploy-ocs-cluster-prod/4054/

Comment 5 Mudit Agarwal 2022-06-13 09:24:20 UTC
Please reopen if this is still reproducible.