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-34918: Use build_root image from repository for coredns-ocp-dnsnamresolver #52809

Conversation

arkadeepsen
Copy link
Member

@arkadeepsen arkadeepsen commented Jun 5, 2024

This PR uses build_root image from repository for coredns-ocp-dnsnamresolver.

@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. labels Jun 5, 2024
@openshift-ci-robot
Copy link
Contributor

@arkadeepsen: This pull request references Jira Issue OCPBUGS-34918, 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.17.0) matches configured target version for branch (4.17.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @lihongan

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

In response to this:

This PR bumps the go version from 1.21 to 1.22 of build_root image for the coredns-ocp-dnsnamresolver repo.

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-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Jun 5, 2024
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 5, 2024
@arkadeepsen
Copy link
Member Author

/pj-rehearse auto-ack

@openshift-ci-robot
Copy link
Contributor

@arkadeepsen: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@arkadeepsen arkadeepsen force-pushed the golang-bump-coredns-ocp-dnsnamresolver branch from 2935f97 to 539e67e Compare June 5, 2024 07:46
@arkadeepsen
Copy link
Member Author

/pj-rehearse auto-ack

@openshift-ci-robot
Copy link
Contributor

@arkadeepsen: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@arkadeepsen arkadeepsen force-pushed the golang-bump-coredns-ocp-dnsnamresolver branch from 539e67e to ccee906 Compare June 5, 2024 08:15
@arkadeepsen
Copy link
Member Author

/pj-rehearse auto-ack

@openshift-ci-robot
Copy link
Contributor

@arkadeepsen: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@arkadeepsen arkadeepsen force-pushed the golang-bump-coredns-ocp-dnsnamresolver branch from ccee906 to d43890e Compare June 5, 2024 11:37
@arkadeepsen
Copy link
Member Author

/pj-rehearse

@openshift-ci-robot
Copy link
Contributor

@arkadeepsen: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@arkadeepsen
Copy link
Member Author

arkadeepsen commented Jun 5, 2024

openshift/coredns-ocp-dnsnameresolver#9 should fix the issue of ci/rehearse/openshift/coredns-ocp-dnsnameresolver/main/unit-operator and ci/rehearse/openshift/coredns-ocp-dnsnameresolver/main/build-operator not being able to query the go module due to the usage of -mod=vendor. The PR adds a GOFLAGS='' when using go install to remove any existing flags.

@candita
Copy link
Contributor

candita commented Jun 5, 2024

/assign @alebedev87

@lihongan
Copy link
Contributor

lihongan commented Jun 6, 2024

/retest

@Miciah
Copy link
Contributor

Miciah commented Jun 6, 2024

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. and removed jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. labels Jun 6, 2024
@openshift-ci-robot
Copy link
Contributor

@Miciah: This pull request references Jira Issue OCPBUGS-34918, which is valid.

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

Requesting review from QA contact:
/cc @lihongan

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.

@@ -7,7 +7,7 @@ build_root:
image_stream_tag:
name: release
namespace: openshift
tag: golang-1.21
tag: rhel-9-release-golang-1.22-openshift-4.17
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that we can set up the build_root from the repository like it's done in CoreDNS. This would simplify the ci config and move the version update to the repository where this decision is taken.

@arkadeepsen arkadeepsen force-pushed the golang-bump-coredns-ocp-dnsnamresolver branch from d43890e to e7812a5 Compare June 7, 2024 10:19
@arkadeepsen arkadeepsen changed the title OCPBUGS-34918: Bump go version from 1.21 to 1.22 of build_root image for the coredns-ocp-dnsnamresolver repo OCPBUGS-34918: Use build_root image from repository for coredns-ocp-dnsnamresolver Jun 7, 2024
@openshift-ci-robot
Copy link
Contributor

@arkadeepsen: This pull request references Jira Issue OCPBUGS-34918, which is valid.

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

Requesting review from QA contact:
/cc @lihongan

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

In response to this:

This PR uses build_root image from repository for coredns-ocp-dnsnamresolver.

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.

@alebedev87
Copy link
Contributor

/lgtm

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

openshift-ci bot commented Jun 7, 2024

@arkadeepsen: The following tests 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/rehearse/openshift/coredns-ocp-dnsnameresolver/main/build-operator d43890e link unknown /pj-rehearse pull-ci-openshift-coredns-ocp-dnsnameresolver-main-build-operator
ci/rehearse/openshift/coredns-ocp-dnsnameresolver/main/unit-operator d43890e link unknown /pj-rehearse pull-ci-openshift-coredns-ocp-dnsnameresolver-main-unit-operator

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

@arkadeepsen arkadeepsen force-pushed the golang-bump-coredns-ocp-dnsnamresolver branch from e7812a5 to 90292d4 Compare June 7, 2024 10:30
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Jun 7, 2024
@openshift-ci-robot
Copy link
Contributor

[REHEARSALNOTIFIER]
@arkadeepsen: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
pull-ci-openshift-coredns-ocp-dnsnameresolver-main-build openshift/coredns-ocp-dnsnameresolver presubmit Ci-operator config changed
pull-ci-openshift-coredns-ocp-dnsnameresolver-main-build-operator openshift/coredns-ocp-dnsnameresolver presubmit Ci-operator config changed
pull-ci-openshift-coredns-ocp-dnsnameresolver-main-unit openshift/coredns-ocp-dnsnameresolver presubmit Ci-operator config changed
pull-ci-openshift-coredns-ocp-dnsnameresolver-main-unit-operator openshift/coredns-ocp-dnsnameresolver presubmit Ci-operator config changed
pull-ci-openshift-coredns-ocp-dnsnameresolver-main-verify openshift/coredns-ocp-dnsnameresolver presubmit Ci-operator config changed
pull-ci-openshift-coredns-ocp-dnsnameresolver-main-verify-operator openshift/coredns-ocp-dnsnameresolver presubmit Ci-operator config changed
Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse abort to abort all active rehearsals

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@arkadeepsen
Copy link
Member Author

Adding the label as the rehearse won't pass on the main branch. openshift/coredns-ocp-dnsnameresolver#9 adds the necessary changes.

/pj-rehearse ack

@openshift-ci-robot
Copy link
Contributor

@arkadeepsen: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Jun 7, 2024
Copy link
Contributor

openshift-ci bot commented Jun 7, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alebedev87, arkadeepsen

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:

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

@alebedev87
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 7, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit 7bed7eb into openshift:master Jun 7, 2024
17 checks passed
@openshift-ci-robot
Copy link
Contributor

@arkadeepsen: Jira Issue OCPBUGS-34918: Some pull requests linked via external trackers have merged:

The following pull requests linked via external trackers have not merged:

These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

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

In response to this:

This PR uses build_root image from repository for coredns-ocp-dnsnamresolver.

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.

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/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. 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. rehearsals-ack Signifies that rehearsal jobs have been acknowledged
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants