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

feat: support RHEL 9 on s390x architecture #290

Merged

Conversation

nestoracunablanco
Copy link
Contributor

What this PR does / why we need it: s390x enablement

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Release note:

NONE

Signed-off-by: Nestor Acuna Blanco <nestor.acuna@ibm.com>
@kubevirt-bot kubevirt-bot added release-note-none Denotes a PR that doesn't merit a release note. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. labels Nov 21, 2024
@nestoracunablanco
Copy link
Contributor Author

/retest

1 similar comment
@nestoracunablanco
Copy link
Contributor Author

/retest

@nestoracunablanco
Copy link
Contributor Author

/test kubevirt-functest-centos-stream-arm64

@kubevirt-bot
Copy link
Contributor

@nestoracunablanco: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

  • /test pull-build-common-instancetypes-builder
  • /test pull-common-instancetypes
  • /test pull-common-instancetypes-kubevirt-functest
  • /test pull-common-instancetypes-kubevirt-functest-centos-7
  • /test pull-common-instancetypes-kubevirt-functest-centos-stream-8
  • /test pull-common-instancetypes-kubevirt-functest-centos-stream-9
  • /test pull-common-instancetypes-kubevirt-functest-fedora
  • /test pull-common-instancetypes-kubevirt-functest-opensuse-leap
  • /test pull-common-instancetypes-kubevirt-functest-opensuse-tumbleweed
  • /test pull-common-instancetypes-kubevirt-functest-ubuntu
  • /test pull-common-instancetypes-kubevirt-functest-validation-os

The following commands are available to trigger optional jobs:

  • /test pull-common-instancetypes-kubevirt-functest-centos-stream-arm64
  • /test pull-common-instancetypes-kubevirt-functest-fedora-arm64
  • /test pull-common-instancetypes-kubevirt-functest-opensuse-leap-arm64
  • /test pull-common-instancetypes-kubevirt-functest-ubuntu-arm64

Use /test all to run the following jobs that were automatically triggered:

  • pull-common-instancetypes
  • pull-common-instancetypes-kubevirt-functest
  • pull-common-instancetypes-kubevirt-functest-centos-7
  • pull-common-instancetypes-kubevirt-functest-centos-stream-8
  • pull-common-instancetypes-kubevirt-functest-centos-stream-9
  • pull-common-instancetypes-kubevirt-functest-centos-stream-arm64
  • pull-common-instancetypes-kubevirt-functest-fedora
  • pull-common-instancetypes-kubevirt-functest-fedora-arm64
  • pull-common-instancetypes-kubevirt-functest-opensuse-leap
  • pull-common-instancetypes-kubevirt-functest-opensuse-leap-arm64
  • pull-common-instancetypes-kubevirt-functest-opensuse-tumbleweed
  • pull-common-instancetypes-kubevirt-functest-ubuntu
  • pull-common-instancetypes-kubevirt-functest-ubuntu-arm64
  • pull-common-instancetypes-kubevirt-functest-validation-os

In response to this:

/test kubevirt-functest-centos-stream-arm64

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.

@nestoracunablanco
Copy link
Contributor Author

/test pull-common-instancetypes-kubevirt-functest-centos-stream-arm64

@jcanocan
Copy link
Contributor

Thanks!
/lgtm

@kubevirt-bot kubevirt-bot added the lgtm Indicates that a PR is ready to be merged. label Nov 22, 2024
@lyarwood
Copy link
Member

/approve

@kubevirt-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lyarwood

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

@kubevirt-bot kubevirt-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 22, 2024
@kubevirt-bot kubevirt-bot merged commit 2eea4e7 into kubevirt:main Nov 22, 2024
12 of 16 checks passed
@nestoracunablanco nestoracunablanco deleted the feat/rhel9s390xEnablement branch November 22, 2024 17:05
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. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. size/M
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants