Bug 29958 - Progressbar is still visible after successful join with member server
Progressbar is still visible after successful join with member server
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: UMC (Generic)
UCS 3.0
Other Linux
: P5 normal (vote)
: UCS 3.x
Assigned To: UMC maintainers
:
: 33547 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-01-08 12:40 CET by Alexander Kläser
Modified: 2017-08-08 07:08 CEST (History)
3 users (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): Usability
Max CVSS v3 score:


Attachments
Screenshot System Setup (39.14 KB, image/png)
2013-01-08 12:40 CET, Alexander Kläser
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Kläser univentionstaff 2013-01-08 12:40:35 CET
Created attachment 4955 [details]
Screenshot System Setup

After successfully joining a member server in a UCS domain with System Setup,
the progressbar is still visible with 87%. The last JSON object was:

{
   "info":"Configure 98univention-pkgdb-tools",
   "errors":[],
   "component":"Domain join",
   "finished":true,
   "critical":false,
   "steps":87.050359712230218
}

As the ProgressInfo widget does not know "finished", System Setup should return
100% as soon as finished == true.
Comment 1 Dirk Wiesenthal univentionstaff 2013-01-08 18:30:22 CET
(In reply to comment #0)
> As the ProgressInfo widget does not know "finished", System Setup should return
> 100% as soon as finished == true.

This is not a Bug against System Setup. The ProgressBar should set itself to 100% if finished
Comment 2 Alexander Kläser univentionstaff 2013-11-25 10:00:31 CET
*** Bug 33547 has been marked as a duplicate of this bug. ***
Comment 3 Stefan Gohmann univentionstaff 2017-06-16 20:40:07 CEST
This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.
Comment 4 Stefan Gohmann univentionstaff 2017-08-08 07:08:17 CEST
This issue has been filed against UCS 3.0.

UCS 3.0 is out of maintenance and many UCS components have vastly changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.