Bug 1724010
| Summary: | meet error "invalid parameter 'start' ..."" to a valid timestamp" when run queries on firefox 52 | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Junqi Zhao <juzhao> | ||||||||
| Component: | Management Console | Assignee: | Andrew Pickering <anpicker> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Junqi Zhao <juzhao> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 4.2.0 | CC: | amobrem, aos-bugs, jokerman, mmccomas, spadgett | ||||||||
| Target Milestone: | --- | Flags: | amobrem:
needinfo-
|
||||||||
| Target Release: | 4.2.0 | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2019-10-16 06:32:26 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: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Junqi Zhao
2019-06-26 02:51:07 UTC
Created attachment 1584556 [details]
no error on firefox 66 - ":kube_pod_info_node_count:"
Support for URLSearchParams's "USVString or sequence for init object" was added in Firefox 53 / Chrome 61 (see https://developer.mozilla.org/en-US/docs/Web/API/URLSearchParams/URLSearchParams#Browser_compatibility). We can easily avoid using that feature in this case. PR: https://github.com/openshift/console/pull/2227 Tested with Firefox 52.0 (64-bit) Run Query ":kube_pod_info_node_count:", no such error now, could show the graph correctly payload: 4.2.0-0.nightly-2019-08-08-002434 Created attachment 1601680 [details]
issue is fixed
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-2019:2922 |