Bug 1807307 - 404: Page Not Found error on clicking the "1 requires Approval' under Subscription Overview->Upgrade Status page
Summary: 404: Page Not Found error on clicking the "1 requires Approval' under Subscri...
Keywords:
Status: CLOSED DUPLICATE of bug 1783651
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: bpeterse
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-26 04:27 UTC by Neha Berry
Modified: 2020-03-06 18:56 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-06 18:56:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
subscription page- 1 requires approval (142.53 KB, image/png)
2020-02-26 04:30 UTC, Neha Berry
no flags Details
Page Not Found (95.34 KB, image/png)
2020-02-26 04:31 UTC, Neha Berry
no flags Details

Description Neha Berry 2020-02-26 04:27:59 UTC
Description of problem (please be detailed as possible and provide log
snippests):
--------------------------------------------------------------
Installed OCP 4.3.3 and then Installed OCS 4.2.1 subscription with Upgrade Policy "Manual". Navigated to Installed Operators->OCS Operator->Subscription Page and clicked on "1 requires Approval" under Subscription Approval->Upgrade Status (to manually approve the Install Plan)

The resulting page gave 404:Not Found Error. Attached screenshots install-1.png and install-2.png

Link giving 404 Error : https://console-openshift-console.apps.neha-rhel.qe.rh-ocs.com/k8s/ns/openshift-storage/installplans/install-7hg9m

>>Workaround:

Clicked on the same install Plan (install-7hg9m) from the Subscription->Install Plan->install-7hg9m and the Install Plan for Approval opened successfully.

Link which opens successfully: https://console-openshift-console.apps.neha-rhel.qe.rh-ocs.com/k8s/ns/openshift-storage/operators.coreos.com~v1alpha1~InstallPlan/install-7hg9m

Version of all relevant components (if applicable):
--------------------------------------------------
OCP 4.3.3

OCS = 4.2.1 (LIVE)

OS =RHEL 7.7

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
------------------------------------
With Install plan approval option present in Subscription Overview->"Install Plan" , the install succeeded. But if one clicks on "1 required Approval", the user is not getting navigated to the Install Plan page.


Is there any workaround available to the best of your knowledge?
-----------------------------------------
Yes. Mentioned above.

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?
------------------------------
tested once

Can this issue reproduce from the UI?
---------------------------
Yes

If this is a regression, please provide more details to justify this:
--------------------------------------
In earlier builds, we have been able to navigate to Install Plan for Approval via the "1 required approval" hyperlink.

Steps to Reproduce:
----------------------
1. Install OCP 4.3.3
2. Install OCS subscription after selecting Upgrade STrategy" -> Manual
3. Goto OCS Operator->Subscription Page->Subscription Overview->Upgrade Status and click on "1 requires Approval" 
4. Check if we get 404 Error or we are taken to the Install Plan page for approval. 


Actual results:
-----------------
Clicking on "1 requires Approval"  in  "OCS Operator->Subscription Page->Subscription Overview->Upgrade Status" does not take you to the Install Plan page for approval

Expected results:
---------------------
It should take you to the Install Plan page for approval.

Additional info:
-----------------------
Logs are same as : http://rhsqe-repo.lab.eng.blr.redhat.com/cns/ocs-qe-bugs/bz-1807301.zip


$ oc get nodes -o wide
NAME                                        STATUS   ROLES    AGE   VERSION   INTERNAL-IP   EXTERNAL-IP   OS-IMAGE                                                       KERNEL-VERSION                CONTAINER-RUNTIME
ip-10-0-60-169.us-east-2.compute.internal   Ready    worker   11h   v1.16.2   10.0.60.169   <none>        Red Hat Enterprise Linux Server 7.7 (Maipo)                    3.10.0-1062.9.1.el7.x86_64    cri-o://1.16.3-20.dev.rhaos4.3.git11c04e3.el7
ip-10-0-62-108.us-east-2.compute.internal   Ready    master   11h   v1.16.2   10.0.62.108   <none>        Red Hat Enterprise Linux CoreOS 43.81.202002170853.0 (Ootpa)   4.18.0-147.5.1.el8_1.x86_64   cri-o://1.16.3-22.dev.rhaos4.3.git11c04e3.el8
ip-10-0-65-182.us-east-2.compute.internal   Ready    master   11h   v1.16.2   10.0.65.182   <none>        Red Hat Enterprise Linux CoreOS 43.81.202002170853.0 (Ootpa)   4.18.0-147.5.1.el8_1.x86_64   cri-o://1.16.3-22.dev.rhaos4.3.git11c04e3.el8
ip-10-0-72-56.us-east-2.compute.internal    Ready    worker   11h   v1.16.2   10.0.72.56    <none>        Red Hat Enterprise Linux Server 7.7 (Maipo)                    3.10.0-1062.9.1.el7.x86_64    cri-o://1.16.3-20.dev.rhaos4.3.git11c04e3.el7
ip-10-0-81-82.us-east-2.compute.internal    Ready    worker   11h   v1.16.2   10.0.81.82    <none>        Red Hat Enterprise Linux Server 7.7 (Maipo)                    3.10.0-1062.9.1.el7.x86_64    cri-o://1.16.3-20.dev.rhaos4.3.git11c04e3.el7
ip-10-0-90-189.us-east-2.compute.internal   Ready    master   11h   v1.16.2   10.0.90.189   <none>        Red Hat Enterprise Linux CoreOS 43.81.202002170853.0 (Ootpa)   4.18.0-147.5.1.el8_1.x86_64   cri-o://1.16.3-22.dev.rhaos4.3.git11c04e3.el8

Comment 2 Neha Berry 2020-02-26 04:30:42 UTC
Created attachment 1665809 [details]
subscription page- 1 requires approval

Comment 3 Neha Berry 2020-02-26 04:31:14 UTC
Created attachment 1665810 [details]
Page Not Found

Comment 9 Samuel Padgett 2020-03-06 18:56:25 UTC

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


Note You need to log in before you can comment on or make changes to this bug.