-
Notifications
You must be signed in to change notification settings - Fork 16
NO-JIRA: CARRY: Restore OWNERS to upstream #224
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
Conversation
This reverts commit 68be840. This release-specific commit should not be on master.
…penshift-4.9-ose-openstack-cinder-csi-driver Updating ose-openstack-cinder-csi-driver images to be consistent with ART
Upstream merge
imagebuilder used by OSBS/brew to create the product images does not handle slashes in `COPY` commands well. See e.g. openshift/imagebuilder#139. This commit ensures the tree is actually present in the container.
Fix ART build
…penshift-4.9-ose-openstack-cloud-controller-manager Updating ose-openstack-cloud-controller-manager images to be consistent with ART
Remove Fedosin from Owners
Add 'nouuid' mount option to all XFS mounts to be able to mount a volume and its restored snapshot on the same node. Without the option, such a mount fails, because XFS detects that two different volumes with the same filesystem UUID are being mounted.
Use the same pattern across all Dockerfiles and remove duplicates. Also remove the dockerfile for the deprecated Manila provisioner, for which the image is not used any more in 4.9.
Bug 1996783: Bump to Go v1.16 and OCP v4.9
The file named `.ci-operator.yaml` governs which image is used in the OpenShift CI. This has to be updated as well.
Bug 1996783: Bump Go to v1.16 - fixup
Bug 1996031: Merge upstream tag 'v1.22.0'
Bug 1988374: UPSTREAM: 1988374: Disable uuid checks on XFS (kubernetes#1614)
…penshift-4.10-ose-openstack-cloud-controller-manager Updating ose-openstack-cloud-controller-manager images to be consistent with ART
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dulek, mdbooth, stephenfin 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 |
|
/rename No-JIRA: CARRY: Restore OWNERS to upstream |
|
/jira refresh |
|
@mandre: No Jira issue is referenced in the title of this pull request. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
/rename NO-JIRA: CARRY: Restore OWNERS to upstream |
|
/retitle NO-JIRA: CARRY: Restore OWNERS to upstream |
|
@dulek: This pull request explicitly references no jira issue. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
/verify-owners |
|
/hold |
|
this requires openshift/release#44277 |
We can still remove the hold because verify-owners won't pass until it merges. |
|
The following users are mentioned in OWNERS file(s) but are untrusted for the following reasons. One way to make the user trusted is to add them as members of the openshift org. You can then trigger verification by writing
|
|
/hold cancel |
|
/verify-owners |
|
I'm about to rebase master on top of upstream release-1.29 and I've included this change already. |
|
No longer needed after the rebase |
|
PR needs rebase. 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. |
|
@mandre: Closed this PR. 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. |
We are now using DOWNSTREAM_OWNERS instead. We can restore OWNERS and OWNERS_ALIASES to upstream to avoid future merge conflicts.
/hold