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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug 2139574: blank vm name in customize #987
Bug 2139574: blank vm name in customize #987
Conversation
@upalatucci: This pull request references Bugzilla bug 2139574, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
Requesting review from QA contact: 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. |
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.
Using the already processed template in the parent component is a great way to get the VM name, thanks for this, Ugo! Looks like this is the improvement PR of #787 :)
However, the code changes don't work in one specific case - when WE need to generate the VM name (I mean the name with those 3 human readable words - as we used to do earlier by default no matter the template NAME parameter). For this case, the empty VM name field occurs in the drawer already (the VM name should already be generated - by generateVMName
function we have already implemented in our code, this code should be executed in this case):
See how the yaml looks like in this case (we need to support this case, too):
This happens (I mean empty Name field) also when the VM cannot be quick created (and has the yaml as above - orange rectangle):
Note that the buggy case mentioned above worked well without code changes in this PR.
...alog/templatescatalog/components/TemplatesCatalogDrawer/TemplatesCatalogDrawerCreateForm.tsx
Outdated
Show resolved
Hide resolved
9b381b5
to
a53054c
Compare
thanks @hstastna i've just fixed that case |
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.
The issue I've mentioned earlier is fixed! 馃憤馃徑
Now just one little thing and then I think we are good to go, Ugo! 馃槉
...alog/templatescatalog/components/TemplatesCatalogDrawer/TemplatesCatalogDrawerCreateForm.tsx
Outdated
Show resolved
Hide resolved
a53054c
to
0de7339
Compare
@avivtur @metalice @pcbailey @vojtechszocs please review |
onChange={(v) => setStartVM(v)} | ||
label={t('Start this VirtualMachine after creation')} | ||
/> | ||
<Alert variant="danger" title={t('Quick create error')} isInline> |
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.
U can use AlertVariant from patternfly
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.
Hmm, what is the preferred component we should use and why? I don't see much difference, at least from the functional point of view, but maybe there is some difference...
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.
done thanks
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.
according to your videos I can't understand if you really fixed the bug, it still seems stuck at a loading skeleton after you click on customize, can you please provide a clip including the vm being created?
...alog/templatescatalog/components/TemplatesCatalogDrawer/TemplatesCatalogDrawerCreateForm.tsx
Outdated
Show resolved
Hide resolved
OMG my videos are so bad ahahahah! |
I've tested this PR (when our clusters were working) and I was not able to reproduce the issue anymore. The issue is presented in the bugzilla (video). |
0de7339
to
5a6d8c2
Compare
I could reproduce it. You have to be fast or set up a throttling in the network dev tools |
5a6d8c2
to
2f56236
Compare
2f56236
to
893005c
Compare
@upalatucci: This pull request references Bugzilla bug 2139574, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: 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. |
1 similar comment
@upalatucci: This pull request references Bugzilla bug 2139574, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: 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. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: avivtur, hstastna, upalatucci 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 |
/retest |
@upalatucci: All pull requests linked via external trackers have merged: Bugzilla bug 2139574 has been moved to the MODIFIED state. 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. |
馃摑 Description
Don't re-process the template just for the VM name. Use the already processed template in the parent component.
If the template is not processable due to required parameters,
canQuickCreate
is false and the user would not have the name input field. The Customize page would generate the name instead (if generatable).馃帴 Demo
Before
simplescreenrecorder-2022-12-13_14.40.07.mp4
After
correct-2022-12-13_14.41.22.mp4