Bug 1999627

Summary: Import from git flow doesn't recommend build image when a Dockerfile exists
Product: OpenShift Container Platform Reporter: divgupta
Component: Dev ConsoleAssignee: divgupta
Status: CLOSED ERRATA QA Contact: spathak <spathak>
Severity: low Docs Contact:
Priority: medium    
Version: 4.9CC: aos-bugs, mifiedle, nmukherj, viraj
Target Milestone: ---   
Target Release: 4.9.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-10-18 17:50:37 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 divgupta 2021-08-31 13:03:46 UTC 
Description of problem:
When the user imports an application from git, the new git import flow recommends automatically the Dockerfile flow also if the application contains a well known builder image format. That's fine!

But when the user selects "Edit Import Strategy" and switches to "Builder Image" it would be cool to recommend an image if the information is available (which works fine earlier).

How reproducible: Always

Steps to Reproduce:
1.Open developer console > Add page > Import from Git
2.Enter a git URL which has a Dockerfile and where the builder image is known (for example contains a package.json for node.js). For example: https://github.com/jerolimov/nodeinfo
3.The validation should pass and the form recommends "Dockerfile" as import strategy.
4.Select "Edit Import Strategy" and switches to "Builder Image"

Actual results:
No builder image is preselected

Expected results:
The right builder image should be preslected (for the repo above "Node.js")
Comment 3 Vikram Raj 2021-09-08 15:49:40 UTC 
Verified it on 4.9.0-0.nightly-2021-09-07-201519. And it works as expected.
Comment 6 errata-xmlrpc 2021-10-18 17:50:37 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 (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), 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/RHSA-2021:3759