Skip to content
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

Merged

Conversation

upalatucci
Copy link
Member

@upalatucci upalatucci commented Nov 28, 2022

馃摑 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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 28, 2022

@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
  • bug is open, matching expected state (open)
  • bug target release (4.13.0) matches configured target release for branch (4.13.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

Requesting review from QA contact:
/cc @gouyang

In response to this:

Bug 2139574: blank vm name in customize

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.

@openshift-ci openshift-ci bot requested a review from gouyang November 28, 2022 09:57
Copy link
Member

@hstastna hstastna left a 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):
no_name
See how the yaml looks like in this case (we need to support this case, too):
no_name_yaml
This happens (I mean empty Name field) also when the VM cannot be quick created (and has the yaml as above - orange rectangle):
nono

Note that the buggy case mentioned above worked well without code changes in this PR.

@upalatucci
Copy link
Member Author

thanks @hstastna i've just fixed that case

Copy link
Member

@hstastna hstastna left a 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! 馃槉

@openshift-ci openshift-ci bot added the lgtm Passed code review, ready for merge label Nov 29, 2022
@hstastna
Copy link
Member

@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>
Copy link
Member

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

Copy link
Member

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...

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done thanks

Copy link
Member

@avivtur avivtur left a 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?

@upalatucci
Copy link
Member Author

upalatucci commented Nov 30, 2022

OMG my videos are so bad ahahahah!
I thought they were good but they don't even show the real issue.
The real issue is that when you click really fast the 'Customize' button on the catalog, the vmName does not show up on the next page. I'll update the video soon

@hstastna
Copy link
Member

hstastna commented Nov 30, 2022

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?

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).

@openshift-ci openshift-ci bot removed the lgtm Passed code review, ready for merge label Nov 30, 2022
@upalatucci
Copy link
Member Author

upalatucci commented Nov 30, 2022

I could reproduce it. You have to be fast or set up a throttling in the network dev tools

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 13, 2022

@upalatucci: This pull request references Bugzilla bug 2139574, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.13.0) matches configured target release for branch (4.13.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

Requesting review from QA contact:
/cc @gouyang

In response to this:

Bug 2139574: blank vm name in customize

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
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 13, 2022

@upalatucci: This pull request references Bugzilla bug 2139574, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.13.0) matches configured target release for branch (4.13.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

Requesting review from QA contact:
/cc @gouyang

In response to this:

Bug 2139574: blank vm name in customize

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.

@openshift-ci openshift-ci bot added the lgtm Passed code review, ready for merge label Dec 13, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 13, 2022

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved This issue is something we want to fix label Dec 13, 2022
@upalatucci
Copy link
Member Author

/retest

@openshift-merge-robot openshift-merge-robot merged commit 2932b63 into kubevirt-ui:main Dec 13, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 13, 2022

@upalatucci: All pull requests linked via external trackers have merged:

Bugzilla bug 2139574 has been moved to the MODIFIED state.

In response to this:

Bug 2139574: blank vm name in customize

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved This issue is something we want to fix bugzilla/severity-medium bugzilla/valid-bug lgtm Passed code review, ready for merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants