You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to setup FCOS Stable v 40.20240504.3.0 on Azure vm with ignition file. However, it always end with provisioning timeout.
I have try this same ignition file on both VM and GCP. Both are working as expected but not on Azure.
Reproduction steps
Create image from vhd file with Linux V2 type.
Using the created image to create a VM.
Copyignition file to "custom-data" field.
Create a VM.
Expected behavior
A FCOS VM with custom setup specify in ignition file.
Actual behavior
Deployment failed with provisioning timeout error which copied below.
{
"code": "OSProvisioningTimedOut",
"message": "OS Provisioning for VM 'testvm02' did not finish in the allotted time.
If you are deploying more than 20 Virtual Machines concurrently, consider moving your custom image to shared image gallery. Please refer to https://aka.ms/movetosig for the same."
}
System details
Azure VM
Standard B2las V2 ( 2 CPU / 4 GB RAM ) x64
32 GB SSD ( P4 )
Butane or Ignition config
# This is a shortened file which also failed to provisionvariant: fcosversion: 1.5.0passwd:
users:
# For Admin Taks
- name: sysadminpassword_hash: SOMEPASSHASHssh_authorized_keys:
- ssh-ed25519 RANDOM USER@HOSTgroups:
- sudo
- wheel# For Running/App Task
- name: sysdeploypassword_hash: SOMEHASHssh_authorized_keys:
- ssh-ed25519 RANDOM USER@HOSTstorage:
directories:
- path: /root/config
- path: /home/sysdeploy/.configmode: 0755user:
name: sysdeploygroup:
name: sysdeploy
- path: /home/sysdeploy/.config/containersmode: 0755user:
name: sysdeploygroup:
name: sysdeploy
- path: /home/sysdeploy/.config/containers/systemdmode: 0755user:
name: sysdeploygroup:
name: sysdeployfiles:
- path: /etc/hostnamemode: 0644contents:
inline: testvm03
- path: /etc/zincati/config.d/51-rollout-wariness.tomlcontents:
inline: | [identity] # Between 0 (eager) < x < 1 (cautious) rollout_wariness = 0.5
- path: /etc/zincati/config.d/55-updates-strategy.tomlcontents:
inline: | [updates] strategy = "periodic" [[updates.periodic.window]] days = [ "Wed" ] start_time = "01:30" length_minutes = 60
Additional information
However, if I create a VM with the same image but without ignition file then the deployment is successful, and everything works.
If my English is too confusing please ask I will try to provide more information.
The text was updated successfully, but these errors were encountered:
I have try both custom and managed boot diagnostics. Both say 'Your virtual machine hasn't written anything to its serial port yet'. Seem like it failed at creating stage.
Describe the bug
I am trying to setup FCOS Stable v 40.20240504.3.0 on Azure vm with ignition file. However, it always end with provisioning timeout.
I have try this same ignition file on both VM and GCP. Both are working as expected but not on Azure.
Reproduction steps
Expected behavior
A FCOS VM with custom setup specify in ignition file.
Actual behavior
Deployment failed with provisioning timeout error which copied below.
{
"code": "OSProvisioningTimedOut",
"message": "OS Provisioning for VM 'testvm02' did not finish in the allotted time.
The VM may still finish provisioning successfully.
Please check provisioning state later. Also, make sure the image has been properly prepared (generalized).\r\n * Instructions for Windows: https://azure.microsoft.com/documentation/articles/virtual-machines-windows-upload-image/
}
System details
Butane or Ignition config
Additional information
However, if I create a VM with the same image but without ignition file then the deployment is successful, and everything works.
If my English is too confusing please ask I will try to provide more information.
The text was updated successfully, but these errors were encountered: