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.

Sign up for GitHub

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

Jump to bottom

[release-4.15] OCPBUGS-32160: chore: expose allocation settings #59

Merged
merged 1 commit into from
Apr 15, 2024
Merged

[release-4.15] OCPBUGS-32160: chore: expose allocation settings #59

merged 1 commit into from
Apr 15, 2024

Conversation

jakobmoellerdev
Copy link

(cherry picked from commit 940a3e1, 3f8fab9 and a967c95)

Note that this is a single cherry pick commit that also has manual adjustments to make the go.mod modification as minimal as possible.

@jakobmoellerdev
chore: expose allocation settings
5240445 
Signed-off-by: Jakob Möller <jmoller@redhat.com>

(cherry picked from commit 940a3e1)
Signed-off-by: Jakob Möller <jmoller@redhat.com>
@openshift-ci-robot
Copy link

@jakobmoellerdev: An error was encountered searching for dependent bug OCPBUGS-30266 for bug OCPBUGS-32160 on the Jira server at https://issues.redhat.com/. No known errors were detected, please see the full error message for details.

Full error message. No response returned: Get "https://issues.redhat.com/rest/api/2/issue/OCPBUGS-30266": GET https://issues.redhat.com/rest/api/2/issue/OCPBUGS-30266 giving up after 5 attempt(s)

Please contact an administrator to resolve this issue, then request a bug refresh with /jira refresh.

In response to this:

(cherry picked from commit 940a3e1, 3f8fab9 and a967c95)

Note that this is a single cherry pick commit that also has manual adjustments to make the go.mod modification as minimal as possible.

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.

@jakobmoellerdev
Copy link
Author

/jira refresh

@openshift-ci-robot
Copy link

@jakobmoellerdev: An error was encountered searching for dependent bug OCPBUGS-30266 for bug OCPBUGS-32160 on the Jira server at https://issues.redhat.com/. No known errors were detected, please see the full error message for details.

Full error message. No response returned: Get "https://issues.redhat.com/rest/api/2/issue/OCPBUGS-30266": GET https://issues.redhat.com/rest/api/2/issue/OCPBUGS-30266 giving up after 5 attempt(s)

Please contact an administrator to resolve this issue, then request a bug refresh with /jira refresh.

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.

@jakobmoellerdev
Copy link
Author

/jira refresh

@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 Apr 12, 2024
@openshift-ci-robot
Copy link

@jakobmoellerdev: This pull request references Jira Issue OCPBUGS-32160, which is invalid:

  • expected dependent Jira Issue OCPBUGS-30266 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED instead

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:

/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.

@jakobmoellerdev jakobmoellerdev changed the title OCPBUGS-32160: chore: expose allocation settings [release-4.15] OCPBUGS-32160: chore: expose allocation settings Apr 12, 2024
@jakobmoellerdev
Copy link
Author

/jira refresh

@openshift-ci-robot
Copy link

@jakobmoellerdev: This pull request references Jira Issue OCPBUGS-32160, which is invalid:

  • expected dependent Jira Issue OCPBUGS-30266 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED instead

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:

/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.

@jakobmoellerdev
Copy link
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 Apr 15, 2024
@openshift-ci-robot
Copy link

@jakobmoellerdev: This pull request references Jira Issue OCPBUGS-32160, which is valid.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.15.z) matches configured target version for branch (4.15.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-30266 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-30266 targets the "4.16.0" version, which is one of the valid target versions: 4.16.0
  • bug has dependents

Requesting review from QA contact:
/cc @radeore

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.

@openshift-ci openshift-ci bot requested a review from radeore April 15, 2024 09:28
@jeff-roche
Copy link

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 15, 2024
@jeff-roche
Copy link

/approve

@jakobmoellerdev jakobmoellerdev merged commit 1c93a55 into openshift:release-4.15 Apr 15, 2024
@openshift-ci-robot
Copy link

@jakobmoellerdev: Jira Issue OCPBUGS-32160: All pull requests linked via external trackers have merged:

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

In response to this:

(cherry picked from commit 940a3e1, 3f8fab9 and a967c95)

Note that this is a single cherry pick commit that also has manual adjustments to make the go.mod modification as minimal as possible.

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
Reviewers

@radeore radeore Awaiting requested review from radeore

Assignees

@jeff-roche jeff-roche

Labels
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
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
3 participants
@jakobmoellerdev @openshift-ci-robot @jeff-roche