Bug 1436819

Summary: Build Configs in the openshift namespace do not show up in the options for editbuilds in webui unless "openshift" is manually added as the namespace
Product: OpenShift Container Platform Reporter: Eric Jones <erjones>
Component: WebsiteAssignee: Jessica Forrester <jforrest>
Status: CLOSED ERRATA QA Contact: Bing Li <bingli>
Severity: low Docs Contact:
Priority: medium    
Version: 3.4.1CC: aos-bugs, dlbewley, jforrest, jokerman, mmccomas, smunilla
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: The image stream tag picker was adding the openshift namespace to the list after the list was already sorted. Consequence: The openshift namespace appeared at the top of the list of namespaces for the image stream tag picker, which was confusing in long lists of namespaces if the user was expecting to find it alphabetically in the dropdown. Fix: The list of namespaces the user can pick from is now sorted after the openshift namespace is added to the list. Result: The list of namespaces a user can pick from when selecting an image stream tag for build configuration options will have openshift sorted alphabetically with the other namespaces the user can access.
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-10 05:20:02 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Eric Jones 2017-03-28 18:23:19 UTC
Description of problem:
As a user that has access to run `oc edit` on a build config stored in the openshift namespace I am unable to edit them from the WebUI unless I manually type "openshift" into the namespace field (will attach screenshots (privately) shortly).

Comment 2 Jessica Forrester 2017-03-29 13:27:32 UTC
It should always guarantee that the openshift namespace appears in that dropdown.
https://github.com/openshift/origin-web-console/blob/enterprise-3.4/app/scripts/directives/istagSelect.js#L75
Seems to be working fine for regular users, will try to reproduce specifically with a user that has view rights to the openshift namespace itself to see if that makes a difference.

Comment 5 dlbewley 2017-04-28 17:15:59 UTC
I've discovered the 'openshift' namespace does appear in the list. However, it is at the top of the list instead of inserted alphabetically. I think that is not obvious and is confusing for users with many projects.

Comment 6 Jessica Forrester 2017-05-01 14:17:30 UTC
The sorting issue will be fixed in https://github.com/openshift/origin-web-console/pull/1491

Comment 8 Bing Li 2017-05-31 03:19:39 UTC
Namespace can be sorted alphabetically:

OCP v3.6.79
kubernetes v1.6.1+5115d708d7

Move to verified.

Comment 10 errata-xmlrpc 2017-08-10 05:20:02 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/RHEA-2017:1716