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.58] Fix populators not repopulating pvc after it was deleted #3071

Commits on Jan 17, 2024

  1. Add tests to verify pvc is recreated and repopulated after delete

    Signed-off-by: Shelly Kagan <skagan@redhat.com>
    ShellyKa13 authored and kubevirt-bot committed Jan 17, 2024
    Configuration menu
    Copy the full SHA
    d5296d2 View commit details
    Browse the repository at this point in the history
  2. Create import/upload source CR in case population pod is not succeeded

    In case someone deleted the pvc a new pvc is created and the
    status of the dv is still succeded. when using populators
    in order for the population to restart and the dv state to change accordingly
    we need to retrigger the population, this depends on the existing of the source CR.
    That CR should exist as long as the pvc pod state is not succeeded.
    When the pvc is recreated the succeded pod state annotation was removed.
    Adjusted UT accordingly
    
    Signed-off-by: Shelly Kagan <skagan@redhat.com>
    ShellyKa13 authored and kubevirt-bot committed Jan 17, 2024
    Configuration menu
    Copy the full SHA
    0f3c162 View commit details
    Browse the repository at this point in the history
  3. Adjust tests after review

    Move cloner test to a parallel test suite.
    Simplify import test.
    
    Signed-off-by: Shelly Kagan <skagan@redhat.com>
    ShellyKa13 authored and kubevirt-bot committed Jan 17, 2024
    Configuration menu
    Copy the full SHA
    6ceb775 View commit details
    Browse the repository at this point in the history