No service info during master node installation

Bug #1439193 reported by deactivateduser
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
High
Maciej Kwiek

Bug Description

{"build_id": "2015-03-26_22-54-44", "ostf_sha": "a4cf5f218c6aea98105b10c97a4aed8115c15867", "build_number": "234", "release_versions": {"2014.2-6.1": {"VERSION": {"build_id": "2015-03-26_22-54-44", "ostf_sha": "a4cf5f218c6aea98105b10c97a4aed8115c15867", "build_number": "234", "api": "1.0", "nailgun_sha": "b163f6fc77d6639aaffd9dd992e1ad96951c3bbf", "production": "docker", "python-fuelclient_sha": "e5e8389d8d481561a4d7107a99daae07c6ec5177", "astute_sha": "3f1ece0318e5e93eaf48802fefabf512ca1dce40", "feature_groups": ["mirantis"], "release": "6.1", "fuelmain_sha": "320b5f46fc1b2798f9e86ed7df51d3bda1686c10", "fuellib_sha": "9c7716bc2ce6075065d7d9dcf96f4c94662c0b56"}}}, "auth_required": true, "api": "1.0", "nailgun_sha": "b163f6fc77d6639aaffd9dd992e1ad96951c3bbf", "production": "docker", "python-fuelclient_sha": "e5e8389d8d481561a4d7107a99daae07c6ec5177", "astute_sha": "3f1ece0318e5e93eaf48802fefabf512ca1dce40", "feature_groups": ["mirantis"], "release": "6.1", "fuelmain_sha": "320b5f46fc1b2798f9e86ed7df51d3bda1686c10", "fuellib_sha": "9c7716bc2ce6075065d7d9dcf96f4c94662c0b56"}

There's no service information during fuel-master node installation.

Steps to reproduce:
1) Start Fuel installation
2) Wait for Fuel menu is shown
3) Press F8 to continue installation
4) "Total time:" message appears in the console

Actual result: the installation process continues for 20-30 minutes (depends on host machine)

Expected result: information about installation process is being shown, for instance current operation, estimated time etc.

Revision history for this message
deactivateduser (deactivateduser-deactivatedaccount) wrote :
description: updated
Revision history for this message
Aleksey Kasatkin (alekseyk-ru) wrote :

Please provide version info.

Changed in fuel:
status: New → Confirmed
Revision history for this message
Nastya Urlapova (aurlapova) wrote :

It is related to UX of MOS, so increase to High.

Changed in fuel:
importance: Medium → High
Revision history for this message
deactivateduser (deactivateduser-deactivatedaccount) wrote :

Added version.

description: updated
description: updated
Changed in fuel:
milestone: none → 6.1
tags: added: feature
Changed in fuel:
assignee: Fuel Python Team (fuel-python) → Maciej Kwiek (maciej-iai)
Revision history for this message
Bartłomiej Piotrowski (bpiotrowski) wrote :

The reason is that Docker doesn't display a progress bar of loading images from the tarball[1][2]. The only solution at the moment is to use pv[3] to pipe the data to Docker.

[1] https://github.com/stackforge/fuel-main/blob/master/iso/bootstrap_admin_node.docker.sh#L104
[2] https://github.com/docker/docker/issues/8298
[3] http://www.ivarch.com/programs/pv.shtml

Changed in fuel:
status: Confirmed → Triaged
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-main (master)

Fix proposed to branch: master
Review: https://review.openstack.org/170153

Changed in fuel:
status: Triaged → In Progress
Changed in fuel:
assignee: Maciej Kwiek (maciej-iai) → Bartlomiej Piotrowski (bpiotrowski)
Changed in fuel:
assignee: Bartlomiej Piotrowski (bpiotrowski) → Maciej Kwiek (maciej-iai)
Changed in fuel:
assignee: Maciej Kwiek (maciej-iai) → Bartlomiej Piotrowski (bpiotrowski)
Changed in fuel:
assignee: Bartlomiej Piotrowski (bpiotrowski) → Maciej Kwiek (maciej-iai)
Revision history for this message
Maciej Kwiek (maciej-iai) wrote :

