Dominik, since the registry-console image exists now, in order to verify this bug, what else do we need to do about it?

Hi Scott, 


We're not quite good at verifying image relative bugs, also we're stuck. Since component is set to Image Registry, could you please help change QA contact to relative QE who could check the image correctly ? if this image has something to do for web console, then we could help on console verification.

Hi Scott,

Some questions need your confrim?

1. On which registry should we check image registry-console-docker-3.3-1/openshift3/registry-console?

2. Once image checking passed, what should we check about web console? Is this related with https://github.com/openshift/openshift-ansible/pull/2318 ?

Yapei,

Yes, the installer should add functionality to install this registry console automatically and that's https://github.com/openshift/openshift-ansible/pull/2318 and https://github.com/openshift/openshift-ansible/pull/2235

The registry should be found at openshift3/registry-console it should be in the brew registry, I'll make sure that we add it to our scripts to sync it to registry.ops.openshift.com too.

Regarding QE owner, I think maybe Ying Zhou owns this? Assigning to them.

Scott:

Now the images has sync to  brew registry and registry.ops.openshift.com . When the related PR merged, will verify on web console.

Hi, changing status to MODIFIED since PR is still not merged.

Could assign back when it's ready to test

Hi, found PR is merged, please help change to ON_QA, sorry for the inconvenience

This has been merged into openshift-ansible-3.3.16-1.git.0.9ed3fd2.el7 the latest puddles and OSE v3.3.0.27 or newer images.

Marking this on QE manually since it is already in the errata.

Hi Dominik,

I would like to move this bug to VERIFIED when bug 1371423 resolved, is this OK?

Verification steps blocked by bug 1371423

bug 1371423 is verified and we test against new atomic registry env(set up with openshift-ansible-playbooks-3.3.22-1.git.0.6c888c2.el7.noarch & cockpit 0.114)

Several bugs found during our testing and already been recorded in bugs with summary started with '[atomic registry]', these bugs are likely to ship with 3.3.1


For this bug tracking atomic registry release in 3.3.0, I think i could move to VERIFIED since most function works well with 3.3.0 puddle and cockpit 0.114.

Functions we had tested: Login/Pull/Push
Installation Matrix: RPM & Container installation on RHEL Atomic Host 7.2


Please feel free to move back to ON_QA if any bug fix is going to ship with 3.3.0 and need to be checked