Fix 404 Error using Nova FlavorsResource.showMetadata() #164
Conversation
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
Problem: FlavorsResource.showMetadata() results in a 404 error because it is issuing an API call that does not exist since Flavors do not have metadata. Instead, they have “extra-specs”, key-value pairs that the Nova scheduler uses to launch Servers on Hosts that can supply the capabilities described by the flavor's extra-specs. Solution: Replace showMetaData() with showExtraSpecs(), use the correct “os-extra_specs” extended API path and add a new ExtraSpecs class to deserialize the API response to a Map<String, String>.
Revert accidental previous commit of pom file where I had set skip.sign=true
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Problem: FlavorsResource.showMetadata() results in a 404 error because
it is issuing an API call that does not exist since Flavors do not have
metadata. Instead, they have something quite similar, “extra-specs”, key-value pairs that the
Nova scheduler uses to launch Servers on Hosts that can supply the
capabilities described by the flavor's extra-specs.
Solution: Replace showMetaData() with showExtraSpecs(), use the correct
“os-extra_specs” extended API path and add a new ExtraSpecs class to
deserialize the API response to a Map<String, String>.