UI prompt wrongly on environment dropdown even after changing the config.csv file

Question

UI prompt wrongly on environment dropdown even after changing the config.csv file

shanrd7 opened this issue 6 years ago · 11 comments

Answer 1 · 2019-03-07T06:24:40.000Z

@shanrd7 I have also opened a similar issue and @nareshv also agree upon it. He has opened couple of open issues to resolve this.
Meanwhile I did a work around of clearing my cookies and it resolves the issue temporarily.

Answer 2 · 2019-03-07T18:53:31.000Z

the code is available in v0.2.0 branch

Answer 3 · 2019-03-08T02:13:48.000Z

please download https://github.com/linkedin/cruise-control-ui/releases/tag/v0.2.0-pre and let us know how it works

Answer 4 · 2019-03-11T11:02:59.000Z

@nareshv the latest release still has the same issue as earlier. Like the UI though opened in new window, it kept showing details of old configs.
If I delete cookies and then try it looks good.

Answer 5 · 2019-03-11T13:49:02.000Z

@nareshv will incognito works?, because it doesn't work for me

Answer 6 · 2019-03-11T15:17:29.000Z

@shanrd7 , just to understand the issue correctly.

opened CCFE page
seeing all the dropdowns for CC endpoints
Made a backend change to config.csv
CC end point information in the dropdown in CCFE is not updated to match with latest config.csv

Is that correct ?

Right now, after step-3, can you select the ⟳ Refresh Config from UI Adminstration dropdown ? which is in 0.2.x

I have not added the fully automated refresh as its being tested.

Answer 7 · 2019-03-11T18:19:14.000Z

I have CCFE for dev environment as poc and in drop down kccpoc after that I have done it for prod environment changing the config.csv file as per prod and started the service, Somehow it still point to dev

Answer 8 · 2019-03-12T03:53:38.000Z

There are two config.csv in the git source tree.

Top level static/config.csv which is used only during the npm run dev phase
Production file dist/static/config.csv which is automatically created by copying top level static/config.csv as part of npm run build. This directory (dist) is what needs to be deployed under a webserver along with the correctly modified dist/static/config.csv

In order to confirm that the config.csv is deployed correctly under a given environment. you can also curl http://dev.example.com/static/config.csv & curl http://prod.example.com/static/config.csv

Depending on what you have deployed you should see the same contents here as its used in CCFE.

Answer 9 · 2019-03-12T09:01:37.000Z

@nareshv I have followed the exact process you have mentioned in wiki/docs. Even used your 2.x release. But still the CCFE would not refresh to the latest config.csv until I clear cookies.

Answer 10 · 2019-03-12T20:46:14.000Z

@chetann , we don't use cookies anywhere in CCFE. There is also a cache buster url param while making a call to the backend (http://host.example.com/static/config.csv?t=<random-unique-timestamp>) which should ensure the server to serve the most recent configuration file thats on disk.

If that doesn't happen i suspect, something to do with the webserver not reloading the disk contents automatically.

Just curious, which webserver is this ?

Answer 11 · 2019-05-30T00:58:17.000Z

closing this due to inactivity. please file a new one in case the problem persists.