Bug 2054385 - redhat-operatori ndex image build failed with AMQ brew build - amq-interconnect-operator-metadata-container-1.10.13
Summary: redhat-operatori ndex image build failed with AMQ brew build - amq-interconne...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.10
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 4.11.0
Assignee: Renato Granzoto
QA Contact: obochan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-14 20:24 UTC by obochan
Modified: 2022-08-10 10:50 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-10 10:49:41 UTC
Target Upstream Version:
Embargoed:
keyoung: needinfo-


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 10:50:11 UTC

Description obochan 2022-02-14 20:24:18 UTC
Description of problem:
When trying to deploy the amq operator for the ZTP, with version 1.10-13(latest version) the deployment fails to mirror and add the operator.

Version-Release number of selected component (if applicable):


How reproducible:
# find latest amq bundle
brew list-builds  --package=amq-interconnect-operator-metadata-container  --state=COMPLETE --quiet | grep 1.10-10  | sort -V | tail -1 | awk '{print $1}'

# get image from latest bundle
brew --noauth call  --json getBuild  amq-interconnect-operator-metadata-container-1.10-10 | jq -r '.extra.image.index.pull[0]'

# add to our index image in disconnected regsistry
opm index add  --bundles registry-proxy.engineering.redhat.com/rh-osbs/amq7-amq-interconnect-operator-metadata@sha256:785dd106ddabb8be1280303a5e5d117f128058b8d262a5dc4cdda75d6c89a968    --from-index registry.hlxcl11.lab.eng.tlv2.redhat.com:5000/olm/redhat-operator-index:v4.10    --tag registry.hlxcl11.lab.eng.tlv2.redhat.com:5000/olm/redhat-operator-index:v4.10

# last step fails with this error:
"Could not find optional dependencies file\" file=bundle_tmp145777961/metadata load=annotations with=bundle_tmp145777961\ntime=\"2022-02-14T13:40:03-05:00\" level=info msg=\"Could not find optional properties file\" file=bundle_tmp145777961/metadata load=annotations with=bundle_tmp145777961\ntime=\"2022-02-14T13:40:03-05:00\" level=info msg=\"Could not find optional dependencies file\" file=bundle_tmp145777961/metadata load=annotations with=bundle_tmp145777961\ntime=\"2022-02-14T13:40:03-05:00\" level=info msg=\"Could not find optional properties file\" file=bundle_tmp145777961/metadata load=annotations with=bundle_tmp145777961\ntime=\"2022-02-14T13:40:03-05:00\" level=error msg=\"permissive mode disabled\" bundles=\"[registry-proxy.engineering.redhat.com/rh-osbs/amq7-amq-interconnect-operator-metadata@sha256:785dd106ddabb8be1280303a5e5d117f128058b8d262a5dc4cdda75d6c89a968]\" error=\"Invalid bundle amq7-interconnect-operator.v1.10.4, replaces nonexistent bundle amq7-interconnect-operator.v1.10.3\"\nError: Invalid bundle amq7-interconnect-operator.v1.10.4, replaces nonexistent bundle amq7-interconnect-operator.v1.10.3

Actual results:
Mirror of the operator fails

Expected results:
Mirror should work and operator should be added to registry

Comment 2 Ken Young 2022-03-15 19:05:46 UTC
Ofer,

Once this is verified, can we close this?

/KenY

Comment 3 yliu1 2022-03-16 20:03:57 UTC
Ken, this is not fixed yet.

Comment 4 yliu1 2022-03-16 20:04:10 UTC
Ken, this is not fixed yet.

Comment 6 errata-xmlrpc 2022-08-10 10:49:41 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 (Important: OpenShift Container Platform 4.11.0 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-2022:5069


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