Bug 1724010 - meet error "invalid parameter 'start' ..."" to a valid timestamp" when run queries on firefox 52
Summary: meet error "invalid parameter 'start' ..."" to a valid timestamp" when run qu...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.2.0
Assignee: Andrew Pickering
QA Contact: Junqi Zhao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-26 02:51 UTC by Junqi Zhao
Modified: 2019-10-31 15:47 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-16 06:32:26 UTC
Target Upstream Version:
Embargoed:
amobrem: needinfo-


Attachments (Terms of Use)
error on firefox 52 - ":kube_pod_info_node_count:" (158.78 KB, image/png)
2019-06-26 02:51 UTC, Junqi Zhao
no flags Details
no error on firefox 66 - ":kube_pod_info_node_count:" (166.63 KB, image/png)
2019-06-26 02:52 UTC, Junqi Zhao
no flags Details
issue is fixed (80.41 KB, image/png)
2019-08-08 04:17 UTC, Junqi Zhao
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 2227 0 None None None 2019-08-07 13:50:54 UTC
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:32:36 UTC

Description Junqi Zhao 2019-06-26 02:51:07 UTC
Created attachment 1584555 [details]
error on firefox 52 - ":kube_pod_info_node_count:"

Description of problem:
Firefox 52.0.2 (64-bit), login cluster console, click "Monitoring -> Query Browser" and input ":kube_pod_info_node_count:" in the search filed and click "Run Queries", there is error "invalid parameter 'start' ..."" to a valid timestamp" in page.

debug in console, the request url is
https://console-openshift-console.apps.qe-juzhao.qe.devcluster.openshift.com/api/prometheus/api/v1/query_range?0=%5B%22end%22%2C%221561516054.34%22%5D&1=%5B%22start%22%2C%221561514254.34%22%5D&2=%5B%22step%22%2C%226%22%5D&query=%3Akube_pod_info_node_count%3A&timeout=5s

decode it, it is
https://console-openshift-console.apps.qe-juzhao.qe.devcluster.openshift.com/api/prometheus/api/v1/query_range?0=["end","1561516054.34"]&1=["start","1561514254.34"]&2=["step","6"]&query=:kube_pod_info_node_count:&timeout=5s


It does not have this issue in higher version, such as firefox 66.0.4 (64-bit)
the request url is:
https://console-openshift-console.apps.qe-juzhao.qe.devcluster.openshift.com/api/prometheus/api/v1/query_range?end=1561516301.659&start=1561514501.659&step=6&query=:kube_pod_info_node_count:&timeout=5s


Version-Release number of selected component (if applicable):
Firefox 52.0.2 (64-bit)
payload: 4.2.0-0.nightly-2019-06-25-222454

How reproducible:
Always

Steps to Reproduce:
1. See the description part
2.
3.

Actual results:
meet error "invalid parameter 'start' ..."" to a valid timestamp" when run queries on firefox 52

Expected results:
Should not have error

Additional info:
We should define the lowest browser version we should test, since we can test on every version

Comment 1 Junqi Zhao 2019-06-26 02:52:05 UTC
Created attachment 1584556 [details]
no error on firefox 66 - ":kube_pod_info_node_count:"

Comment 5 Andrew Pickering 2019-07-31 04:45:26 UTC
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

Comment 7 Junqi Zhao 2019-08-08 04:16:36 UTC
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

Comment 8 Junqi Zhao 2019-08-08 04:17:44 UTC
Created attachment 1601680 [details]
issue is fixed

Comment 9 errata-xmlrpc 2019-10-16 06:32:26 UTC
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


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