Hide Forgot
Description of problem: Configured loggingPublicURL in master-config to enable showing "View Archive" on web console. Check the "View Archive" link on pod page's Logs Tab and monitoring page's pod logs. The link is not seen there. Version-Release number of selected component (if applicable): openshift v1.5.0-alpha.0+3b2bbe5 kubernetes v1.4.0+776c994 etcd 3.1.0-rc.0 How reproducible: Always Steps to Reproduce: 1.Configure loggingPublicURL in master-config to enable showing "View Archive" on web console. 2.Create app from image on web console. Make sure pods are running. 3.Check "View Archive" link on pod page's Logs Tab and monitoring page's pod logs. Actual results: 3. The link is not seen there Expected results: 3. The link should be shown there. Additional info:
Oh, after configuring loggingPublicURL in master-config and restarting master, it needs **logout** and login again to web console to see the "View Archive" link. So it is better to note this in Documentation. Seems https://docs.openshift.org/latest/install_config/aggregate_logging.html#aggregate-logging-kibana has no note about this. Moving to Documentation ... Thank you!
Does refreshing the page work as well?
Refreshing works. However, navigating does not work, below is comparison: a. First open 2 tabs called tab1 and tab2 in browser to visit pod Logs page b. Second, configure master loggingPublicURL and restart master. c. In browser tab2, refresh page, the View archive link is shown. d. But in browser tab1, DON'T refresh page, just navigate to other page, e.g. overview page, then navigate back by clicking Applications --> Pods --> the pod --> Logs, the View archive link is NOT shown. In summary, user needs explicitly refresh or logout/login. The bug was reported when step d was hit.
Right, I'd expect only refresh or logout to work. We don't fetch the config on every page because it changes very rarely. Note that this is the case for any master config change, not just logging URL. If we update the docs, we probably say to refresh the browser rather than logging out. We should also mention it for any master config change that impacts the console (assetConfig, logging URL, metrics URL, extensions).
> ... We should also mention it for any master config change that > impacts the console (assetConfig, logging URL, metrics URL, extensions) Thanks for the clarification. Searched the docs website, e.g. https://docs.openshift.org/latest/install_config/web_console_customization.html , seems there is no note about this (Though there is one only sentence "When set, the web console reloads any changes to existing extension script or stylesheet files when you refresh the page in your browser", which is about "extensionDevelopment: true", RATHER than the point we talked) I'd like to keep the docs as it is, considering the note may have not much value.