This bug was initially created as a copy of Bug #2070542 I am copying this bug because: Created attachment 1869691 [details] While creating Storage System in AWS OCP 4.11, ODF 4.10 it leads to 404 error page Description of problem (please be detailed as possible and provide log snippests): While creating storagesystem from UI after the final step 404 page not found error page is displayed. But the storagesystem actually got created. Version of all relevant components (if applicable): ocp version: 4.11.0-0.nightly-2022-03-27-140854 odf version=4.10.0-198 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? No, it still works. But it is not the expected behavior. Is there any workaround available to the best of your knowledge? No Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)?2 Can this issue reproducible? Yes Can this issue reproduce from the UI? Yes If this is a regression, please provide more details to justify this: Yes, in the previous versions we have faced similar issue, Bug 2032984 which got fixed. Steps to Reproduce: 1. Deploy an AWS, OCP 4.11 cluster, without ODF. 2. Install ODF 4.10 through the UI. 3. Create a new StorageSystem. Actual results: After creating and installing the StorageSystem it redirects to a 404 page. Expected results: After creating and installing the StorageSystem it should redirect to the "StorageSystems" page. Additional info:
Moving the bug to 4.10.4 so verification on 4.11 is complete before backporting into the 4.10 z stream
Moving the BZs to next batch update to accommodate CVE fix.
This bug has been hanging for quite a while, its moved from 4.10.2 --> 4.10.3 --> 4.10.4, now are we proposing it for 4.10.5 ?? If it is alright, I would suggest to take it up in 4.10.4 itself. PR is already up and reviewed and we only have to merge it. Also, it is very important to have this fix before OCP 4.11 is GAed (I know that is somewhere around August, still if possible we should take this PR for 4.10.4 only, so that we have some buffer in case some unexpected situation arises at last moment when we are about to GA OCP 4.11).
Continuation to https://bugzilla.redhat.com/show_bug.cgi?id=2074518#c17, because of an urgent CVE we have do 4.10.4 without any bug fix. So, this BZ needs to go in 4.10.5 (which is mostly in second week of July).
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (ODF 4.10.5 bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:5607