Closed Sneha-at closed 1 month ago
Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all
/ok-to-test
@Sneha-at: The following test failed, say /retest
to rerun all failed tests or /retest-required
to rerun all mandatory failed tests:
Test name | Commit | Details | Required | Rerun command |
---|---|---|---|---|
pull-gcp-compute-persistent-disk-csi-driver-e2e | b73bf17725818661f35916f931fa85548f94f51b | link | true | /test pull-gcp-compute-persistent-disk-csi-driver-e2e |
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.
/lgtm /approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: mattcary, Sneha-at
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/test pull-gcp-compute-persistent-disk-csi-driver-e2e
Force merging as there's some infra problem with the e2e tests.
What type of PR is this?
What this PR does / why we need it: Updates the LVM configuration steps in the Dockerfile to support running in read only FS. To achieve this, it updates the entrypoint of the container. Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: