Bug 2002363 - Missing ability to provide deployment time ImageContentSourcePolicy during ZTP flow
Summary: Missing ability to provide deployment time ImageContentSourcePolicy during ZT...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Telco Edge
Version: 4.8
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.10.0
Assignee: Ian Miller
QA Contact: Marius Cornea
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-08 15:58 UTC by Marius Cornea
Modified: 2022-03-16 11:39 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-16 11:38:43 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift-kni cnf-features-deploy pull 664 0 None Merged Bug 2002363: ztp: Support disconnected registry. 2021-10-18 15:59:00 UTC
Github openshift-kni cnf-features-deploy pull 801 0 None Merged ztp: allow siteconfig extra-manifest, separate siteconfig from PGT and update resource generator 2022-03-03 14:51:06 UTC
Github openshift-kni cnf-features-deploy pull 862 0 None Merged ztp: Add ztp-deploy-wave annotation in source CR 2022-03-03 14:53:16 UTC
Red Hat Product Errata RHBA-2022:0798 0 None None None 2022-03-16 11:39:09 UTC

Description Marius Cornea 2021-09-08 15:58:01 UTC 
Description of problem:

In a disconnected environment creating the ImageContentSourcePolicy providing mirror configuration for the operators setup in the same time with the operators subscriptions can lead to the issue described in BZ#1984829 where the operators InstallPlans get blocked and operators installation cannot succeed. In order to avoid this condition the ImageContentSourcePolicy needs to be created at deployment time which is not possible at this moment. 

To workaround this issue the ImageContentSourcePolicy can be injected in the ArgoCD container image by:


cat 04-rh-internal-icsp.yaml

apiVersion: operator.openshift.io/v1alpha1
kind: ImageContentSourcePolicy
metadata:
  name: fec-disconnected-icsp
spec:
  repositoryDigestMirrors:
  - mirrors:
    - {{ disconnected_registry }}
    source: registry.redhat.io


Containerfile:

FROM quay.io/redhat_emp1/ztp-site-generator:latest
COPY 04-rh-internal-icsp.yaml /usr/src/hook/ztp/source-crs/extra-manifest/04-rh-internal-icsp.yaml

 
Version-Release number of selected component (if applicable):
4.8
Comment 1 Nick Stielau 2021-10-07 17:19:08 UTC 
Assuming not a blocker for 4.9.  Please look for blocker? BZs and make a blocker determination.
Comment 2 Ian Miller 2021-10-19 11:56:30 UTC 
Linked PR supports ICSP as post-deployment configuration. This BZ is to include during deployment. Reopening.
Comment 4 Ian Miller 2022-03-03 14:53:16 UTC 
PR 801 adds support for user-supplied extra manifests. These manifests are applied to the cluster during installation.
Comment 5 Ian Miller 2022-03-03 14:56:16 UTC 
PR 862 adds support for phased installation of the post-installation configuration. The defaults apply the ICSP in the wave before Subscriptions. This ordering ensures that the ICSP exists prior to the subscription being created.
Comment 8 errata-xmlrpc 2022-03-16 11:38:43 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 (OpenShift Container Platform 4.9.24 bug fix 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/RHBA-2022:0798
Note You need to log in before you can comment on or make changes to this bug.