| Summary: | Unable to upload objects to object storage using IE 11 | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Jeremy <jmelvin> | ||||||
| Component: | python-django-horizon | Assignee: | Itxaka <iserrano> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Ido Ovadia <iovadia> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 7.0 (Kilo) | CC: | aortega, apevec, athomas, dhill, dmaley, hguemar, jliberma, jmelvin, lhh, mrunge, rhos-maint, sgotliv, srevivo | ||||||
| Target Milestone: | async | Keywords: | ZStream | ||||||
| Target Release: | 7.0 (Kilo) | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | python-django-horizon-2015.1.3-2.el7ost | Doc Type: | Bug Fix | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2016-06-01 12:28:47 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
Created attachment 1146903 [details]
object name changed
Swift upload using cli works, and using Chrome, Safari, Firefox.... Just to clarify, it is not working just for IE 11, May be related to: https://bugs.launchpad.net/horizon/+bug/1348404 deployed overcloud(controller and computes), using OSP-D and swift manually 3 swift proxies and 6 object data. (In reply to Jeremy from comment #2) > Swift upload using cli works, and using Chrome, Safari, Firefox.... > Just to clarify, it is not working just for IE 11, > > > May be related to: > https://bugs.launchpad.net/horizon/+bug/1348404 > > deployed overcloud(controller and computes), using OSP-D and swift manually > 3 swift proxies and 6 object data. This LP is fixed in Juno whilst this user is using a Kilo which probably means that something else happens here. I strongly recommend to close it as a documentation bug since nobody tested it with IE. (In reply to Sergey Gotliv from comment #7) > This LP is fixed in Juno whilst this user is using a Kilo which probably > means that something else happens here. I strongly recommend to close it as > a documentation bug since nobody tested it with IE. Agreed that LP is not what's happening here. However the customer has a requirement for IE11 and based on the upstream wiki/docs expectations were set that it would work. So we at least need to dig into this issue. The fact that the problem only occurs when "object name" is auto-filled, and works when the field is manually populated would seem to indicate this is not general failure of IE11 but rather something that could be fixed w/ a targetted code change. Can reproduce it locally. Can we get the specific versions of horizon and swift? You provided the manila versions which have nothing to do with object storage. Thanks! Seems that the fix upstream is not valid for IE11, as this can also be triggered on Liberty. (In reply to Dave Maley from comment #8) > (In reply to Sergey Gotliv from comment #7) > > This LP is fixed in Juno whilst this user is using a Kilo which probably > > means that something else happens here. I strongly recommend to close it as > > a documentation bug since nobody tested it with IE. > > Agreed that LP is not what's happening here. However the customer has a > requirement for IE11 and based on the upstream wiki/docs expectations were > set that it would work. So we at least need to dig into this issue. > > The fact that the problem only occurs when "object name" is auto-filled, and > works when the field is manually populated would seem to indicate this is > not general failure of IE11 but rather something that could be fixed w/ a > targetted code change. Actually this seems to be an issue with IE10,11 as they behave totally different from any other browsers, marking all fields as dirty as they are instantiated, thus the necessity for a workaround _only_ for IE11. Also, regarding the "support" for IE11, I would say that its pretty bad. The page linked hasnt been updated since juno and even there the status is set as "good?" which probably means that it hasnt been tested, nor there is any incentive upstream to test it. I dont think we should take that page as a source of truth as it doesnt seem to reflect the reality of the testing done on IE browsers :) Patch was merged. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1197 |
Created attachment 1146902 [details] Autofilled Description of problem: Unable to upload objects to object storage using Internet Explorer 11. This seems to be a bug related to the object name field. If object name is autofilled then upload is greyed out, if you change the field then it works. Please check attached screen shots. Version-Release number of selected component (if applicable): python-manila-2015.1.0-2.el7ost.noarch python-manilaclient-1.1.0-1.el7ost.noarch openstack-manila-ui-1.0.1-1.el7ost.noarch How reproducible: 100% Steps to Reproduce: 1.attempt to upload object to object storage without changing object name field Actual results: greyed out upload button Expected results: able to upload using button Additional info: