Hide Forgot
Description of problem: Access to registry web console in other tabs fails and shows (see attachment): Couldn't connect to server Couldn't find running API server Reconnect Clicking Reconnect also fails and gives same prompt. But clicking links in the first tab still work. Even if close all tabs (without browser closed), access again, still fail. Have to in the fail page click username --> logout, then login again, only now it can access successfully. Or have to open another browser to login and access successfully Version-Release number of selected component (if applicable): openshift3/registry-console:3.3 How reproducible: Always Steps to Reproduce: 1. Input registry URL in address bar, login to registry web console 2. After login successfully, open a new browser tab, input registry URL again. Actual results: 2. Fail and prompt: Couldn't connect to server Couldn't find running API server Reconnect Expected results: 2. Should access successfully on other tabs in the browser Additional info:
Created attachment 1198158 [details] Access in another tab fails
This was fixed in 0.117.
cockpit 118-2 has been released. We have created image openshift3/registry-console:3.3-4 that has the updated rpms and should fix this problem.
Verified with openshift3/registry-console:3.3-4 with Cockpit Version 118: $ docker images | grep registry .../openshift3/registry-console 3.3-4 445ef31dcaaf 10 hours ago 223.8 MB Fixed. Now can access registry console in other Tab
If the registry console is already deployed, how should admins update to use the latest image? I see in the registry-console deploymentConfig it specifies the general 3.3 tag: image: registry.access.redhat.com/openshift3/registry-console:3.3 imagePullPolicy: IfNotPresent And it has a ConfigChange trigger: triggers: - type: ConfigChange So I guess just importing the 3.3 tag wouldn't be enough since the dc wouldn't actually change? $ oc import-image -n default registry-console:3.3 Should an admin just manually update the tag version in the "image" field of the dc from "3.3" to "3.3-4", like we do for manual registry or router updates? I.e., https://docs.openshift.com/container-platform/3.3/install_config/upgrading/manual_upgrades.html#upgrading-the-registry Side note, when I tried importing w/o specifying a tag (defaulting to "latest"), it failed with: error: the tag "latest" does not exist on the image stream - choose an existing tag to import or use the 'tag' command to create a new tag
I think Troy Dawson is a better source for the release mechanics of the shipped images.
I looked and we should have a :latest :3.3 and :3.3-4 tags, and they should all be pointing to the same image. That part will be in place when this is fixed. I believe Alex is asking what's going to actually trigger the running registry-console to actually use the new image.
Confirmed w/ aweiteka via IRC that we'll follow the "bump the 'image' field / let ConfigChange auto-trigger new delpoyment" method for upgrading, same as we do for registry and router deployments.
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:2777