operator catalog initialization test fails about operator-test-playbooks

[dirgim]

Hi, the playbook fails if a test failed, like in this case. As far as I can see, that was a legitimate failure when running the catalog init test on the operator, indicating there is a package name conflict when trying to initialize an operator catalog.

[jeyaramashok]

this is the operator manifest I'm using pingpong-operator.zip
package.yaml

channels:
- currentCSV: pingpong-operator.v0.1.0
  name: alpha
defaultChannel: stable
packageName: pingpong-operator

does this package already exist in the catalog ?

EDIT:

• fixed to add correct zip file

[jeyaramashok]

how should I fix this?

[dirgim]

If the package already exists in the production catalog, the test replaces it with the manifest that's being tested, so it shouldn't be a problem. I'm not sure what the issue is currently. The manifest you provided has only the package file in it, so I'm not able to reproduce the problem.

[jeyaramashok]

apologies I missed -r flag when I created the zip to upload here . here is right zip file
pingpong-operator.zip

its not in production catalog ( i assume production means certified / ecosystem catalog) , I created the operator locally on my computer

EDIT:

fixed to add correct zip file

[jeyaramashok]

@scoheb I reran the test after fixing my channel name in package.yaml and I still get the same error

[cvp-ops]

@jeyaramashok Can you link us to your up-to-date zip? The ones I download from this issue or the closed one all point a stable while the alpha channel points to 0.1.0 even though latest CSV is 0.1.1

[jeyaramashok]

sorry, here is the right link pingpong-operator.zip . (Ive downloaded it once from the link and made sure the files are right this time)

I have also removed the 0.1.1 version to avoid confusion

these are the contents

$ unzip -l pingpong-operator.zip
Archive:  pingpong-operator.zip
  Length      Date    Time    Name
---------  ---------- -----   ----
        0  03-10-2020 12:23   0.1.0/
      116  03-10-2020 14:46   pingpong-operator.package.yaml
     1197  02-24-2020 23:02   0.1.0/jey.com_pingpongs_crd.yaml
     4899  02-25-2020 23:38   0.1.0/pingpong-operator.v0.1.0.clusterserviceversion.yaml
---------                     -------
     6212                     4 files

channels:
- currentCSV: pingpong-operator.v0.1.0
  name: alpha
defaultChannel: alpha
packageName: pingpong-operator

ran with this directory layout, the catalog initialization test fails. I couldn't find what's missing.

here is the playbook log run-2020-03-11_162208.log

here is zip of /tmp/operator-test operator-test.zip

[scoheb]

@jeyaramashok

Both myself and @dirgim tried testing your operator zip file and the catalog init passed for us.

Please ensure you are setting:

-e production_quay_namespace="certified-operators"

Please re-run with that setting and let us know.

[jeyaramashok]

Thanks Scott, I've now changed to set -e production_quay_namespace="certified-operators"

I ran into the catalog initialization failure again. Then I changed my directory structure looking at other manifests. That seemed to fix the problem.

So initially I had version directory 0.1.0 with crd & csv like this:

$ ls pingpong-operator/
total 4.0K
drwxr-x--- 2 jey 137 Mar  4 12:28 0.1.0/
-rw-r--r-- 1 jey 117 Mar 10 12:47 pingpong-operator.package.yaml

Then I removed that version dir 0.1.0 and made it flat:

$ ls pingpong-operator/
total 16K
-rw-r--r-- 1 jey 4.8K Mar 18 12:05 pingpong-operator.v0.1.0.clusterserviceversion.yaml
-rw-r--r-- 1 jey  116 Mar 18 12:05 pingpong-operator.package.yaml
-rw-r--r-- 1 jey 1.2K Mar 18 12:05 jey.com_pingpongs_crd.yaml

Then playbooks ran succesfully.