Bug 1911656 - using 'operator-sdk run bundle' to install operator successfully, but the command output said 'Failed to run bundle''
Summary: using 'operator-sdk run bundle' to install operator successfully, but the com...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Operator SDK
Version: 4.7
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: 4.7.0
Assignee: Jesus M. Rodriguez
QA Contact: Cuiping HUO
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-12-30 14:37 UTC by Cuiping HUO
Modified: 2021-02-24 15:49 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-24 15:49:31 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:5633 0 None None None 2021-02-24 15:49:54 UTC

Description Cuiping HUO 2020-12-30 14:37:07 UTC
Description of problem:
using 'operator-sdk run bundle' to install operator successfully, but the command output said 'Failed to run bundle'

Version-Release number of selected component (if applicable):
operator-sdk version: "v1.2.0-54-g50fcdb8d", commit: "50fcdb8dd189ffe00d34a077adfcbee7309d5fec", kubernetes version: "v1.19.4", go version: "go1.14.2", GOOS: "linux", GOARCH: "amd64"

How reproducible:
Always

Steps to Reproduce:
1.using "operator-sdk run bundle quay.io/olmqe/etcd-bundle:0.9.2-share" to install an etcd operator 

Actual results:
etcd operator installed successfully, but the command output shows 
FATA[0128] Failed to run bundle: error waiting for CSV to install

Expected results:
etcd operator installed succesfully with command output shows installation success

Additional info:
$ operator-sdk run bundle quay.io/olmqe/etcd-bundle:0.9.2-share
INFO[0039] Successfully created registry pod: quay-io-olmqe-etcd-bundle-0-9-2-share 
INFO[0041] Created CatalogSource: etcd-catalog          
INFO[0041] OperatorGroup "operator-sdk-og" created      
INFO[0042] Created Subscription: etcdoperator-v0-9-2-sub 
INFO[0121] Approved InstallPlan install-gzcg5 for the Subscription: etcdoperator-v0-9-2-sub 
INFO[0128] Waiting for ClusterServiceVersion "default/etcdoperator.v0.9.2" to reach 'Succeeded' phase 
FATA[0128] Failed to run bundle: error waiting for CSV to install:  

$ oc get po
NAME                                                              READY   STATUS      RESTARTS   AGE
ef6c746fe255c178c82c00ae6a817621ee5e7d4a497600a9c27b4b11a8v7tvw   0/1     Completed   0          6m40s
etcd-operator-7d48b9fbdc-zm22v                                    3/3     Running     0          6m27s
quay-io-olmqe-etcd-bundle-0-9-2-share                             1/1     Running     0          8m4s

$ oc get csv
NAME                                           DISPLAY                            VERSION                 REPLACES   PHASE
etcdoperator.v0.9.2                            etcd                               0.9.2                              Succeeded

Comment 1 Fan Jia 2020-12-31 07:00:28 UTC
I can't reproduce it , might be the problem of the network.

Comment 2 Jesus M. Rodriguez 2021-01-18 22:48:44 UTC
Using the latest build from ocp-release-operator-sdk I was able to successfully run this bundle. 

```
/tmp/operator-sdk run bundle quay.io/olmqe/etcd-bundle:0.9.2-share
INFO[0005] Successfully created registry pod: quay-io-olmqe-etcd-bundle-0-9-2-share 
INFO[0005] Created CatalogSource: etcd-catalog          
INFO[0005] OperatorGroup "operator-sdk-og" created      
INFO[0005] Created Subscription: etcdoperator-v0-9-2-sub 
INFO[0010] Approved InstallPlan install-vd5kk for the Subscription: etcdoperator-v0-9-2-sub 
INFO[0010] Waiting for ClusterServiceVersion "default/etcdoperator.v0.9.2" to reach 'Succeeded' phase 
INFO[0010]   Waiting for ClusterServiceVersion "default/etcdoperator.v0.9.2" to appear 
INFO[0020]   Found ClusterServiceVersion "default/etcdoperator.v0.9.2" phase: InstallReady 
INFO[0021]   Found ClusterServiceVersion "default/etcdoperator.v0.9.2" phase: Installing 
INFO[0028]   Found ClusterServiceVersion "default/etcdoperator.v0.9.2" phase: Succeeded 
INFO[0028] OLM has successfully installed "etcdoperator.v0.9.2" 
```

Comment 3 Cuiping HUO 2021-01-19 08:57:34 UTC
Verified.

operator-sdk version: "e534ae0b", commit: "e534ae0bf45356506fc823f22667b36e572ee90e", kubernetes version: "v1.19.4", go version: "go1.14.2", GOOS: "linux", GOARCH: "amd64"

# operator-sdk run bundle quay.io/olmqe/etcd-bundle:0.9.2-share --namespace default
INFO[0013] Successfully created registry pod: quay-io-olmqe-etcd-bundle-0-9-2-share 
INFO[0013] Created CatalogSource: etcd-catalog          
INFO[0013] OperatorGroup "operator-sdk-og" created      
INFO[0013] Created Subscription: etcdoperator-v0-9-2-sub 
INFO[0021] Approved InstallPlan install-8jzs5 for the Subscription: etcdoperator-v0-9-2-sub 
INFO[0021] Waiting for ClusterServiceVersion "default/etcdoperator.v0.9.2" to reach 'Succeeded' phase 
INFO[0021]   Waiting for ClusterServiceVersion "default/etcdoperator.v0.9.2" to appear 
INFO[0049]   Found ClusterServiceVersion "default/etcdoperator.v0.9.2" phase: Pending 
INFO[0050]   Found ClusterServiceVersion "default/etcdoperator.v0.9.2" phase: InstallReady 
INFO[0051]   Found ClusterServiceVersion "default/etcdoperator.v0.9.2" phase: Installing 
INFO[0062]   Found ClusterServiceVersion "default/etcdoperator.v0.9.2" phase: InstallReady 
INFO[0063]   Found ClusterServiceVersion "default/etcdoperator.v0.9.2" phase: Installing 
INFO[0065]   Found ClusterServiceVersion "default/etcdoperator.v0.9.2" phase: InstallReady 
INFO[0066]   Found ClusterServiceVersion "default/etcdoperator.v0.9.2" phase: Succeeded 
INFO[0066] OLM has successfully installed "etcdoperator.v0.9.2"

Comment 6 errata-xmlrpc 2021-02-24 15:49:31 UTC
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.7.0 security, 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/RHSA-2020:5633


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