Description of problem: Git import detection does not happen for private repositories even when secrets are provided. Version-Release number of selected component (if applicable): 4.9 How reproducible: Always Steps to Reproduce: 1. Navigate to +Add > git import 2. Enter a private git repository 3. In advanced git options create a secret with personal access token and select it Actual results: Import strategy detection should happen. Expected results: Import strategy detection does not happen.
Hello, since 4.9 this happens for us too, also for public repos without authentication. Creating BuildConfigs via "oc new-app https://git-url --allow-missing-images --source-secret=<secret> is working fine.
Hi David, This bug is about import detection not working for private repositories, but you might be facing a different issue if detection for public repositories is affected. Can you please elaborate on the issue you face, or file a new bug for it?
Verified on build version: 4.11.0-0.nightly-2022-03-20-160505 Browser version: Chrome 99
Have any update for this bug?
This bug is fixed for 4.11, 4.10 backport progress can be tracked with https://bugzilla.redhat.com/show_bug.cgi?id=2057507
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 (Important: OpenShift Container Platform 4.11.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-2022:5069