Bug 1884404 - opm index add does not error when multiple channel head candidates exist
Summary: opm index add does not error when multiple channel head candidates exist
Keywords:
Status: CLOSED DUPLICATE of bug 1885425
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: OLM
Version: 4.6
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.7.0
Assignee: Ankita Thomas
QA Contact: Jian Zhang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-01 20:44 UTC by lgallett
Modified: 2020-11-30 18:26 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-30 18:26:49 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description lgallett 2020-10-01 20:44:38 UTC
Description of problem:

adding two bundles that are both channel heads to an index should produce an error


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

latest

How reproducible:

always

Steps to Reproduce:

opm index add -b="registry-proxy.engineering.redhat.com/rh-osbs/web-terminal-operator-metadata@sha256:f172e2293caa7ef04e0f4bf9570c4e91000d570456b0d9b7f34ce54c14d895fa,registry-proxy.engineering.redhat.com/rh-osbs/web-terminal-operator-metadata@sha256:6c2e7e3abe33ea2e4fbd4fb8d4a75c0b52288be74a70e0cba59a59df2d0ac5fc" -t="quay.io/galletti94/my-index:web-terminal" -u=docker

create two bundles that have no replaces field and are pushing to the same channel. add these to an index

Actual results:

succeeds and order is determined by the order of the bundles in the command.

Expected results:

should fail and raise an error

Additional info:

Comment 3 Kevin Rizza 2020-11-30 18:26:49 UTC

*** This bug has been marked as a duplicate of bug 1885425 ***


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