Bug 1468462 - Edit aborted! duplicate sessions
Summary: Edit aborted! duplicate sessions
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.8.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: GA
: cfme-future
Assignee: Jozef Zigmund
QA Contact: Vatsal Parekh
URL:
Whiteboard: general:usability
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-07 07:37 UTC by Vatsal Parekh
Modified: 2017-07-18 06:02 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-13 14:51:20 UTC
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Vatsal Parekh 2017-07-07 07:37:41 UTC
Description of problem:
From configuration, when I try to change 'VMware Console Support', it gives me this error 'Edit aborted! CFME does not support the browser's back button or access from multiple tabs or windows of the same browser. Please close any duplicate sessions before proceeding.'
But, I'm the only one using this appliance. 
Video: https://goo.gl/h1xZXh

Version-Release number of selected component (if applicable):
Version 5.8.1.0.20170623170756_3ed4411
Chrome : Version 59.0.3071.115 (Official Build) (64-bit)
How reproducible:


Steps to Reproduce:
1.Configurations -> VMware Console Support
2.
3.

Actual results:
Duplicate session error

Expected results:
Changes should be there 

Additional info:
Didn't find any error or fatal on production log
Video: https://goo.gl/h1xZXh

Comment 5 Jozef Zigmund 2017-07-13 13:50:17 UTC
Hi Vatsal, I tested it and it works for me (on 5.8.z - fine branch). Could you please verify that? Please be sure that your Chrome browser has disabled the additional plugins and you operate only with 1 browser tab. If you are still able to reproduce the bug, can you send me the link to the appliance (private comment)?

Comment 6 Vatsal Parekh 2017-07-13 14:21:39 UTC
Hey Josef, 
I had sent a message regarding this on gitter/manageIQ channel. 
So, the issue seems to be the Grammerly Plugin on Chrome, even if I had disable it, I was still getting the issue. So now I completely deleted it from Chrome, and it works perfect now! I had filed many Chrome specific bugs which Devs are not able to reproduce, but seems like Grammerly was blocking some of the js stuff. I think you should close this BZ now, as even I'm not getting this error. 
Just a suggestion that, we should put this into a Note somewhere that this kind of behaviour is noted with Grammerly, maybe some user would encounter someday and we can be aware.

Comment 7 Jozef Zigmund 2017-07-13 14:51:20 UTC
Hi Vatsal, thank you for fast reply. Yes there is more plugins those can cause failures, just be aware of that. It could be JS specific plugin, but also session manipulating ones. My recommendation is, avoid to use them (have them enabled) when you are testing.

Closing the BZ as the bug was caused by browser plugin.


Note You need to log in before you can comment on or make changes to this bug.