Unable to use tabs in new environment

[David Bell]

I have Mirantis Fuel 7.0, and it has been installed since the day of release. A few days ago I started experiencing an issue where it would not allow me to select the tabs such as Network or Settings after creating a new environment. This also affected my ability to select tabs in previously created environments.

I have tried this on Firefox, Chrome, and IE and all exhibit the same issue. I have also updated the Fuel server to the latest code release.

The only way I have found to get my tab functionality back was to delete the new environment, I was then able to select tabs in the previously created environments.

[Vitaly Kramskikh (vkramskikh)]

Hi, there should be JS error in the browser console (it's better to use Chrome Dev Tools as they support source maps). Could you please provide it?

[David Bell (db4068)]

Ok, I did as you asked and I attached the screen shot of what happened.

- I created the new environment "CIT-OPENSTACK-TEST"
- I added a node to the environment
- I then tried tabbing through the different elements
   - It went to Network tab with no error, then I was unable to reach any other tab.

The first image is a screen shot of the Fuel UI and the second one is a screen shot of the JS Error that was caught when trying to go to another tab.

I have also attached a txt document that contains the output of the JS error link in the error log. It was too long to post in this comment box.

[David Bell (db4068)]

Apparently I am not able to attach more then one file, here is the second one

[David Bell (db4068)]

Here is the third one

[Vitaly Kramskikh (vkramskikh)]

Thanks! Could you please also:

1) expand error to see the stacktrace by clicking the triangle near "Uncaught error" and make a screenshot?
2) Attach diagnostic snapshot from the support page?
3) Tell if you have some plugins installed

[David Bell (db4068)]

1. Attached Stacktrace screenshot

2. Not sure what is being requested

3. I have removed all plugins and rebooted the Fuel server prior to posting the bug request. There are no add-in's in Chrome either.

[Vitaly Kramskikh (vkramskikh)]

It seems the zabbix section is still here after plugin removal even for the new env. Python guys, could you please look into it?

David, you can download the diagnostic snapshot on the support page of the Fuel UI ("Download Diagnostic Snapshot" section)

[Ihor Kalnytskyi (ikalnytskyi)]

Hey David,

I have no idea what's going on. Did you install zabbix previously? And then remove it?

I'd expect such kind of errors if:

* you install zabbix plugins
* create new env
* remove zabbix plugin

but if you after that create one more new env, everything should work fine for that env.

Could you please attach diagnostic snapshot?

[David Bell (db4068)]

I have been trying to add the diagnostic snapshot, but it keeps timing out. It is 1GB in size, so this may be an issue. I will keep trying to post it.

[David Bell (db4068)]

As for Zabbix, I did have the plug in installed but I have removed all plug ins and rebooted Fuel and still get the same error.

[David Bell (db4068)]

Here is the diagnostic snapshot

[Bug Checker Bot (bug-checker)]

(This check performed automatically)
Please, make sure that bug description contains the following sections filled in with the appropriate data related to the bug you are describing:

actual result

expected result

steps to reproduce

For more detailed information on the contents of each of the listed sections see https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Here_is_how_you_file_a_bug

[Dmitry Pyzhov (dpyzhov)]

QA team, could you check if the issue still exists in 9.0 release?

[Nastya Urlapova (aurlapova)]

@Dima, we don't work with zabbix plugin, could you address to right person?

[Dmitry Pyzhov (dpyzhov)]

Zabbix code has been removed from Fuel and the bug shouldn't exist in Mitaka version. Please check if it is still applicable.

[Ivan Ponomarev (ivanzipfer)]

Please reopen when 'JS error' will be provided