ci: fix prow-build.sh to fetch same repos#802
Conversation
openshift-ci
Bot
added
the
approved
openshift-ci
Bot
added
the
do-not-merge/work-in-progress
|
/test validate |
|
/test validate |
|
Chasing down the new failure in openshift/release#28790 |
The `validate` job started to fail with:
```
fatal: unsafe repository ('/go/src/github.com/openshift/os' is owned by someone else)
To add an exception for this directory, call:
git config --global --add safe.directory /go/src/github.com/openshift/os
```
Applying this suggestion as part of the `ci/validate.sh` script
(see openshift/os#802) fails with the error:
```
+ git config --global --add safe.directory /go/src/github.com/openshift/os
error: could not lock config file //.gitconfig: Permission denied
```
I suspect this is related to how the random user ID is configured in
OCP pods, similar to what is described in openshift/os#781, so I tried
using the `ci/set-openshift-user.sh` script as part of the `validate`
job.
Through trial and error, I found that using the `fcos-buildroot`
container based on F36 would not work with this change and had to
switch to using the `cosa:latest` container. Going further down the
rabbit hole, I found that I didn't need to use the
`ci/set-openshift-user.sh` script at all and just the `cosa:latest`
container was enough to get the `validate` job to pass. I don't claim
to fully understand why this is the case, but it does effectively
unblock the `validate` job.
|
/test validate |
|
/test validate |
The introduction of new Prow periodic jobs (openshift/release#27779) means we have to keep the `prow-build.sh` and `prow-build-test-qemu.sh` scripts in sync, with regards to fetching the repo configs. This brings `prow-build.sh` in sync with the changes from openshift#796. Closes openshift#801
openshift-ci
Bot
removed
the
do-not-merge/work-in-progress
|
/retest |
|
/retest |
|
The |
|
OK, this is just failing on the bits that should be fixed in #810 |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cgwalters, HuijingHei, miabbott 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 |
|
/override ci/prow/test-in-cluster |
|
@cgwalters: Overrode contexts on behalf of cgwalters: ci/prow/test-in-cluster, ci/prow/test-qemu-metal 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. |
|
Forcing merge to get our CI going. |
|
@miabbott: The following test failed, say
Full PR test history. Your PR dashboard. 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. |
|
/cherrypick release-4.11 |
|
@cgwalters: new pull request created: #813 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. |
5 participants
The introduction of new Prow periodic jobs (openshift/release#27779)
means we have to keep the
prow-build.shandprow-build-test-qemu.shscripts in sync, with regards to fetchingthe repo configs.
This brings
prow-build.shin sync with the changes from #796.Closes #801