Skip to content

Comments

OCPBUGS-23399: Check if PER is enabled in the target PowerVS workspace#7736

Merged
openshift-merge-bot[bot] merged 2 commits intoopenshift:release-4.14from
miyamotoh:check-if-per-enabled-414
Dec 6, 2023
Merged

OCPBUGS-23399: Check if PER is enabled in the target PowerVS workspace#7736
openshift-merge-bot[bot] merged 2 commits intoopenshift:release-4.14from
miyamotoh:check-if-per-enabled-414

Conversation

@miyamotoh
Copy link
Contributor

@miyamotoh miyamotoh commented Nov 16, 2023

This is essentially a backport of #7683, but with additional code to check the customer-prepared Workspace is good, which 4.15 changes and stops allowing BYO Workspace for GA. Due to more cases to support in 4.14, a little more logic & tests are included in this PR.

Signed-off-by: Hiro Miyamoto <miyamotoh@us.ibm.com>
@openshift-ci openshift-ci bot requested review from bfournie and rna-afk November 16, 2023 21:27
@miyamotoh miyamotoh force-pushed the check-if-per-enabled-414 branch from da9892f to 0d8e0e6 Compare November 16, 2023 22:18
@miyamotoh miyamotoh changed the title Check if PER is enabled in the target PowerVS workspace OCPBUGS-23399: Check if PER is enabled in the target PowerVS workspace Nov 17, 2023
@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/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Nov 17, 2023
@openshift-ci-robot
Copy link
Contributor

@miyamotoh: This pull request references Jira Issue OCPBUGS-23399, which is invalid:

  • expected Jira Issue OCPBUGS-23399 to depend on a bug targeting a version in 4.15.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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.

Details

In response to this:

This is essentially a backport of #7683, but with additional code to check the customer-prepared Workspace is good, which 4.15 changes and stops allowing BYO Workspace for GA. Due to more cases to support in 4.14, a little more logic & tests are included in this PR.

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.

@miyamotoh
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@miyamotoh: This pull request references Jira Issue OCPBUGS-23399, which is invalid:

  • expected Jira Issue OCPBUGS-23399 to depend on a bug targeting a version in 4.15.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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.

Details

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 kubernetes/test-infra repository.

@mjturek
Copy link
Contributor

mjturek commented Nov 17, 2023

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@mjturek: This pull request references Jira Issue OCPBUGS-23399, which is invalid:

  • expected Jira Issue OCPBUGS-23399 to depend on a bug targeting a version in 4.15.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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.

Details

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 kubernetes/test-infra repository.

@mjturek
Copy link
Contributor

mjturek commented Nov 17, 2023

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@mjturek: This pull request references Jira Issue OCPBUGS-23399, which is invalid:

  • expected Jira Issue OCPBUGS-23399 to depend on a bug targeting a version in 4.15.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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.

Details

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 kubernetes/test-infra repository.

@mjturek
Copy link
Contributor

mjturek commented Nov 17, 2023

/jira refresh

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Nov 17, 2023

