No connectivity notifies me to update and destroy_all - Formatting and content issue

Bug #1470771 reported by Sam Stoelinga
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
Medium
Fuel Python (Deprecated)
8.0.x
Fix Released
Medium
Fuel Python (Deprecated)

Bug Description

Verion: 6.1 build_id: 2015-06-19_13-02-31 (Official 6.1 release)

Current result:
When there is no connectivity a message is shown in Fuel UI:
WARNING: There are issues connecting to Fuel update repository.\nPlease fix your connection and update this node with `yum update`\nThen run `dockerctl destroy all; bootstrap_admin_node.sh;`\nto repeat bootstrap on Fuel Master with the latest updates.\nFor more information, check out Fuel documentation at:\nhttp://docs.mirantis.com/fuel

Also see screenshot..

Expected results:

Don't suggest user to destroy all we all know the dangers of this. There should be a solution to update Fuel Master with latest updates without having to destroy all. Please advice user to use that solution instead. If there is no solution without using destroy all then we should create such a solution.

Related info:
This is the bug that introduced this: https://bugs.launchpad.net/fuel/+bug/1466418

Tags: area-python
Revision history for this message
Sam Stoelinga (sammiestoel) wrote :
description: updated
Changed in fuel:
milestone: none → 7.0
assignee: nobody → Fuel Library Team (fuel-library)
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Baboune (seyvet) wrote :

Installing a new fuel controller with Mirantis 6.1, I can see the warning.

It is unclear if I should destroy all the containers since "yum update" does nothing and all repositories are accessible.

Revision history for this message
Oleksiy Molchanov (omolchanov) wrote :

Python team, can you help with this?

Changed in fuel:
assignee: Fuel Library Team (fuel-library) → Fuel Python Team (fuel-python)
Revision history for this message
Vladimir Sharshov (vsharshov) wrote :

UI team, please check moment with message '\n'

Changed in fuel:
assignee: Fuel Python Team (fuel-python) → Fuel UI Team (fuel-ui)
Revision history for this message
Sam Stoelinga (sammiestoel) wrote :

This is not a duplicate. You should never recommend a user to destroy all his data when there is no connectivity. The bug marked as duplicate just says the formatting issue. This bug is about incorrect and dangerous content.

I suggest removing the duplicate tag and putting it as higher importance. It's really bad if a user blindly follows the suggestion and deletes his data when there was jsut a connectivity issue.....

Revision history for this message
Vitaly Kramskikh (vkramskikh) wrote :

Agreed. Since formatting issue is covered by another bug, reassigning this one back to python team

Changed in fuel:
assignee: Fuel UI Team (fuel-ui) → Fuel Python Team (fuel-python)
description: updated
Revision history for this message
Vladimir Sharshov (vsharshov) wrote :

UX problem. Do not affect deployment. Let move it to 8.0

Changed in fuel:
status: Confirmed → Won't Fix
Revision history for this message
Ihor Kalnytskyi (ikalnytskyi) wrote :

The message was changed in 8.0. Now it's

There is an issue connecting to the Fuel update repository. Please fix your connection prior to applying any updates. Once the connection is fixed, we recommend reviewing and applying Maintenance Updates for this release of Mirantis OpenStack: https://docs.mirantis.com/openstack/fuel/fuel-${FUEL_RELEASE}/release-notes.html#maintenance-updates"

So move it to Fix Commited.

Revision history for this message
Sam Stoelinga (sammiestoel) wrote :

Igor can you link the gerrit review where this was introduced? Thanks!

Revision history for this message
Dmitriy Kruglov (dkruglov) wrote :
Dmitry Pyzhov (dpyzhov)
tags: added: area-python
Dmitry Pyzhov (dpyzhov)
Changed in fuel:
milestone: 7.0 → 8.0
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.