Activity log for bug #1470771

Date Who What changed Old value New value Message
2015-07-02 08:33:22 Sam Stoelinga bug added bug
2015-07-02 08:33:22 Sam Stoelinga attachment added fuel-destroy-all.png https://bugs.launchpad.net/bugs/1470771/+attachment/4423336/+files/fuel-destroy-all.png
2015-07-02 08:34:09 Sam Stoelinga 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: 1. Change the \n to <br> for the web interface. 2. 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. 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: 1. Change the \n to <br> for the web interface. 2. 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
2015-07-02 13:16:02 Oleksiy Molchanov fuel: milestone 7.0
2015-07-02 13:16:22 Oleksiy Molchanov fuel: assignee Fuel Library Team (fuel-library)
2015-07-02 13:16:25 Oleksiy Molchanov fuel: importance Undecided Medium
2015-07-02 13:16:28 Oleksiy Molchanov fuel: status New Confirmed
2015-07-16 12:46:44 Oleksiy Molchanov fuel: assignee Fuel Library Team (fuel-library) Fuel Python Team (fuel-python)
2015-08-05 12:01:36 Vladimir Sharshov fuel: assignee Fuel Python Team (fuel-python) Fuel UI Team (fuel-ui)
2015-08-05 12:37:41 Vitaly Kramskikh marked as duplicate 1467893
2015-08-05 12:52:35 Sam Stoelinga removed duplicate marker 1467893
2015-08-05 13:26:48 Vitaly Kramskikh fuel: assignee Fuel UI Team (fuel-ui) Fuel Python Team (fuel-python)
2015-08-06 11:33:02 Vladimir Sharshov 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: 1. Change the \n to <br> for the web interface. 2. 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 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
2015-08-06 11:50:06 Vladimir Sharshov nominated for series fuel/8.0
2015-08-06 11:50:06 Vladimir Sharshov bug task added fuel/8.0
2015-08-06 11:50:18 Vladimir Sharshov fuel/8.0: status New Triaged
2015-08-06 11:50:21 Vladimir Sharshov fuel/8.0: status Triaged Confirmed
2015-08-06 11:50:23 Vladimir Sharshov fuel/8.0: importance Undecided Medium
2015-08-06 11:50:29 Vladimir Sharshov fuel/8.0: assignee Fuel Python Team (fuel-python)
2015-08-06 11:50:31 Vladimir Sharshov fuel/8.0: milestone 8.0
2015-08-06 11:50:34 Vladimir Sharshov fuel: status Confirmed Won't Fix
2015-09-24 12:20:36 Ihor Kalnytskyi fuel/8.0.x: status Confirmed Fix Committed
2015-10-19 12:18:06 Dmitriy Kruglov fuel/8.0.x: status Fix Committed Fix Released
2015-10-22 03:07:24 Dmitry Pyzhov tags area-python
2015-11-30 15:28:46 Dmitry Pyzhov fuel: milestone 7.0 8.0