@mjturek: This pull request references Jira Issue OCPBUGS-23399, which is invalid:

  • bug is open, matching expected state (open)
  • bug target version (4.14.z) matches configured target version for branch (4.14.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • bug has dependents
  • dependent bug MULTIARCH-3965 is not in the required OCPBUGS project

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.

Details

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 kubernetes/test-infra repository.

Copy link
Member

Choose a reason for hiding this comment

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

here it says zone but the param name in the package definition says region, good have same name everywhere.

Copy link
Contributor

Choose a reason for hiding this comment

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

weird! PER enablement is zone specific so I'm a bit surprised at that. For example, dal12 does not currently support PER but dal10 does!

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah, the API says it's a region, but when I passed in dal, it didn't work, and I was told by the PowerVS team that I should pass in dal10 (which is a zone), instead. So, there's nothing we can do on our end.

@mjturek
Copy link
Contributor

mjturek commented Nov 28, 2023

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@mjturek: This pull request references Jira Issue OCPBUGS-23399, which is invalid:

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.

Details

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 kubernetes/test-infra repository.

@mjturek
Copy link
Contributor

mjturek commented Nov 28, 2023

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@mjturek: This pull request references Jira Issue OCPBUGS-23399, which is invalid:

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.

Details

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 kubernetes/test-infra repository.

@mjturek
Copy link
Contributor

mjturek commented Nov 28, 2023

/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 Nov 28, 2023
@openshift-ci-robot
Copy link
Contributor

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

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.14.z) matches configured target version for branch (4.14.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-24032 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-24032 targets the "4.15.0" version, which is one of the valid target versions: 4.15.0
  • bug has dependents

Requesting review from QA contact:
/cc @gpei

Details

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 kubernetes/test-infra repository.

@openshift-ci openshift-ci bot requested a review from gpei November 28, 2023 17:13
@mjturek
Copy link
Contributor

mjturek commented Nov 28, 2023

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 28, 2023
Copy link
Member

Choose a reason for hiding this comment

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

you can do this change to avoid confusion

Suggested change
func (c *Client) GetDatacenterCapabilities(ctx context.Context, region string) (map[string]bool, error) {
func (c *Client) GetDatacenterCapabilities(ctx context.Context, zone string) (map[string]bool, error) {

@mjturek
Copy link
Contributor

mjturek commented Nov 28, 2023

/remove-lgtm

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Nov 28, 2023
@miyamotoh miyamotoh force-pushed the check-if-per-enabled-414 branch from 0d8e0e6 to 8bb86c0 Compare November 29, 2023 02:20
@miyamotoh miyamotoh force-pushed the check-if-per-enabled-414 branch from 8bb86c0 to e91465d Compare November 29, 2023 13:30
Copy link
Contributor

Choose a reason for hiding this comment

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

This is 4.14 so serviceInstanceID is required.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good catch, addressed in the latest force-push, though go test doesn't fail either way.

@mjturek
Copy link
Contributor

mjturek commented Dec 1, 2023

Small change requested but otherwise LGTM

Signed-off-by: Hiro Miyamoto <miyamotoh@us.ibm.com>
@miyamotoh miyamotoh force-pushed the check-if-per-enabled-414 branch from e91465d to 9c7980b Compare December 1, 2023 18:50
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 1, 2023

@miyamotoh: 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/prow/okd-scos-e2e-gcp-ovn-upgrade 9c7980b link false /test okd-scos-e2e-gcp-ovn-upgrade
ci/prow/okd-scos-e2e-vsphere 9c7980b link false /test okd-scos-e2e-vsphere
ci/prow/e2e-openstack-nfv-intel 9c7980b link false /test e2e-openstack-nfv-intel
ci/prow/okd-scos-e2e-gcp 9c7980b link false /test okd-scos-e2e-gcp
ci/prow/okd-scos-e2e-aws-ovn 9c7980b link false /test okd-scos-e2e-aws-ovn

Full PR test history. Your PR dashboard.

Details

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.

@mjturek
Copy link
Contributor

mjturek commented Dec 2, 2023

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 2, 2023
@mjturek
Copy link
Contributor

mjturek commented Dec 2, 2023

/retest-required

@miyamotoh
Copy link
Contributor Author

@sadasu PTAL and approve.

@sadasu
Copy link
Contributor

sadasu commented Dec 5, 2023

/approve

@sadasu
Copy link
Contributor

sadasu commented Dec 5, 2023

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Dec 5, 2023
@sadasu
Copy link
Contributor

sadasu commented Dec 5, 2023

@gpei Could you PTAL? This also needs the cherry-pick-approved label.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 5, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sadasu

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

The pull request process is described here

Details 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 Dec 5, 2023
@gpei
Copy link
Contributor

gpei commented Dec 6, 2023

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Dec 6, 2023
@openshift-merge-bot openshift-merge-bot bot merged commit 143dda3 into openshift:release-4.14 Dec 6, 2023
@openshift-ci-robot
Copy link
Contributor

@miyamotoh: Jira Issue OCPBUGS-23399: All pull requests linked via external trackers have merged:

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

Details

In response to this:

This is essentially a backport of #7683, but with additional code to check the customer-prepared Workspace is good, which 4.15 changes and stops allowing BYO Workspace for GA. Due to more cases to support in 4.14, a little more logic & tests are included in this PR.

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.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-installer-container-v4.14.0-202312060110.p0.g143dda3.assembly.stream for distgit ose-installer.
All builds following this will include this PR.

@openshift-merge-robot
Copy link
Contributor

Fix included in accepted release 4.14.0-0.nightly-2023-12-06-070113

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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.

8 participants