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

Rebasing upstream master #10

Closed
wants to merge 324 commits into from
Closed

Rebasing upstream master #10

wants to merge 324 commits into from

Conversation

tjungblu
Copy link

@tjungblu tjungblu commented Jul 5, 2021

pulling in all the master changes, including the azure stackhub fixes

andyzhangx and others added 30 commits April 23, 2021 03:05
fix: potential race condition in detach disk
Dockerfile fix
…64-build-failure

fix: random arm64 build failure
fail external-e2e prow job on test failure
…lib11

feat: support edge zone managed disk
test: run external e2e test using 1.21 branch
…ding-no-ns

fix: remove namespace in ClusterRole
andyzhangx and others added 27 commits July 14, 2021 10:40
fix v2fix v2fix v2fix v2fix v2fix v2fix v2fix v2
vendor

disk bursting

vendor azure lib
feat: customize hostNetwork setting in helm install
…PointCheck

fix: unmount failure due to incorrect mount path check
…ptions

chore: refine driver parameter setting
feat: add cloudConfigSecret in helm install
…1.6.0

chore: switch master branch to use v1.6.0
This is an autogenerated PR that updates the `.ci-operator.yaml`
to reference the `build_root_image` found in the [ci-operator-config](https://github.com/openshift/release/tree/master/ci-operator/config)
in the [openshift/release](https://github.com/openshift/release) repository.

This is done in preparation for enabling reading the `build_root` from
your repository rather than the central config in [openshift/release](https://github.com/openshift/release).
This allows to update the `build_root` in lockstep with code changes. For details, please
refer to the [docs](https://docs.ci.openshift.org/docs/architecture/ci-operator/#build-root-image).

Note that enabling this feature is mandatory for all OCP components that have an ART build config.

A second autogenerated PR to the [openshift/release repository](https://github.com/openshift/release)
will enable reading the `build_root` from your repository once this PR was merged.

If you have any questions, please feel free to reach out in the #forum-testplatform
channel in the CoreOS Slack.
@openshift-ci
Copy link

openshift-ci bot commented Jul 20, 2021

@tjungblu: PR needs rebase.

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.

@openshift-ci openshift-ci bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 20, 2021
@tjungblu tjungblu closed this Jul 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet