Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-11832

Git repos held into a "main" default banch instead of "master" default branch cannot get pulled

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • ACM 2.10.0
    • DevOps
    • None
    • False
    • None
    • False
    • Moderate
    • No

      Description of problem:

      When using a git repo with the new "main" default branch type, an error can be raised while replicating the repository.

      Version-Release number of selected component (if applicable):

      RHACM 2.10.3

      MCE - 2.5.3

      gitops 1.12.2

      How reproducible:

      not attempted in lab, customer environment able to reproduce easily

      Steps to Reproduce:

      1. create a new git repo using "main" as a branch name
      2. use it to host a gitops policy project
      3. deploy it to managed clusters with RHACM

      Actual results:

      An error is raised syncing the repo. The one in the attempt had a kustomize.yaml and raised a "entry not found" error.

      Expected results:

      the repo does not fail to download or raises a better error on the cause for the failure to clone the repo

      Additional info:

      • the environment affected was using Atlassian v 0.19.
      • when creating a new project with "master" as a default branch and the same content the project did not fail to get cloned

              Gurney.Buchanan@ibm.com Gurney Buchanan
              rhn-support-fdewaley Felix Dewaleyne
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: