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-28203: Power VS: Add sleep to allow workspace to configure PER #7889

Merged
merged 1 commit into from Feb 14, 2024

Conversation

mjturek
Copy link
Contributor

@mjturek mjturek commented Jan 9, 2024

No description provided.

@openshift-ci openshift-ci bot requested review from barbacbd and r4f4 January 9, 2024 19:05
Copy link
Contributor

@barbacbd barbacbd left a comment

Choose a reason for hiding this comment

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

There may be a default value, but is there any point in having these input variables to terraform if the installer doesn't supply the data?

pkg/tfvars/powervs/powervs.go

@mjturek
Copy link
Contributor Author

mjturek commented Jan 10, 2024

There may be a default value, but is there any point in having these input variables to terraform if the installer doesn't supply the data?

pkg/tfvars/powervs/powervs.go

Mostly for consistency. We generally try not to keep values in variables for our terraform (though there are probably cases where we broke this convention). Making it configurable in the future would also be easier.

@mjturek mjturek changed the title Power VS: Add sleep to allow workspace to configure PER OCPBUGS-28203: Power VS: Add sleep to allow workspace to configure PER Jan 25, 2024
@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. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Jan 25, 2024
@openshift-ci-robot
Copy link
Contributor

@mjturek: This pull request references Jira Issue OCPBUGS-28203, 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 New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @gpei

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

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

@openshift-ci openshift-ci bot requested a review from gpei January 25, 2024 15:06
@miyamotoh
Copy link
Contributor

/lgtm
as long as this is verified working in most, if not all, regions we support.

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

@r4f4 r4f4 left a comment

Choose a reason for hiding this comment

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

/approve

@r4f4
Copy link
Contributor

r4f4 commented Feb 14, 2024

/approve

Copy link
Contributor

openshift-ci bot commented Feb 14, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: r4f4

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

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

openshift-ci bot commented Feb 14, 2024

@mjturek: all tests passed!

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.

@openshift-merge-bot openshift-merge-bot bot merged commit 73b5742 into openshift:master Feb 14, 2024
21 checks passed
@openshift-ci-robot
Copy link
Contributor

@mjturek: Jira Issue OCPBUGS-28203: All pull requests linked via external trackers have merged:

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

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

@openshift-merge-robot
Copy link
Contributor

Fix included in accepted release 4.16.0-0.nightly-2024-02-17-013806

@mjturek
Copy link
Contributor Author

mjturek commented Feb 21, 2024

/cherrypick release-4.15

@openshift-cherrypick-robot

@mjturek: new pull request created: #8052

In response to this:

/cherrypick 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/severity-moderate Referenced Jira bug's severity is moderate 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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants