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

wrap s3 benchmark-tool - ns in hostname fixed #11104

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

DanielOsypenko
Copy link
Contributor

The hostname for wrap s3 benchmark-tool is now dynamic, tuned to a storage namespace.

test run Pass: https://url.corp.redhat.com/218b7dc

Signed-off-by: Daniel Osypenko <[email protected]>
sagihirshfeld
sagihirshfeld previously approved these changes Jan 6, 2025
Copy link
Contributor

@sagihirshfeld sagihirshfeld left a comment

Choose a reason for hiding this comment

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

LGTM

Comment on lines 40 to 42
# avoid failing DNS server to resolve hostname, when running on cluster with custom storage namespace
if config.ENV_DATA["cluster_namespace"] not in self.host:
self.host = f"s3.{config.ENV_DATA['cluster_namespace']}.svc"
Copy link
Contributor

Choose a reason for hiding this comment

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

Please remove the condition and change line 39 to self.host = f"s3.{config.ENV_DATA['cluster_namespace']}.svc"

@openshift-ci openshift-ci bot removed the lgtm label Jan 6, 2025
Signed-off-by: Daniel Osypenko <[email protected]>
@openshift-ci openshift-ci bot added the lgtm label Jan 6, 2025
@DanielOsypenko DanielOsypenko added the Verified Mark when PR was verified and log provided label Jan 6, 2025
@DanielOsypenko
Copy link
Contributor Author

/cherry-pick release-4.17

@openshift-cherrypick-robot
Copy link
Collaborator

@DanielOsypenko: once the present PR merges, I will cherry-pick it on top of release-4.17 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.17

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.

@DanielOsypenko
Copy link
Contributor Author

/cherry-pick release-4.16

@openshift-cherrypick-robot
Copy link
Collaborator

@DanielOsypenko: once the present PR merges, I will cherry-pick it on top of release-4.16 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.16

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.

@DanielOsypenko
Copy link
Contributor Author

/cherry-pick release-4.15

@openshift-cherrypick-robot
Copy link
Collaborator

@DanielOsypenko: once the present PR merges, I will cherry-pick it on top of release-4.15 in a new PR and assign it to you.

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-sigs/prow repository.

Copy link

openshift-ci bot commented Jan 6, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: DanielOsypenko, sagihirshfeld, udaysk23

The full list of commands accepted by this bot can be found 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

@DanielOsypenko DanielOsypenko changed the title ns in hostname fixed wrap s3 benchmark-tool - ns in hostname fixed Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm size/XS TestCase failing Verified Mark when PR was verified and log provided
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants