Bug 1538940

Is this still relevant? If not, can you please close?

> Should not use the "execute" button during configuration while deploying HE 
> via cockpit based ansible deployment. It will produce a misunderstanding for
> user.
>
> Additional info: 
> Suggest to provide the "next" button to switch to the next page.

It's possible we should use a different word than "Execute", but "Next" would imply to the user that they will simply be moving to the next major step, which isn't true. Non-trivial activity occurs at the end of each major step, which is what the wording on the button is intended to indicate to the user. If the execution for that step is successful, the "Next" button is displayed, indicating to the user that it's safe to move on to the next major step.

I'm open to wording suggestions for the button, but "Next" isn't the correct choice, in my opinion. If no other suggestions are presented, I recommend closing this.

How about "Continue"?

(In reply to Ryan Barry from comment #3)
> How about "Continue"?

I think "Continue" has the same problem as "Next" in that it doesn't indicate that something more than moving to the next step is going to happen upon clicking it. A couple of alternatives off the top of my head are: 

1. Put an info message in the preview screen explaining what will happen
2. Move the button inside of the preview screen and disable the "Next" button until execution has completed

To me, at least, "Next" implies some immediacy, where "continue" and "proceed" carry the subtext that this is a process.

But this is nitpicky. Windows installer packages and Anaconda have used "next" for years, and it's something users are familiar with. They also don't expect an immediate return

(In reply to Ryan Barry from comment #5)
> To me, at least, "Next" implies some immediacy, where "continue" and
> "proceed" carry the subtext that this is a process.

I suppose. I like "proceed" better than continue.

> 
> But this is nitpicky. Windows installer packages and Anaconda have used
> "next" for years, and it's something users are familiar with. They also
> don't expect an immediate return

I don't know that I agree with the user expectation, but I'll concede as I agree that the whole issue is nitpicky.

(In reply to Phillip Bailey from comment #2)
> > Should not use the "execute" button during configuration while deploying HE 
> > via cockpit based ansible deployment. It will produce a misunderstanding for
> > user.
> >
> > Additional info: 
> > Suggest to provide the "next" button to switch to the next page.
> 
> It's possible we should use a different word than "Execute", but "Next"
> would imply to the user that they will simply be moving to the next major
> step, which isn't true. Non-trivial activity occurs at the end of each major
> step, which is what the wording on the button is intended to indicate to the
> user. If the execution for that step is successful, the "Next" button is
> displayed, indicating to the user that it's safe to move on to the next
> major step.
> 
> I'm open to wording suggestions for the button, but "Next" isn't the correct
> choice, in my opinion. If no other suggestions are presented, I recommend
> closing this.

"Proceed" seems ok.

Two patches are merged - what else is missing? Why is it in NEW state?

(In reply to Yaniv Kaul from comment #8)
> Two patches are merged - what else is missing? Why is it in NEW state?

The patches were pushed and merged today. I just hadn't gone back through the list of bugs to see what needed to be updated. Moving to MODIFIED now.

With cockpit-ovirt-0.11.17-1, it changes the "execute" button to "Prepare VM". It will tell the user the step is preparing a local VM , isn't confusing.

So, change the bug's status to verified.

This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.