Virtual machine launched using Azure Java SDK is not booting up if interfaces connected in dual stack network - IMDS server connection timing out in cloud-init script.
Query/Question VM is not booting up, as IMDS server connection timing out in cloud-init script. This issue happens when the node is deployed via Azure Java SDK with 2 network interfaces, both of them connected to a dual stack network.
Why is this not a Bug or a feature Request? Raising this issue here, based on the advice from Azure support team. This is not analysed from SDK POV to confirm if the issue is in SDK. Looks to be a bug but not sure if it could be in SDK, raising it as a query here because deploying the same image via Azure portal with single network interface in a dual stack subnet is working fine.
Setup (please complete the following information if applicable):
- OS: Application running in Linux
- IDE: NA
- Library/Libraries: Not specific to a library, issue is with virtual machine deployment.
Information Checklist Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report
- [x] Query Added
- [x] Setup information Added
Hi @mahudees. Thank you for opening this issue and giving us the opportunity to assist. To help our team better understand your issue and the details of your scenario please provide a response to the question asked above or the information requested above. This will help us more accurately address your issue.
Not specific to a library, issue is with virtual machine deployment.
Hi @mahudees we'll need more details about a specific SDK / callstack that you're having an issue with to provide help.
https://github.com/Azure/azure-sdk-for-java/blob/main/SUPPORT.md#azure-support-tickets
Please note that customers with an Azure support plan can open an Azure support ticket. We recommend this option if your problem requires immediate attention.
Hi @joshfree , I have opened a support ticket already, based on the advice from support team I have opened this issue here in github. Should I need to keep this open for debugging from SDK team as an additional option or I need to work through with support case. If needed, I can share the support case # here or via some private channel.
@mahudees does this issue still persist, if not could you close it?
Hi @mahudees. Thank you for opening this issue and giving us the opportunity to assist. To help our team better understand your issue and the details of your scenario please provide a response to the question asked above or the information requested above. This will help us more accurately address your issue.
Closing this as it started working now, with no changes from our end. We have also raised a support ticket with Azure, while they were analysing it, it started working suddenly. Hence, we closed the support case.