image-builder
image-builder copied to clipboard
kubernetes-sigs
Added qemu image support for opensuse 15.3 Cloud image
What this PR does / why we need it: Adds support for building CAPI qemu/qcow2 images based of openSuse 15.3 cloud init JeOS images - https://en.opensuse.org/Portal:JeOS .
Which issue(s) this PR fixes (optional, in fixes #
Additional context Base image is provisioned with a cloud init script to bootstrap the initial user for ansible to execute all the image building tasks. The rpm repos providing kubelet,kubeadm etc work directly with zypper. however some of the dependencies specifically conntrack isnt recognized by zypper even after installing it from suse repos. For this reason the kubelet and other rpms are downloaded from the repos and installed manually.
Hi @venkatnsrinivasan. Thanks for your PR.
I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.
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.
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: davidjumani, venkatnsrinivasan
To complete the pull request process, please assign enxebre after the PR has been reviewed.
You can assign the PR to them by writing /assign @enxebre in a comment when ready.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
@venkatnsrinivasan: 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 |
|---|---|---|---|---|
| json-sort-check | 8dfaf56eaf50364e43a7b2a356f1ca2e0345465a | link | true | /test json-sort-check |
| pull-packer-validate | 8dfaf56eaf50364e43a7b2a356f1ca2e0345465a | link | true | /test pull-packer-validate |
| pull-ova-all | 8dfaf56eaf50364e43a7b2a356f1ca2e0345465a | link | true | /test pull-ova-all |
| pull-azure-sigs | 8dfaf56eaf50364e43a7b2a356f1ca2e0345465a | link | false | /test pull-azure-sigs |
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your 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. I understand the commands that are listed here.
@venkatnsrinivasan: PR needs rebase.
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.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale - Mark this issue or PR as rotten with
/lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
Closing the PR since there has been no activity in 5 months. Please re-open when you work on it.
