Bug 999964 - Unclear completion message in engine-setup esp for upgrades
Summary: Unclear completion message in engine-setup esp for upgrades
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-setup
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.3.0
Assignee: Alon Bar-Lev
QA Contact: movciari
URL:
Whiteboard: integration
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-22 13:15 UTC by Andrew Cathrow
Modified: 2015-09-22 13:09 UTC (History)
7 users (show)

Fixed In Version: is12
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-21 22:19:24 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 18440 0 None None None Never
oVirt gerrit 18508 0 None None None Never

Description Andrew Cathrow 2013-08-22 13:15:25 UTC
At the end of an upgrade running engine-setup the last message is

"[ INFO  ] Stage: Termination"

It's not clear what that means.
I understand what this means, but a customer may believe this is a failure.
We can fix this simply by adding an extra INFO messaging saying that upgrade/setup completed successfully

Comment 1 Alon Bar-Lev 2013-08-23 02:57:46 UTC
(In reply to Andrew Cathrow from comment #0)
> At the end of an upgrade running engine-setup the last message is
> 
> "[ INFO  ] Stage: Termination"
> 
> It's not clear what that means.
> I understand what this means, but a customer may believe this is a failure.
> We can fix this simply by adding an extra INFO messaging saying that
> upgrade/setup completed successfully

The same infrastructure is used for host-deploy, host-rename, engine-clean, hosted-engine and of course engine setup and upgrade.

This is the last stage of sequence (well apart of reboot), we can display any label you want but it should be generic and at the framework we do not actually know what we are used for.

Comment 2 Alon Bar-Lev 2013-08-23 03:12:01 UTC
Forgot to mention that this stage is executed regardless of success/failure.

Comment 3 Andrew Cathrow 2013-08-23 03:15:03 UTC
(In reply to Alon Bar-Lev from comment #2)
> Forgot to mention that this stage is executed regardless of success/failure.


Can we display something like "operation completed successfully" ?

Ideally we would replace operation with the appropriate use (upgrade, etc) - is that possible?

Comment 4 Alon Bar-Lev 2013-08-23 03:19:51 UTC
(In reply to Andrew Cathrow from comment #3)
> (In reply to Alon Bar-Lev from comment #2)
> > Forgot to mention that this stage is executed regardless of success/failure.
> 
> 
> Can we display something like "operation completed successfully" ?

No... see above... this stage is executed regardless of success failure.

> Ideally we would replace operation with the appropriate use (upgrade, etc) -
> is that possible?

Of course we can, but I try to avoid extra complexity at the core (otopi), it does not currently know what is happening.

Maybe best to just remove this message? I can add silents rules...

Or, I can add another message after the termination with the message you want. It will look like:

[ INFO  ] Stage: Termination
[ INFO  ] {action} completed successfully

action ::= setup|cleanup|upgrade|rename

Comment 5 Andrew Cathrow 2013-08-23 03:22:05 UTC
(In reply to Alon Bar-Lev from comment #4)

> 
> Or, I can add another message after the termination with the message you
> want. It will look like:
> 
> [ INFO  ] Stage: Termination
> [ INFO  ] {action} completed successfully
> 
> action ::= setup|cleanup|upgrade|rename

Yes please.

Comment 6 Alon Bar-Lev 2013-08-23 03:34:57 UTC
[ INFO  ] Stage: Clean up
[ INFO  ] Stage: Pre-termination
[ INFO  ] Stage: Termination
[ INFO  ] Execution of upgrade completed successfully

[ INFO  ] Stage: Clean up
[ INFO  ] Stage: Pre-termination
[ INFO  ] Stage: Termination
[ ERROR ] Execution of upgrade failed

Comment 7 Itamar Heim 2014-01-21 22:19:24 UTC
Closing - RHEV 3.3 Released

Comment 8 Itamar Heim 2014-01-21 22:25:34 UTC
Closing - RHEV 3.3 Released


Note You need to log in before you can comment on or make changes to this bug.