Repository navigation
provider OpenStack: add 404 retryCode #2355
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
Open
robinschneider
wants to merge
2
commits into
coreos:main
Choose a base branch
from
robinschneider:openstack-retry-404
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
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.
Preserve the empty-config response.
When an instance has no user data, Nova returns 404 for
user_data. (raw.githubusercontent.com) This retry policy prevents that response from becomingresource.ErrNotFound. With the default unlimited HTTP timeout and no config drive, Ignition waits indefinitely instead of booting with an empty config. (raw.githubusercontent.com)Distinguish a ready metadata service with no user data from a service that is not ready, then retain retries for the latter. As per path instructions, “Platform providers must retry config fetch, allow empty config.”
Source: Path instructions
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.
I spawned an instance using this patch without user-data on Brightbox, an OpenStack based cloud-provider - the user-data has returned a 200 with an empty config. That has been processed by Ignition as "empty config".
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.
Analysis chain
Script executed:
Length of output: 11487
@tormath1Thanks for testing. Your result confirms that Brightbox handles the HTTP 200 empty-response case correctly with this patch. My original wording was too broad: no user data does not always produce HTTP 404.The remaining concern is specific to deployments that return HTTP 404 for absent user data. Nova’s source distinguishes absent user data from empty user data. Ignition’s HTTP code confirms that adding 404 to
RetryCodesretries that response indefinitely with the default timeout.The Brightbox result does not exercise that case. Please also check a Nova instance with absent user data and no config drive, and confirm whether
user_datareturns 404 and whether boot completes.Learnings used
You are interacting with an AI system.