-
Notifications
You must be signed in to change notification settings - Fork 1.1k
config: set internal RootConfig to default storage if not specified #4131
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
config: set internal RootConfig to default storage if not specified #4131
Conversation
fc3dbcd to
8798ffa
Compare
After we pull in the initial config, it is our source of truth for telling the world where our container storage is in particular, if we, say, have an empty `storage` entry, we will return `StorageDriver: ""` on an Inspect request the problem is, that is a lie. c/storage populates defaults for us, so we actually use overlay in that scenerio. we don't encounter this normally, because if the toml field isn't specified (as it isn't by default), then we inherit the information from the default config However, if a user (or an ignition config) overrides those fields to empty, we will listen to it as the source of truth, and never update to what is actually being used Fix this by inheriting the values from c/storage on the validation step. Signed-off-by: Peter Hunt <[email protected]>
8798ffa to
8152e00
Compare
Codecov Report
@@ Coverage Diff @@
## master #4131 +/- ##
==========================================
+ Coverage 40.42% 40.52% +0.09%
==========================================
Files 110 110
Lines 9331 9338 +7
==========================================
+ Hits 3772 3784 +12
+ Misses 5209 5203 -6
- Partials 350 351 +1 |
|
/retest |
|
LGTM |
|
/retest |
1 similar comment
|
/retest |
|
@haircommander: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: haircommander, mrunalp The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/lgtm |
|
/cherry-pick release-1.19 |
|
@haircommander: once the present PR merges, I will cherry-pick it on top of release-1.19 in a new PR and assign it to you. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
@haircommander: new pull request created: #4161 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/cherry-pick release-1.18 |
|
@haircommander: new pull request created: #4176 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/cherry-pick release-1.17 |
|
@haircommander: #4131 failed to apply on top of branch "release-1.17": DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What type of PR is this?
/kind bug
What this PR does / why we need it:
After we pull in the initial config, it is our source of truth for telling the world where our container storage is
in particular, if we, say, have an empty
storageentry, we will returnStorageDriver: ""on an Inspect requestthe problem is, that is a lie. c/storage populates defaults for us, so we actually use overlay in that scenerio.
we don't encounter this normally, because if the toml field isn't specified (as it isn't by default), then we inherit the information from the default config
However, if a user (or an ignition config) overrides those fields to empty, we will listen to it as the source of truth, and never update to what is actually being used
Fix this by inheriting the values from c/storage on the validation step.
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?