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

Backport 2.6 fixes #783

Merged
merged 13 commits into from
Mar 5, 2024
Merged

Backport 2.6 fixes #783

merged 13 commits into from
Mar 5, 2024

Conversation

ahadas
Copy link
Member

@ahadas ahadas commented Mar 5, 2024

liranr23 and others added 13 commits March 5, 2024 23:33
In OCP 4.15, CDI dropped their annotation of the import disk ID.
We added an annotation `forklift.konveyor.io/disk-source` before to the
DataVolumes only which propagates to the PersistentVolumeClaim. Now it
will also be included on other non-CDI flows.

This change is made as we used the CDI annotation to be an identifier
when importing a disk. Not having it caused an NPE. Now we will use the
forklift annotation.

Signed-off-by: Liran Rotenberg <[email protected]>
When validating a plan we have specific logic that applies for source
providers of type OpenShift but the check of the type of the source
provider didn't take into consideration that the source provider may be
invalid, leading to a sig fault. Here we extend the function that
validates the source providers of type OpenShift with nil-check of the
source provider as done in other validation function for a plan.

Signed-off-by: Arik Hadas <[email protected]>
Similar to the previous change that added a nil-check for the source
provider when validating a plan, here we add a nil-check for the
destination provider thay may also be invalid when posting a plan via
the command line.

Signed-off-by: Arik Hadas <[email protected]>
Move secret setup to the top, as VM validation is skipped when the plan
is executing which can lead to an NPEin checks that rely on it

Signed-off-by: Benny Zlotnik <[email protected]>
Signed-off-by: Benny Zlotnik <[email protected]>
Signed-off-by: Arik Hadas <[email protected]>
Signed-off-by: Arik Hadas <[email protected]>
The previous attempt to fix the execution of the VDDK validation pod
didn't succeed - it allowed to run it on the 'default' namespace but its
execution failed on other retricted namespaces in which the QEMU user
(107) is not included in the allowed range.

In order to fix this properly on OpenShift, we drop RunAsNonRoot and
RunAsUser so that OpenShift would pick a proper user based on the
configuration of the namespace.

Signed-off-by: Arik Hadas <[email protected]>
Signed-off-by: Arik Hadas <[email protected]>
Copy link

sonarqubecloud bot commented Mar 5, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

@ahadas ahadas merged commit 516f0b3 into kubev2v:release-v2.6.0 Mar 5, 2024
6 checks passed
@ahadas ahadas deleted the release-v2.6.0 branch March 5, 2024 22:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants