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/v1.58] AWS: Increase HttpPutResponseHopLimit to 3 for EC2 instances #1835

Merged
merged 1 commit into from
Aug 1, 2024
Merged

[release/v1.58] AWS: Increase HttpPutResponseHopLimit to 3 for EC2 instances #1835

merged 1 commit into from
Aug 1, 2024

Conversation

kubermatic-bot
Copy link
Contributor

This is an automated cherry-pick of #1833

/assign xrstf

AWS: Increase HttpPutResponseHopLimit to 3 for EC2 instances

@kubermatic-bot kubermatic-bot mentioned this pull request Jul 31, 2024
Merged
@kubermatic-bot kubermatic-bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jul 31, 2024
@xrstf
Copy link
Contributor

xrstf commented Jul 31, 2024

/approve
/lgtm

@kubermatic-bot kubermatic-bot added the lgtm Indicates that a PR is ready to be merged. label Jul 31, 2024
@kubermatic-bot
Copy link
Contributor Author

LGTM label has been added.

Git tree hash: baa4de2ae95ada4f53dccd0b51bee638cccf0860

@kubermatic-bot kubermatic-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 31, 2024
@xrstf
Copy link
Contributor

xrstf commented Jul 31, 2024

/retest

@kubermatic-triage-bot
Copy link

/retest
This bot automatically retries jobs that failed/flaked on approved PRs

Review the full test history

Silence the bot with an /lgtm cancel or /hold comment for consistent failures.

3 similar comments
@kubermatic-triage-bot
Copy link

/retest
This bot automatically retries jobs that failed/flaked on approved PRs

Review the full test history

Silence the bot with an /lgtm cancel or /hold comment for consistent failures.

@kubermatic-triage-bot
Copy link

/retest
This bot automatically retries jobs that failed/flaked on approved PRs

Review the full test history

Silence the bot with an /lgtm cancel or /hold comment for consistent failures.

@kubermatic-triage-bot
Copy link

/retest
This bot automatically retries jobs that failed/flaked on approved PRs

Review the full test history

Silence the bot with an /lgtm cancel or /hold comment for consistent failures.

ahmedwaleedmalik
ahmedwaleedmalik approved these changes Aug 1, 2024
View reviewed changes
Copy link
Member

@ahmedwaleedmalik ahmedwaleedmalik left a comment

Choose a reason for hiding this comment

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

/approve
/hold

centos is failing since it's dead @xrstf you can override and remove hold

@kubermatic-bot kubermatic-bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 1, 2024
@kubermatic-bot
Copy link
Contributor Author

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ahmedwaleedmalik, xrstf

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:
  • OWNERS [ahmedwaleedmalik,xrstf]

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

@xrstf
Copy link
Contributor

xrstf commented Aug 1, 2024

/override pull-machine-controller-e2e-aws

CentOS not working anymore.

@kubermatic-bot
Copy link
Contributor Author

@xrstf: Overrode contexts on behalf of xrstf: pull-machine-controller-e2e-aws

In response to this:

/override pull-machine-controller-e2e-aws

CentOS not working anymore.

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.

@xrstf
Copy link
Contributor

xrstf commented Aug 1, 2024

/unhold

@kubermatic-bot kubermatic-bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 1, 2024
@kubermatic-bot kubermatic-bot merged commit b63acc6 into kubermatic:release/v1.58 Aug 1, 2024
16 checks passed
@kubermatic-bot kubermatic-bot deleted the cherry-pick-1833-to-release/v1.58 branch August 1, 2024 09:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@ahmedwaleedmalik ahmedwaleedmalik ahmedwaleedmalik approved these changes

Assignees

@xrstf xrstf

@ahmedwaleedmalik ahmedwaleedmalik

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@kubermatic-bot @xrstf @kubermatic-triage-bot @ahmedwaleedmalik