-
Notifications
You must be signed in to change notification settings - Fork 1.5k
azure: create bootimages using image gallery #6304
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
azure: create bootimages using image gallery #6304
Conversation
fc69cc7 to
6960917
Compare
|
/test e2e-azure |
|
/cc @r4f4 |
patrickdillon
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In general this looks good. I can see that you're working through some errors in CI. The issue is not obvious, so feel free to provide an update or reach out if you want to discuss what's going on there.
I left a comment about setting the version. I think this is preferable, but I would not say i is a hard requirement. We can discuss this idea further. The first suggestion, in terms of piping the release through the codebase may be preferable to parsing the url, but may also be a bit more hairy to implement.
yes the CI results concern me a bit..the current run seems to be progressing fine but the failure was essentially: so the flow here is image gallery -> image definition(inside the gallery) -> image version (inside the image definition). the error above indicates that the image gallery could not be found, but in the previous few lines i see: so from a timeline perspective it seems ok. I'm still wondering if we need these resources to each have a |
6960917 to
d273965
Compare
This error is an example of a common class of errors we see in the upstream terraform providers. The terraform providers should handle these dependencies, but frequently there are bugs. We've had two similar bugs reported in the past week. Adding a Digging into the upstream code: the creation of the image gallery is here: and the image itself is here: |
d273965 to
0b3e91e
Compare
|
/retest-required |
|
/test e2e-azure-shared-vpc |
|
/test e2e-azure-shared-vpc |
|
/test e2e-azure-shared-vpc |
33c21ae to
f344b5b
Compare
f72486c to
a333b21
Compare
|
/test e2e-azure-ovn-resourcegroup |
a333b21 to
9e8fbf0
Compare
0a8560a to
553d13e
Compare
|
/override ci/prow/e2e-aws-ovn |
|
@patrickdillon: Overrode contexts on behalf of patrickdillon: ci/prow/e2e-aws-ovn DetailsIn response to this:
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. |
|
/override ci/prow/e2e-vsphere-ovn |
|
/override ci/prow/e2e-gcp-ovn |
|
@r4f4: Overrode contexts on behalf of r4f4: ci/prow/e2e-vsphere-ovn DetailsIn response to this:
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. |
|
@r4f4: Overrode contexts on behalf of r4f4: ci/prow/e2e-gcp-ovn DetailsIn response to this:
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. |
|
/override ci/prow/e2e-azure-ovn |
|
@r4f4: Overrode contexts on behalf of r4f4: ci/prow/e2e-azure-ovn DetailsIn response to this:
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. |
|
/override ci/prow/e2e-gcp-ovn |
|
@r4f4: Overrode contexts on behalf of r4f4: ci/prow/e2e-gcp-ovn DetailsIn response to this:
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. |
|
/hold Revision 7994d1c was retested 3 times: holding |
|
/skip |
|
/hold cancel |
|
/skip |
|
/override ci/prow/e2e-aws-ovn ci/prow/okd-scos-images ci/prow/okd-scos-unit ci/prow/okd-scos-verify-codegen ci/prow/e2e-agent-compact |
|
@r4f4: Overrode contexts on behalf of r4f4: ci/prow/e2e-agent-compact, ci/prow/e2e-aws-ovn, ci/prow/okd-scos-images, ci/prow/okd-scos-unit, ci/prow/okd-scos-verify-codegen DetailsIn response to this:
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. |
|
@Prashanth684: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
…resscontroller With the bootimage creation for Azure changing from managed images to image gallery with this installer PR: openshift/installer#6304, it is better to infer the image id path from existing machines as it has a version and gallery name which are not easy to derive.
…resscontroller (#33067) With the bootimage creation for Azure changing from managed images to image gallery with this installer PR: openshift/installer#6304, it is better to infer the image id path from existing machines as it has a version and gallery name which are not easy to derive.
In order to support provisioning of arm64 bootimages, these need to be
created using the image gallery resource as they are not supported
through managed images. For this purpose, it would be good to unify the
implementation of x86 and arm64 to use image galleries as Microsoft have
said that it will be the supported way of creating bootimages going forward
for new instance types of new architectures.
This implementation would create one image gallery with two images: a
gen1 and a gen2 image which we would then pick appropriately based on
the VM generation.
xref: https://issues.redhat.com/browse/ARMOCP-16