-
Notifications
You must be signed in to change notification settings - Fork 247
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
Support Azure generation 2 VMs #1194
Labels
Comments
sohankunkerkar
added a commit
to sohankunkerkar/ignition
that referenced
this issue
Jun 21, 2021
sohankunkerkar
added a commit
to sohankunkerkar/ignition
that referenced
this issue
Jun 21, 2021
sohankunkerkar
added a commit
to sohankunkerkar/ignition
that referenced
this issue
Jun 22, 2021
sohankunkerkar
added a commit
to sohankunkerkar/ignition
that referenced
this issue
Jun 25, 2021
sohankunkerkar
added a commit
to sohankunkerkar/ignition
that referenced
this issue
Jun 25, 2021
sohankunkerkar
added a commit
to sohankunkerkar/ignition
that referenced
this issue
Jun 25, 2021
sohankunkerkar
added a commit
to sohankunkerkar/ignition
that referenced
this issue
Jun 25, 2021
sohankunkerkar
added a commit
to sohankunkerkar/ignition
that referenced
this issue
Jun 25, 2021
sohankunkerkar
added a commit
to sohankunkerkar/ignition
that referenced
this issue
Jun 25, 2021
sohankunkerkar
added a commit
to sohankunkerkar/ignition
that referenced
this issue
Jun 25, 2021
sohankunkerkar
added a commit
to sohankunkerkar/ignition
that referenced
this issue
Jun 25, 2021
sohankunkerkar
added a commit
to sohankunkerkar/ignition
that referenced
this issue
Jun 25, 2021
sohankunkerkar
added a commit
to sohankunkerkar/ignition
that referenced
this issue
Jun 25, 2021
sohankunkerkar
added a commit
to sohankunkerkar/ignition
that referenced
this issue
Jun 25, 2021
sohankunkerkar
added a commit
to sohankunkerkar/ignition
that referenced
this issue
Jun 26, 2021
sohankunkerkar
added a commit
to sohankunkerkar/ignition
that referenced
this issue
Jun 30, 2021
sohankunkerkar
added a commit
to sohankunkerkar/ignition
that referenced
this issue
Jun 30, 2021
sohankunkerkar
added a commit
to sohankunkerkar/ignition
that referenced
this issue
Jun 30, 2021
sohankunkerkar
added a commit
to sohankunkerkar/ignition
that referenced
this issue
Jun 30, 2021
sohankunkerkar
added a commit
to sohankunkerkar/ignition
that referenced
this issue
Jul 1, 2021
sohankunkerkar
added a commit
to sohankunkerkar/ignition
that referenced
this issue
Jul 8, 2021
sohankunkerkar
added a commit
to sohankunkerkar/ignition
that referenced
this issue
Jul 9, 2021
sohankunkerkar
added a commit
to sohankunkerkar/ignition
that referenced
this issue
Jul 9, 2021
sohankunkerkar
added a commit
to sohankunkerkar/ignition
that referenced
this issue
Jul 9, 2021
sohankunkerkar
added a commit
to sohankunkerkar/ignition
that referenced
this issue
Jul 9, 2021
sohankunkerkar
added a commit
to sohankunkerkar/ignition
that referenced
this issue
Jul 9, 2021
sohankunkerkar
added a commit
to sohankunkerkar/ignition
that referenced
this issue
Jul 13, 2021
Fixes coreos#1194 This change uses the same path for gen1 and gen2 VMs because they can't easily be distinguished at runtime.
sohankunkerkar
added a commit
to sohankunkerkar/ignition
that referenced
this issue
Jul 13, 2021
Fixes coreos#1194 This change uses the same path for gen1 and gen2 VMs because they can't easily be distinguished at runtime.
sohankunkerkar
added a commit
to sohankunkerkar/ignition
that referenced
this issue
Jul 13, 2021
Fixes coreos#1194 This change uses the same path for gen1 and gen2 VMs because they can't easily be distinguished at runtime.
sohankunkerkar
added a commit
to sohankunkerkar/ignition
that referenced
this issue
Jul 13, 2021
Fixes coreos#1194 This change uses the same path for gen1 and gen2 VMs because they can't easily be distinguished at runtime.
sohankunkerkar
added a commit
to sohankunkerkar/ignition
that referenced
this issue
Jul 13, 2021
Fixes coreos#1194 This change uses the same path for gen1 and gen2 VMs because they can't easily be distinguished at runtime.
sohankunkerkar
added a commit
to sohankunkerkar/ignition
that referenced
this issue
Jul 13, 2021
Fixes coreos#1194 This change uses the same path for gen1 and gen2 VMs because they can't easily be distinguished at runtime.
sohankunkerkar
added a commit
to sohankunkerkar/ignition
that referenced
this issue
Jul 13, 2021
Fixes coreos#1194 This change uses the same path for gen1 and gen2 VMs because they can't easily be distinguished at runtime.
sohankunkerkar
added a commit
to sohankunkerkar/ignition
that referenced
this issue
Jul 13, 2021
Fixes coreos#1194 This change uses the same path for gen1 and gen2 VMs because they can't easily be distinguished at runtime.
sohankunkerkar
added a commit
to sohankunkerkar/ignition
that referenced
this issue
Jul 15, 2021
Fixes coreos#1194 This change uses the same path for gen1 and gen2 VMs because they can't easily be distinguished at runtime.
sohankunkerkar
added a commit
to sohankunkerkar/ignition
that referenced
this issue
Jul 15, 2021
Fixes coreos#1194 This change uses the same path for gen1 and gen2 VMs because they can't easily be distinguished at runtime.
sohankunkerkar
added a commit
to sohankunkerkar/ignition
that referenced
this issue
Jul 15, 2021
Fixes coreos#1194 This change uses the same devicepath for gen1 and gen2 VMs because they can't easily be distinguished at runtime.
sohankunkerkar
added a commit
to sohankunkerkar/ignition
that referenced
this issue
Jul 22, 2021
Fixes coreos#1194 This change uses the same devicepath for gen1 and gen2 VMs because they can't easily be distinguished at runtime.
sohankunkerkar
added a commit
to sohankunkerkar/ignition
that referenced
this issue
Jul 23, 2021
Fixes coreos#1194 This change uses the same devicepath for gen1 and gen2 VMs because they can't easily be distinguished at runtime.
sohankunkerkar
added a commit
to sohankunkerkar/ignition
that referenced
this issue
Jul 23, 2021
Fixes coreos#1194 This change uses the same devicepath for gen1 and gen2 VMs because they can't easily be distinguished at runtime.
sohankunkerkar
added a commit
to sohankunkerkar/ignition
that referenced
this issue
Jul 23, 2021
Fixes coreos#1194 This change uses the same devicepath for gen1 and gen2 VMs because they can't easily be distinguished at runtime.
sohankunkerkar
added a commit
to sohankunkerkar/ignition
that referenced
this issue
Jul 28, 2021
Fixes coreos#1194 This change uses the same devicepath for gen1 and gen2 VMs because they can't easily be distinguished at runtime.
jepio
pushed a commit
to flatcar/ignition
that referenced
this issue
Aug 17, 2021
Fixes coreos/ignition#1194 This change uses the same devicepath for gen1 and gen2 VMs because they can't easily be distinguished at runtime. Signed-off-by: Jeremi Piotrowski <jpiotrowski@microsoft.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature Request
Environment
Azure
Desired Feature
Support Azure generation 2 VMs.
Other Information
When booting an Azure image on gen2, Ignition 2.9.0 loops infinitely looking for the OVF device:
The text was updated successfully, but these errors were encountered: