This repository has been archived by the owner. It is now read-only.
coreos-metadata race condition on Microsoft Azure #1582
Closed
Labels
Milestone
Comments
For reference, something like this should work: {
"ignition": { "version": "2.0.0" },
"systemd": {
"units": [{
"name": "coreos-metadata.service",
"dropins": [{
"name": "network-online.conf",
"contents": "[Service]\nRequires=network-online.target\nAfter=network-online.target"
}]
}]
}
} |
Fixed in coreos/coreos-overlay#2262. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Issue Report
Bug
CoreOS Version
1122.2.0
Environment
What hardware/cloud provider/hypervisor is being used to run CoreOS?
Microsoft Azure
Expected Behavior
coreos-metadata.service runs normally and generates the IP metadata (COREOS_AZURE_IPV4_DYNAMIC) for the instance.
Actual Behavior
About 1/3 to 1/2 of the time, coreos-metadata runs before DHCP has completed so it can't capture the private IP.
Reproduction Steps
Other Information
Creating a dropin for coreos-metadata.service to make it require and run after network-online.target works around the issue.
The text was updated successfully, but these errors were encountered: