Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-10304

[Samsung] official document needs details about creating disconnected environment install-config.yaml after mirroring with oc-mirror.

XMLWordPrintable

    • Important
    • No
    • 6
    • OSDOCS Sprint 241, OSDOCS Sprint 242, OSDOCS Sprint 243
    • 3
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • N/A
    • Release Note Not Required
    • 8/8: docs team has PR in progress, seeking review & backport(s) clarification; KNIECO-7139

      Description of problem:

      There is not clear guide about creating install-config.yaml when using oc-mirror.
      
      Before oc-mirror method released, RH guided customer to use 'oc adm relase mirror' command. When 'oc adm relase mirror' is used, the 'imageContentSources:' was out like below at the end of the mirror process.
      ~~~
      imageContentSources: 
      - mirrors:
        - <local_registry>/<local_repository_name>/release
        source: quay.io/openshift-release-dev/ocp-release
      - mirrors:
        - <local_registry>/<local_repository_name>/release
        source: quay.io/openshift-release-dev/ocp-v4.0-art-dev 
      ~~~
      
      However, when customers are using oc-mirror, there is not output printed about 'imageContentSources:'. There is only the results-*/imageContentSourcePolicy.yaml file. Customers don't know what to put in the 'imageContentSources:' part of install-config.ymal[1].
      [1] https://docs.openshift.com/container-platform/4.12/installing/installing_bare_metal/installing-restricted-networks-bare-metal.html#installation-bare-metal-config-yaml_installing-restricted-networks-bare-metal
      ~~~
      imageContentSources: 
      - mirrors:
        - <local_registry>/<local_repository_name>/release
        source: quay.io/openshift-release-dev/ocp-release
      - mirrors:
        - <local_registry>/<local_repository_name>/release
        source: quay.io/openshift-release-dev/ocp-v4.0-art-dev
      ~~~

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

      4.11, 4.12 documentation

      How reproducible:

      NA

      Steps to Reproduce:

      NA
      

      Actual results:

      Before, when I was using 'oc adm release mirror' command, I could see ' 'imageContentSources:' when the mirror process was completed. On the contrary, when I'm using oc-mrirror there is no 'imageContentSources:' printed. I know there is output called imageContentSourcePolicy.yaml but this is to be used after installation.

      Expected results:

      Please make 'imageContentSources:' printed at the end of the mirror process so I can copy and paste for install-config.yaml.
      Or, Please revise the official document about install-config.yaml part to guide where I can find the 'imageContentSources:' when using oc-mirror.

      Additional info:

      https://access.redhat.com/support/cases/#/case/03343389
      There is the former case related for this.

            rhn-support-jbrigman James Brigman
            soh@redhat.com Sehee Oh
            Gaoyun Pei Gaoyun Pei
            James Brigman James Brigman
            Votes:
            1 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated:
              Resolved:

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 6 weeks
                6w