Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

./migrate_tenant.sh hang at the ibm-common-service-operator to be upgraded, #1205

Open
humantask opened this issue May 4, 2023 · 0 comments

Comments

@humantask
Copy link

[[email protected] cp3pt0-deployment]# ./migrate_tenant.sh --operator-namespace auto-ucvvr --services-namespace auto-ucvvr --cert-manager-source ibm-cert-manager-catalog --enable-licensing false -v 1
wildcard
[:heavy_check_mark:] oc command available
[:heavy_check_mark:] yq command available
[:heavy_check_mark:] oc command logged in as kube:admin
[INFO] v3.23 is less than v4.0
[INFO] catalogsource opencloud-operators is the same as opencloud-operators
[INFO] is ready for scaling down.
deployment.apps/ibm-common-service-operator scaled
Deleting operand-deployment-lifecycle-manager-app in namesapce auto-ucvvr...
[1] Removing the subscription of operand-deployment-lifecycle-manager-app in namesapce auto-ucvvr ...
subscription.operators.coreos.com "operand-deployment-lifecycle-manager-app" deleted
[2] Removing the csv of operand-deployment-lifecycle-manager-app in namesapce auto-ucvvr ...
clusterserviceversion.operators.coreos.com "operand-deployment-lifecycle-manager.v1.21.2" deleted
[:heavy_check_mark:] Remove operand-deployment-lifecycle-manager-app successfully.
operandregistry.operator.ibm.com "common-service" deleted
operandconfig.operator.ibm.com "common-service" deleted
[:heavy_check_mark:] oc command available
[:heavy_check_mark:] oc command logged in as kube:admin
De-activating IBM Cloud Pak 2.0 Cert Manager in auto-cs-control...
[INFO] Configuring Common Services Cert Manager..
configmap/ibm-cpp-config created
[INFO] Deleting existing Cert Manager CR...
certmanager.operator.ibm.com "default" deleted
[INFO] Restarting IBM Cloud Pak 2.0 Cert Manager to provide cert-rotation only...
pod "ibm-cert-manager-operator-84fb46ff9d-gjxhs" deleted
[INFO] Waiting for pod cert-manager-cainjector in namespace auto-cs-control to be deleting
[:heavy_check_mark:] Pod cert-manager-cainjector in namespace auto-cs-control is deleted
[INFO] Waiting for pod cert-manager-controller in namespace auto-cs-control to be deleting
[:heavy_check_mark:] Pod cert-manager-controller in namespace auto-cs-control is deleted
[INFO] Waiting for pod cert-manager-webhook in namespace auto-cs-control to be deleting
[:heavy_check_mark:] Pod cert-manager-webhook in namespace auto-cs-control is deleted
[INFO] Waiting for pod ibm-cert-manager-operator in namespace auto-cs-control to be running
[:heavy_check_mark:] Pod ibm-cert-manager-operator in namespace auto-cs-control is running
[:heavy_check_mark:] oc command available
[:heavy_check_mark:] oc command logged in as kube:admin
Installing cert-manager
[✗] There is a cert-manager Subscription already
[INFO] Namespace ibm-cert-manager already exists. Skip creating
[INFO] Checking existing OperatorGroup in ibm-cert-manager:
[INFO] OperatorGroup already exists in ibm-cert-manager. Skip creating
[INFO] Creating following Subscription:
apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
name: ibm-cert-manager-operator
namespace: ibm-cert-manager
spec:
channel: v4.0
installPlanApproval: Automatic
name: ibm-cert-manager-operator
source: ibm-cert-manager-catalog
sourceNamespace: openshift-marketplace
subscription.operators.coreos.com/ibm-cert-manager-operator configured
[INFO] Waiting for operator ibm-cert-manager-operator in namespace ibm-cert-manager to be made available
[:heavy_check_mark:] Operator ibm-cert-manager-operator in namespace ibm-cert-manager is available
[:heavy_check_mark:] Migration is completed for Cloud Pak 3.0 Foundational singleton services.
[INFO] Configuring CommonService CR common-service in auto-ucvvr
Warning: resource commonservices/common-service is missing the kubectl.kubernetes.io/last-applied-configuration annotation which is required by oc apply. oc apply should only be used on resources created declaratively by either oc create --save-config or oc apply. The missing annotation will be patched automatically.
commonservice.operator.ibm.com/common-service configured
[INFO] v3.23 is less than v4.0
[INFO] catalogsource opencloud-operators is the same as opencloud-operators
[INFO] ibm-common-service-operator is ready for updaing the subscription.
Warning: resource subscriptions/ibm-common-service-operator-v3.23-opencloud-operators-openshift-marketplace is missing the kubectl.kubernetes.io/last-applied-configuration annotation which is required by oc apply. oc apply should only be used on resources created declaratively by either oc create --save-config or oc apply. The missing annotation will be patched automatically.
subscription.operators.coreos.com/ibm-common-service-operator-v3.23-opencloud-operators-openshift-marketplace configured
[INFO] Waiting for operator ibm-common-service-operator to be upgraded
[INFO] RETRYING: Waiting for operator ibm-common-service-operator to be upgraded (10 left)
[INFO] RETRYING: Waiting for operator ibm-common-service-operator to be upgraded (9 left)
[INFO] RETRYING: Waiting for operator ibm-common-service-operator to be upgraded (8 left)
[INFO] RETRYING: Waiting for operator ibm-common-service-operator to be upgraded (7 left)
[INFO] RETRYING: Waiting for operator ibm-common-service-operator to be upgraded (6 left)
[INFO] RETRYING: Waiting for operator ibm-common-service-operator to be upgraded (5 left)
[INFO] RETRYING: Waiting for operator ibm-common-service-operator to be upgraded (4 left)
[INFO] RETRYING: Waiting for operator ibm-common-service-operator to be upgraded (3 left)
[INFO] RETRYING: Waiting for operator ibm-common-service-operator to be upgraded (2 left)
[INFO] RETRYING: Waiting for operator ibm-common-service-operator to be upgraded (1 left)
[✘] Timeout after 5 minutes waiting for operator ibm-common-service-operator to be upgraded

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant