Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

oc mirror from imagesets failed to build catalog image #629

Closed
theodor2311 opened this issue May 9, 2023 · 4 comments
Closed

oc mirror from imagesets failed to build catalog image #629

theodor2311 opened this issue May 9, 2023 · 4 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@theodor2311
Copy link

Version

Client Version: version.Info{Major:"", Minor:"", GitVersion:"4.12.0-202304070941.p0.g7635353.assembly.stream-7635353", GitCommit:"7635353ed12fdcb725855b1d4165cfec8dc10e16", GitTreeState:"clean", BuildDate:"2023-04-07T10:11:09Z", GoVersion:"go1.19.6", Compiler:"gc", Platform:"linux/amd64"}

What happened?

oc mirror from imagesets failed to build catalog image.

rebuilding catalog images
Rendering catalog image "test.local:8443/redhat/redhat-operator-index:v4.12" with file-based catalog
"Using existing OCI layout to oc-mirror-workspace/images.3253033354/catalogs/registry.redhat.io/redhat/redhat-operator-index/v4.12/layout"
error: error rebuilding catalog images from file-based catalogs: error creating OCI layout: stat oc-mirror-workspace/images.3253033354/catalogs/registry.redhat.io/redhat/redhat-operator-index/v4.12/layout/index.json: no such file or directory

What did you expect to happen?

The oc mirror from imagesets should run without error.

How to reproduce it (as minimally and precisely as possible)?

Using the following command on the same machine with my testing imageset-config.yaml configuration will produce the error every time.

oc mirror --config=./imageset-config.yaml file://mirror
oc mirror --from=mirror docker://test.local:8443 --dest-skip-tls -v=9

imageset-config.yaml

apiVersion: mirror.openshift.io/v1alpha2
archiveSize: 1
storageConfig:
  local:
    path: metadata
mirror:
  platform:
    architectures:
      - amd64
    channels:
    - name: eus-4.12
      minVersion: 4.12.13
      maxVersion: 4.12.13
    - name: stable-4.12
      minVersion: 4.12.13
  operators:
  - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.12
    packages:
    - name: 3scale-operator
      channels:
      - name: threescale-2.13
    - name: local-storage-operator
      channels:
      - name: stable
    - name: cluster-logging
      channels:
      - name: stable
    - name: elasticsearch-operator
      channels:
      - name: stable

Anything else we need to know?

Using the same configuration with the partially disconnected approach is working fine for me.

oc mirror --config=./imageset-config.yaml docker://test.local:8443 --dest-skip-tls # Working fine
@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 7, 2023
@openshift-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 7, 2023
@openshift-bot
Copy link
Contributor

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci
Copy link

openshift-ci bot commented Oct 7, 2023

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci openshift-ci bot closed this as completed Oct 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

2 participants