Deployment progress bar inaccurate

Bug #1401676 reported by Joseph Fisher
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Committed
Low
Vladimir Sharshov
5.1.x
Won't Fix
Medium
Fuel Library (Deprecated)
6.0.x
Won't Fix
Medium
Fuel Library (Deprecated)
6.1.x
Won't Fix
Medium
Fuel Library (Deprecated)
7.0.x
Won't Fix
Low
Fuel Library (Deprecated)
Mitaka
Fix Committed
Low
Vladimir Sharshov
Newton
Fix Committed
Low
Vladimir Sharshov

Bug Description

For an Ubuntu deployment with Fuel 5.1.1, progress bar is increasing in regular 3% increments, although in reality the Ubuntu install has stalled completely at the disk provisioning step. This appears to be an inaccurate status if the deployment is stalled, but is reporting that it's moving forward.

Changed in fuel:
milestone: none → 6.0.1
assignee: nobody → Vladimir Sharshov (vsharshov)
Stanislav Makar (smakar)
Changed in fuel:
status: New → Triaged
importance: Undecided → High
Changed in fuel:
milestone: 6.0.1 → 6.1
Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

This bug was inactive for two months, returning it back to Fuel library team

Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

The bug description does not contain a solution or workaround, hence was not triaged

Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

The deployment impact of this bug cannot be considered as a high. This bugs looks like the medium one. As we do not backport medium bugs, I set its status won't fix for <=6.0 releases. Please return it back to confirmed if you think this bug should be addressed for all affected releases,

Revision history for this message
Tomasz 'Zen' Napierala (tzn) wrote :

Accordking to triaging rules [1], this bug has no effect on deployment itself, only the information is inaccurate. I need to change the severity to "Low"
[1] https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Confirm_and_triage_bugs

Revision history for this message
Stanislaw Bogatkin (sbogatkin) wrote :

Why it is on fuel-library team? Deployment process indicator managed by astute, isn't it?

Revision history for this message
Aleksandr Didenko (adidenko) wrote :

Assigning it to fuel-python, since we're going to remove fuel-astute group shortly as discussed in ML.

Changed in fuel:
assignee: Fuel Astute Team (fuel-astute) → Fuel Python Team (fuel-python)
Revision history for this message
Vladimir Sharshov (vsharshov) wrote :
tags: added: covered-by-bp feature-progress-bar
Dmitry Pyzhov (dpyzhov)
Changed in fuel:
importance: Medium → Low
milestone: 6.0-updates → 8.0
no longer affects: fuel/8.0.x
Dmitry Pyzhov (dpyzhov)
tags: added: area-python
Revision history for this message
Alexander Kislitsky (akislitsky) wrote :

We passed SCF in 8.0. Moving the bug to 9.0.

Changed in fuel:
milestone: 8.0 → 9.0
Revision history for this message
Vladimir Sharshov (vsharshov) wrote :

Moving to Task Based Deployment solve the problem. Now progress bar calculated based on tasks which run on nodes.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.