[FCOS] bootstrap: replace CRIO's hooks dir on bootstrap#2795
[FCOS] bootstrap: replace CRIO's hooks dir on bootstrap#2795openshift-merge-robot merged 2 commits intoopenshift:fcosfrom
Conversation
This would ensure CRIO's bootstrap would use FCOS-compatible hooks dir. PR openshift/machine-config-operator#1311 would do the same for masters and workers
|
Is there a reason not to support both locations? I.e. can't we tolerate both? |
|
Crio chokes if one of the directories doesn't exist |
|
This is because /lgtm |
|
@LorbusChris: once the present PR merges, I will cherry-pick it on top of master in a new PR and assign it to you. DetailsIn response to this:
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. |
|
/override e2e-vsphere Needs #2671 |
|
@vrutkovs: /override requires a failed status context to operate on.
Only the following contexts were expected:
DetailsIn response to this:
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. |
|
/override ci/prow/e2e-vsphere |
|
@vrutkovs: Overrode contexts on behalf of vrutkovs: ci/prow/e2e-vsphere DetailsIn response to this:
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. |
|
Man, |
I'll add a patch to fix mkdir calls |
@cgwalters I don't think we support it any longer: https://src.fedoraproject.org/rpms/oci-systemd-hook/c/d5081a1acda993325729a45202fa87598c89696a?branch=master This may be different in RHCOS, though, but IIRC @miabbott mentioned something about dropping it from there as well. |
|
/retest |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: LorbusChris, vrutkovs The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
15 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@vrutkovs: The following tests failed, say
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. DetailsInstructions 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. I understand the commands that are listed here. |
|
Bootstrap has started crio in run 219 /override ci/prow/e2e-aws |
|
@vrutkovs: Overrode contexts on behalf of vrutkovs: ci/prow/e2e-aws, ci/prow/e2e-vsphere DetailsIn response to this:
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. |
|
@LorbusChris: #2795 failed to apply on top of branch "master": DetailsIn response to this:
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. |
|
@vrutkovs automated cherry-pck failed, mind rebasing this on top of master for a PR there? |
This would ensure CRIO's bootstrap would use FCOS-compatible hooks dir.
PR openshift/machine-config-operator#1311 would
do the same for masters and workers.
This also ensures mkdir calls have
--parentso that these would not fail if dirs already exist/cc @LorbusChris @smarterclayton