fix the image type can not be saved when saving cluster as a template #108
Conversation
Signed-off-by: liuying <liu.ying@99cloud.net>
|
@lysign: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it. 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. |
kubeclipper-bot
added
kind/bug
Codecov Report
@@ Coverage Diff @@
## master #108 +/- ##
=======================================
Coverage 47.46% 47.46%
=======================================
Files 6 6
Lines 552 552
Branches 152 152
=======================================
Hits 262 262
Misses 227 227
Partials 63 63 |
|
LGTM label has been added. Git tree hash: e3e2e12249620c5bdbcc8c660d91431964df4268
|
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lysign, moweiwei The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
kubeclipper-bot
added
the
approved
|
/cherrypick release-1.1 |
|
@lysign: once the present PR merges, I will cherry-pick it on top of release-1.1 in a new PR and assign it to you. In 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. |
|
@lysign: new pull request created: #109 In 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. |
Signed-off-by: liuying liu.ying@99cloud.net
What type of PR is this?
/kind bug
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #76
Special notes for reviewers:
Does this PR introduced a user-facing change?
Additional documentation, usage docs, etc.: