Bug 2055141 - Upgrade to ODF 4.9.3 from OCS 4.8.8 did not start
Summary: Upgrade to ODF 4.9.3 from OCS 4.8.8 did not start
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: odf-operator
Version: 4.9
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: ODF 4.10.0
Assignee: Nitin Goyal
QA Contact: Petr Balogh
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-16 10:56 UTC by Petr Balogh
Modified: 2023-08-09 17:00 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-21 09:12:46 UTC
Embargoed:


Attachments (Terms of Use)

Description Petr Balogh 2022-02-16 10:56:34 UTC
Description of problem (please be detailed as possible and provide log
snippests):

In the subscription we see:
 - message: 'constraints not satisfiable: subscription ocs-operator exists, no operators
      found in channel stable-4.8 of package ocs-operator in the catalog referenced
      by subscription ocs-operator'
    reason: ConstraintsNotSatisfiable
    status: "True"
    type: ResolutionFailed

http://magna002.ceph.redhat.com/ocsci-jenkins/openshift-clusters/j-155vu1cs33-ua/j-155vu1cs33-ua_20220215T122619/logs/failed_testcase_ocs_logs_1644930356/test_upgrade_ocs_logs/ocp_must_gather/quay-io-openshift-origin-must-gather-sha256-ea30a2fe24e53e97d8e15de93ef15504e54250806622eb43d8d91dfeeb03db80/namespaces/openshift-storage/operators.coreos.com/subscriptions/odf-operator.yaml


Version of all relevant components (if applicable):
OCS 4.8.8 GA upgrade to ODF 4.9.3-2 internal build
OCP: 4.9.0-0.nightly-2022-02-15-030050

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

Upgrade didn't start

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)?


Can this issue reproducible?
Trying now


Can this issue reproduce from the UI?


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


Steps to Reproduce:
1. Install OCS 4.8.8
2. Upgrade to internal build of 4.9.3
3.


Actual results:
Upgrade didn't start

Expected results:
Have upgrade started and finished

Additional info:

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

Must gather logs:
http://magna002.ceph.redhat.com/ocsci-jenkins/openshift-clusters/j-155vu1cs33-ua/j-155vu1cs33-ua_20220215T122619/logs/failed_testcase_ocs_logs_1644930356/test_upgrade_ocs_logs/

Comment 9 Nitin Goyal 2022-02-17 10:53:09 UTC
Moving it to ONQA as the build is fixed 

$ grpcurl -plaintext -d '{"name":"ocs-operator"}' localhost:50051 api.Registry/GetPackage
{
  "name": "ocs-operator",
  "channels": [
    {
      "name": "eus-4.8",
      "csvName": "ocs-operator.v4.8.8"
    },
    {
      "name": "stable-4.8",
      "csvName": "ocs-operator.v4.8.8"
    },
    {
      "name": "stable-4.9",
      "csvName": "ocs-operator.v4.9.3"
    }
  ],
  "defaultChannelName": "stable-4.9"
}


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