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

[release-v1.57] Don't use scratch space for registry node pull imports #2846

Commits on Aug 14, 2023

  1. Don't use scratch space for registry node pull imports

    When importing via node container runtime cache, we always have the image handy locally.
    This manifests itself in the form of a bug where we loop over
    ```bash
    E0813 13:32:38.443088       1 data-processor.go:251] scratch space required and none found
    E0813 13:32:38.443102       1 importer.go:181] scratch space required and none found
    ```
    On registry node pull imports where images are not raw
    
    Signed-off-by: Alex Kalenyuk <akalenyu@redhat.com>
    akalenyu authored and kubevirt-bot committed Aug 14, 2023
    Configuration menu
    Copy the full SHA
    5c561fb View commit details
    Browse the repository at this point in the history