Skip to content

fix AMI query for Ubuntu images #1927

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
Merged
merged 1 commit into from
Jun 9, 2025
Merged

fix AMI query for Ubuntu images #1927

merged 1 commit into from
Jun 9, 2025

Conversation

xrstf
Copy link
Contributor

@xrstf xrstf commented Jun 5, 2025

What this PR does / why we need it:
The old query does not yield any results anymore. With the new one, the following AMI is currently chosen:

  • id=ami-0300b7cf57a2ea956,
  • owner=679593333241
  • ubuntu/images/hvm-ssd-gp3/ubuntu-noble-24.04-amd64-server-20250530-prod-ib2w5aw4ynhey

What type of PR is this?
/kind chore

Does this PR introduce a user-facing change? Then add your Release Note here:

Fix AMI query for Ubuntu images

Documentation:

NONE

@kubermatic-bot kubermatic-bot added kind/chore Updating grunt tasks etc; no production code changes. release-note Denotes a PR that will be considered when it comes time to generate release notes. docs/none Denotes a PR that doesn't need documentation (changes). 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 Jun 5, 2025
@xrstf
Copy link
Contributor Author

xrstf commented Jun 5, 2025

/retest

@mohamed-rafraf
Copy link
Member

/approve
/lgtm

@kubermatic-bot kubermatic-bot added the lgtm Indicates that a PR is ready to be merged. label Jun 9, 2025
@kubermatic-bot
Copy link
Contributor

LGTM label has been added.

Git tree hash: 838d81055ce8ed07c179ee895b5827e065dac41e

@kubermatic-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mohamed-rafraf

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

@kubermatic-bot kubermatic-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 9, 2025
@kubermatic-bot kubermatic-bot merged commit bab47c4 into kubermatic:main Jun 9, 2025
12 checks passed
@xrstf
Copy link
Contributor Author

xrstf commented Jun 10, 2025

/cherrypick release/v1.61

@xrstf
Copy link
Contributor Author

xrstf commented Jun 10, 2025

/cherrypick release/v1.60

@xrstf xrstf deleted the fix-ami-filter branch June 10, 2025 12:21
@kubermatic-bot
Copy link
Contributor

@xrstf: new pull request created: #1928

In response to this:

/cherrypick release/v1.61

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.

@kubermatic-bot
Copy link
Contributor

@xrstf: new pull request created: #1929

In response to this:

/cherrypick release/v1.60

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.

This was referenced Jun 10, 2025
Merged
Merged
@toschneck
Copy link
Member

@xrstf I saw I think the same issue also with AWS at KKP 2.27.5. Will the fix be land there as well?
Machine Deployment 'ubuntu' in Cluster 'aws-demo-app-cluster' in Project 'Demo Project 🚀' 2025-06-12 09-38-31

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@mohamed-rafraf mohamed-rafraf

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. docs/none Denotes a PR that doesn't need documentation (changes). kind/chore Updating grunt tasks etc; no production code changes. 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

@xrstf @mohamed-rafraf @kubermatic-bot @toschneck