Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1785613

Summary: Templates Export to git repo is failing with error : <branch> did not find file known to git
Product: Red Hat Satellite Reporter: Jitendra Yejare <jyejare>
Component: Templates PluginAssignee: Ondřej Pražák <oprazak>
Status: CLOSED ERRATA QA Contact: Ondrej Gajdusek <ogajduse>
Severity: high Docs Contact:
Priority: high    
Version: 6.7.0CC: mhulan, oprazak, pcreech
Target Milestone: 6.7.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tfm-rubygem-foreman_templates-7.0.6-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-14 13:28:08 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:
Bug Depends On:    
Bug Blocks: 1778146    

Description Jitendra Yejare 2019-12-20 13:01:16 UTC
Description of problem:
"Export to git {Note: before that, I did purging}" is failing with error :
Error : "git '--git-dir=/tmp/d20191218-16244-1zdqb6/.git' '--work-tree=/tmp/d20191218-16244-1zdqb6' checkout 'master'  2>&1:error: pathspec 'master' did not match any file(s) known to git."

Version-Release number of selected component (if applicable):
Satellite 6.7 snap 6

How reproducible:
Always

Steps to Reproduce:
1. Attempt to export templates from satellite to any git repository. (Make sure you have added foreman public key to the repo already)

Actual results:
"Export to git {Note: before that, I did purging}" is failing with error :
Error : "git '--git-dir=/tmp/d20191218-16244-1zdqb6/.git' '--work-tree=/tmp/d20191218-16244-1zdqb6' checkout 'master'  2>&1:error: pathspec 'master' did not match any file(s) known to git."

Expected results:
The successful template export to Git repo.

Additional info:

Comment 5 Ondřej Pražák 2020-01-10 09:37:17 UTC
Created redmine issue https://projects.theforeman.org/issues/28716 from this bug

Comment 7 Bryan Kearney 2020-01-10 15:06:50 UTC
Upstream bug assigned to oprazak

Comment 8 Bryan Kearney 2020-01-10 15:06:52 UTC
Upstream bug assigned to oprazak

Comment 9 Bryan Kearney 2020-01-13 19:06:35 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/28716 has been resolved.

Comment 13 errata-xmlrpc 2020-04-14 13:28:08 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/RHSA-2020:1454

Comment 14 Jitendra Yejare 2021-11-08 13:39:37 UTC
Resetting the QA assignee to set the `qe_test_coverage` based on current test coverage and decide on the flag/implementation if not covered.

Comment 15 Ondrej Gajdusek 2021-11-30 10:03:31 UTC
Pending PR that adds the coverage: https://github.com/SatelliteQE/robottelo/pull/9199