Created attachment 1765885 [details] dc-detail-page Description of problem: The "Status" field is always "Updating" on dc detail page after deployment has failed Version-Release number of selected component (if applicable): 4.8.0-0.nightly-2021-03-22-104536 How reproducible: Always Steps to Reproduce: 1.Create a dc which will fail to deployment. Example yaml: apiVersion: apps.openshift.io/v1 kind: DeploymentConfig metadata: name: faildc spec: strategy: type: Rolling rollingParams: updatePeriodSeconds: 1 intervalSeconds: 1 timeoutSeconds: 20 maxUnavailable: 25% maxSurge: 25% resources: {} activeDeadlineSeconds: 30 triggers: - type: ConfigChange selector: app: hello-openshiftfail replicas: 1 template: metadata: labels: app: hello-openshiftfail spec: containers: - name: hello-openshift image: openshift/hello-openshiftdc ports: - containerPort: 8080 2.Wait after the deployment failed, the rc satus was "Failed" 3.Check on the dc detail page. Actual results: 3.The "Status" field was always "Updating" for hours. Expected results: 3.Use would feel confused about what is updating all the time. It's better to show correct status, eg "Up to date", "Failed". Additional info: I notice the status when I check https://issues.redhat.com/browse/ODC-5594, in which I need deal with dc in "Active" and "Not active" status, but I can not guess the exact meaning of "Updating" status on dc detail page.
Created attachment 1765886 [details] rc-status
The fix are not contained in payload 4.8.0-0.nightly-2021-03-26-054333, wait for new payload containing the fix.
Checked on ocp 4.8 cluster with payload 4.8.0-0.nightly-2021-03-30-160509. Create dc with wrong image, the deployment will fail, check "Status" on dc detail page, it shows "Failed". The bug is fixed.
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 (Moderate: OpenShift Container Platform 4.8.2 bug fix and security 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/RHSA-2021:2438