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

OCPBUGS-29072: Add infrastructure annotations #82

Merged

Conversation

bertinatto
Copy link
Member

All required infrastructure-required annotations are added, plus the CSI one, which is optional.

CC @openshift/storage

All required infrastructure-required annotations are added, plus
the CSI one, which is optional.
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Feb 9, 2024
@openshift-ci-robot
Copy link

@bertinatto: This pull request references Jira Issue OCPBUGS-29072, which is invalid:

  • expected the bug to target the "4.16.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

All required infrastructure-required annotations are added, plus the CSI one, which is optional.

CC @openshift/storage

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.

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 9, 2024
@bertinatto
Copy link
Member Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Feb 9, 2024
@openshift-ci-robot
Copy link

@bertinatto: This pull request references Jira Issue OCPBUGS-29072, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.16.0) matches configured target version for branch (4.16.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (wduan@redhat.com), skipping review request.

In response to this:

/jira refresh

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.

@mpatlasov
Copy link
Contributor

/retest-required

@mpatlasov
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 9, 2024
Copy link
Contributor

openshift-ci bot commented Feb 9, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bertinatto, mpatlasov

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:
  • OWNERS [bertinatto,mpatlasov]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD c3b5e86 and 2 for PR HEAD d898ff7 in total

Copy link
Contributor

openshift-ci bot commented Feb 12, 2024

@bertinatto: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

  • /test ci-index-gcp-filestore-csi-driver-operator-bundle
  • /test images
  • /test operator-e2e
  • /test unit
  • /test verify
  • /test verify-deps

The following commands are available to trigger optional jobs:

  • /test operator-e2e-extended
  • /test security

Use /test all to run all jobs.

In response to this:

/retest operator-e2e

ERROR: (gcloud.filestore.instances.delete) NOT_FOUND: Resource 'projects/XXXXXXXXXXXXXXXXXXXXXX/locations/us-central1-b/instances/pvc-f345edb2-bd48-4f16-8847-dc79dcefb24a' was not found
- '@type': type.googleapis.com/google.rpc.ResourceInfo
 resourceName: projects/XXXXXXXXXXXXXXXXXXXXXX/locations/us-central1-b/instances/pvc-f345edb2-bd48-4f16-8847-dc79dcefb24a
{"component":"entrypoint","error":"wrapped process failed: exit status 1","file":"k8s.io/test-infra/prow/entrypoint/run.go:84","func":"k8s.io/test-infra/prow/entrypoint.Options.internalRun","level":"error","msg":"Error executing test process","severity":"error","time":"2024-02-10T02:43:32Z"}
error: failed to execute wrapped command: exit status 1

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.

@bertinatto
Copy link
Member Author

bertinatto commented Feb 12, 2024

/test operator-e2e

ERROR: (gcloud.filestore.instances.delete) NOT_FOUND: Resource 'projects/XXXXXXXXXXXXXXXXXXXXXX/locations/us-central1-b/instances/pvc-f345edb2-bd48-4f16-8847-dc79dcefb24a' was not found
- '@type': type.googleapis.com/google.rpc.ResourceInfo
  resourceName: projects/XXXXXXXXXXXXXXXXXXXXXX/locations/us-central1-b/instances/pvc-f345edb2-bd48-4f16-8847-dc79dcefb24a
{"component":"entrypoint","error":"wrapped process failed: exit status 1","file":"k8s.io/test-infra/prow/entrypoint/run.go:84","func":"k8s.io/test-infra/prow/entrypoint.Options.internalRun","level":"error","msg":"Error executing test process","severity":"error","time":"2024-02-10T02:43:32Z"}
error: failed to execute wrapped command: exit status 1

@bertinatto
Copy link
Member Author

/retest operator-e2e

 error: failed to push image registry.build02.ci.openshift.org/ci-op-kbdmydqg/release:latest: unable to upload new layer (0): Patch "https://registry.build02.ci.openshift.org/v2/ci-op-kbdmydqg/release/blobs/uploads/2f0173a2-4a84-438c-8006-5239e8c269e9?_state=8Xjj1Uf7tDGt0al6GUJUZv2eMRA3c_l8ykyyZJ3DZgN7Ik5hbWUiOiJjaS1vcC1rYmRteWRxZy9yZWxlYXNlIiwiVVVJRCI6IjJmMDE3M2EyLTRhODQtNDM4Yy04MDA2LTUyMzllOGMyNjllOSIsIk9mZnNldCI6MCwiU3RhcnRlZEF0IjoiMjAyNC0wMi0xMlQxMzoyNDowOS45ODEwNDQxOTFaIn0%3D": operator "cluster-samples-operator" contained an invalid image-references file: input image stream has multiple versions defined for version kubectl for all the tags 1.29.1,1.28.2,1.29.0
{"component":"entrypoint","error":"wrapped process failed: exit status 1","file":"k8s.io/test-infra/prow/entrypoint/run.go:84","func":"k8s.io/test-infra/prow/entrypoint.Options.internalRun","level":"error","msg":"Error executing test process","severity":"error","time":"2024-02-12T13:24:11Z"} 

Copy link
Contributor

openshift-ci bot commented Feb 12, 2024

@bertinatto: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

  • /test ci-index-gcp-filestore-csi-driver-operator-bundle
  • /test images
  • /test operator-e2e
  • /test unit
  • /test verify
  • /test verify-deps

The following commands are available to trigger optional jobs:

  • /test operator-e2e-extended
  • /test security

Use /test all to run all jobs.

In response to this:

/retest operator-e2e

error: failed to push image registry.build02.ci.openshift.org/ci-op-kbdmydqg/release:latest: unable to upload new layer (0): Patch "https://registry.build02.ci.openshift.org/v2/ci-op-kbdmydqg/release/blobs/uploads/2f0173a2-4a84-438c-8006-5239e8c269e9?_state=8Xjj1Uf7tDGt0al6GUJUZv2eMRA3c_l8ykyyZJ3DZgN7Ik5hbWUiOiJjaS1vcC1rYmRteWRxZy9yZWxlYXNlIiwiVVVJRCI6IjJmMDE3M2EyLTRhODQtNDM4Yy04MDA2LTUyMzllOGMyNjllOSIsIk9mZnNldCI6MCwiU3RhcnRlZEF0IjoiMjAyNC0wMi0xMlQxMzoyNDowOS45ODEwNDQxOTFaIn0%3D": operator "cluster-samples-operator" contained an invalid image-references file: input image stream has multiple versions defined for version kubectl for all the tags 1.29.1,1.28.2,1.29.0
{"component":"entrypoint","error":"wrapped process failed: exit status 1","file":"k8s.io/test-infra/prow/entrypoint/run.go:84","func":"k8s.io/test-infra/prow/entrypoint.Options.internalRun","level":"error","msg":"Error executing test process","severity":"error","time":"2024-02-12T13:24:11Z"} 

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.

@bertinatto
Copy link
Member Author

/test operator-e2e

 error: failed to push image registry.build02.ci.openshift.org/ci-op-kbdmydqg/release:latest: unable to upload new layer (0): Patch "https://registry.build02.ci.openshift.org/v2/ci-op-kbdmydqg/release/blobs/uploads/2f0173a2-4a84-438c-8006-5239e8c269e9?_state=8Xjj1Uf7tDGt0al6GUJUZv2eMRA3c_l8ykyyZJ3DZgN7Ik5hbWUiOiJjaS1vcC1rYmRteWRxZy9yZWxlYXNlIiwiVVVJRCI6IjJmMDE3M2EyLTRhODQtNDM4Yy04MDA2LTUyMzllOGMyNjllOSIsIk9mZnNldCI6MCwiU3RhcnRlZEF0IjoiMjAyNC0wMi0xMlQxMzoyNDowOS45ODEwNDQxOTFaIn0%3D": operator "cluster-samples-operator" contained an invalid image-references file: input image stream has multiple versions defined for version kubectl for all the tags 1.29.1,1.28.2,1.29.0
{"component":"entrypoint","error":"wrapped process failed: exit status 1","file":"k8s.io/test-infra/prow/entrypoint/run.go:84","func":"k8s.io/test-infra/prow/entrypoint.Options.internalRun","level":"error","msg":"Error executing test process","severity":"error","time":"2024-02-12T13:24:11Z"} 

@dobsonj
Copy link
Member

dobsonj commented Feb 12, 2024

/retest

@bertinatto
Copy link
Member Author

/test operator-e2e

{  ["operator-e2e" pod "operator-e2e-openshift-e2e-test" failed: could not watch pod: context canceled
Link to step on registry info site: https://steps.ci.openshift.org/reference/openshift-e2e-test
Link to job on registry info site: https://steps.ci.openshift.org/job?org=openshift&repo=gcp-filestore-csi-driver-operator&branch=main&test=operator-e2e, cancelled]}

Copy link
Contributor

openshift-ci bot commented Feb 14, 2024

@bertinatto: 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
ci/prow/operator-e2e-extended d898ff7 link false /test operator-e2e-extended

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

@bertinatto
Copy link
Member Author

/test operator-e2e

 	3h1m29s
{  ["operator-e2e" pod "operator-e2e-openshift-e2e-test" failed: could not watch pod: context canceled
Link to step on registry info site: https://steps.ci.openshift.org/reference/openshift-e2e-test
Link to job on registry info site: https://steps.ci.openshift.org/job?org=openshift&repo=gcp-filestore-csi-driver-operator&branch=main&test=operator-e2e, cancelled]}

@openshift-merge-bot openshift-merge-bot bot merged commit 0015a83 into openshift:main Feb 15, 2024
8 of 9 checks passed
@openshift-ci-robot
Copy link

@bertinatto: Jira Issue OCPBUGS-29072: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-29072 has been moved to the MODIFIED state.

In response to this:

All required infrastructure-required annotations are added, plus the CSI one, which is optional.

CC @openshift/storage

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.

@bertinatto
Copy link
Member Author

/cherry-pick release-4.15

@openshift-cherrypick-robot

@bertinatto: #82 failed to apply on top of branch "release-4.15":

Applying: Add infrastructure annotations
Using index info to reconstruct a base tree...
M	config/manifests/stable/gcp-filestore-csi-driver-operator.clusterserviceversion.yaml
Falling back to patching base and 3-way merge...
Auto-merging config/manifests/stable/gcp-filestore-csi-driver-operator.clusterserviceversion.yaml
CONFLICT (content): Merge conflict in config/manifests/stable/gcp-filestore-csi-driver-operator.clusterserviceversion.yaml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Add infrastructure annotations
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-4.15

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants