Description of problem: "Context Dir" and "Git Reference" are empty when clicking "advanced options" after clicking "Try Sample Repository" Version-Release number of selected component (if applicable): # oc version oc v3.7.9 kubernetes v1.7.6+a08f5eeb62 features: Basic-Auth GSSAPI Kerberos SPNEGO Server https://ose37-master:8443 openshift v3.7.9 kubernetes v1.7.6+a08f5eeb62 How reproducible: Always Steps to Reproduce: 1. Click "Add to project" and "Browse Catalog" 2. Click ".NET Core Builder Images 2.0" (or another template which has a sample repository) 3. Click Next 4. [attached image1] Click "Try Sample Repository", application name and git URL are filled. 5. Click "advanced options" Actual results: [attached image2] "Git Reference" and "Context Dir" are empty. For .NET Core 2.0 s2i image, Git Reference should be "dotnetcore-2.0" and "Context Dir" should be "app". (see attached image3) Once the user clicked "Try Sample Repository" at the dialog (image1), Web console no longer provides "Git Reference" and "Context Dir" Expected results: "Git Reference" and "Context Dir" are filled with the valid values. Additional info:
Created attachment 1360686 [details] image1
Created attachment 1360687 [details] image2
Created attachment 1360688 [details] image3
https://github.com/openshift/origin-web-catalog/pull/576
enterprise-3.7 catalog PR: https://github.com/openshift/origin-web-catalog/pull/579
3.7.z console PR: https://github.com/openshift/origin-web-console/pull/2551
v3.7.13 doesn't include the changes yet, will check in next update
Change to MODIFIED since fix not picked in OCP, and it couldn't be tested
*** Bug 1527638 has been marked as a duplicate of this bug. ***
Issue reported in this bug has been fixed in v3.7.35(OCP v3.9.1 also has the fix) Clicking "Try Sample Repository" in catalog wizard could fill "Context Dir" and "Git Reference" correctly if an imagestream has. Move to VERIFIED
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-2018:0636