After testing it appears that pv is useless in this use case. `Docker load` command loads the image tarball at the beginning of it's runtime, which happens quite fast and then it makes it's own processing, which doesn't involve any IO for the most time (therefore -d option for pv is useless too). I proposed a fix which was the initial idea - split the message so that after the lrzip executes, there is a message stating "This will take a while".

If we are ever going to show real progress bar to the user, the change to docker load command will be needed. Another workaround would be creating docker registry and loading the image by docker pull instead of docker load, but that doesn't really make much sense in any other way and seems to hacky for my taste.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-main (master)

Reviewed: https://review.openstack.org/170153
Committed: https://git.openstack.org/cgit/stackforge/fuel-main/commit/?id=8a50ebda3a19f30cbd6d53ed4c787b0a7c08a4b4
Submitter: Jenkins
Branch: master

commit 8a50ebda3a19f30cbd6d53ed4c787b0a7c08a4b4
Author: Maciej Kwiek <email address hidden>
Date: Thu Apr 2 16:46:54 2015 +0200

    Split message about unpacking and loading images

    User could think that master node installation hanged, as lrzip provided
    total time and nothing happened next. After lrzip executes there is
    additional message warning that image loading may take some time.

    PipeViewer was thought of as possible mean to show progress bar to the
    user, but because of the way `docker load` command works (it loads the
    data first and then processes it) it wasn't a viable option.

    To assure good user experience docker load should provide it's own
    progress bar or any other indicator, but this change would need to be
    made in docker itself.

    Change-Id: I57a63a15adfef45a5e68861c91ff09dc281a15e4
    Closes-Bug: #1439193

Changed in fuel:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on fuel-main (master)

Change abandoned by Aleksey Kasatkin (<email address hidden>) on branch: master
Review: https://review.openstack.org/173241
Reason: Related https://launchpad.net/bugs/1439193 was fixed another way.

tags: added: on-verification
Revision history for this message
Anastasia Palkina (apalkina) wrote :

Verified on ISO #360

"build_id": "2015-04-28_22-54-38", "build_number": "360", "release_versions": {"2014.2.2-6.1": {"VERSION": {"build_id": "2015-04-28_22-54-38", "build_number": "360", "api": "1.0", "fuel-library_sha": "0e5b82d24853304befb22145ac4aaf3545d295e1", "nailgun_sha": "5753e0ce613473381a63c63d4309777fce4bea70", "feature_groups": ["mirantis"], "openstack_version": "2014.2.2-6.1", "production": "docker", "python-fuelclient_sha": "8cd6cf575d3c101dee1032abb6877dfa8487e077", "astute_sha": "04ebab96d57b0e8acbf2d7f3ba05e4fbf31b741e", "fuel-ostf_sha": "b38602c841deaa03ddffc95c02f319360462cbe3", "release": "6.1", "fuelmain_sha": "ee112acfdd0f9017ef40be53e8e51bb5c429e97c"}}}, "auth_required": true, "api": "1.0", "fuel-library_sha": "0e5b82d24853304befb22145ac4aaf3545d295e1", "nailgun_sha": "5753e0ce613473381a63c63d4309777fce4bea70", "feature_groups": ["mirantis"], "openstack_version": "2014.2.2-6.1", "production": "docker", "python-fuelclient_sha": "8cd6cf575d3c101dee1032abb6877dfa8487e077", "astute_sha": "04ebab96d57b0e8acbf2d7f3ba05e4fbf31b741e", "fuel-ostf_sha": "b38602c841deaa03ddffc95c02f319360462cbe3", "release": "6.1", "fuelmain_sha": "ee112acfdd0f9017ef40be53e8e51bb5c429e97c"

Changed in fuel:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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