Hide Forgot
Description of problem: Cloud Intel - reports - Dashboards Unable to save default dashboard . Got error message "Tab title must be Unique for this group" Version-Release number of selected component (if applicable): 5.6.1.2.20160810181333_8ba817b How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I cannot reproduce the bug in 5.6. and in upstream but in 5.7.1. Do we need to clone and fix this BZ for target release 5.7.1 (euwe)?
Dmitry, can you please try to reproduce this for Hilda, thanks!
I cannot reproduce the issue at all. I checked it on CFME 5.6.1, 5.7.1 and the latest upstream. Tried to edit default dashboard tab title and revert it back to "Default Dashboard". I couldn't catch any error. Default dashboard is saved fine. Gellert, am I missing something?
I don't remember. It is soo long and far. Next time, we need to make sure reproducer steps are written down. We cannot rely on my memory. I can jump under the bus tomorrow.
Gellert, we still cannot reproduce the bug. Could you provide more exact info about how to reproduce it? Thanks.
a new copy of the database is available - I'll build a reproducer with it and can place the dump somewhere if you let me know where, the file is roughtly 9.8Gb large uncompressed.
steps using the reproducer : 1- log in as admin 2- go to "cloud intel > reports" 3- go to "darhboards" 4- edit the default dashboard and add any widget 5- save results : error message "Tab Title must be unique for this group"
Felix, thank you very much, reproducer works but I still haven't find out, how to reproduce the bug. DB looks ok. Any ideas about exact steps to reproduce it? Maybe user did some unusual steps before reaching Dashboards which led to the bug when reaching Dashboards.
(In reply to Hilda Stastna from comment #16) > Felix, > > thank you very much, reproducer works > but I still haven't find out, > how to reproduce the bug. DB looks ok. > > Any ideas about exact steps to reproduce it? > Maybe user did some unusual steps before reaching Dashboards > which led to the bug when reaching Dashboards. no idea either - I doubt the customer knows either why that happened. it may help that their setup likely went through a lot of updates - since 3.2 I believe. Can we try and find a way to fox their appliance from this state? if we can understand why it got to that state maybe we can do something about preventing that state and catch the cause when it happens again, if ever.
I cannot reproduce the bug in master and also in older versions (including darga, euwe, fine) so I am closing the bug. Please, reopen if bug occurs again or if we find all the steps to reproduce it because some step is still missing to reproduce the bug properly.