Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1635809

Summary: [osp14] config download tarball getting added to git repo
Product: Red Hat OpenStack Reporter: James Slagle <jslagle>
Component: openstack-tripleo-commonAssignee: James Slagle <jslagle>
Status: CLOSED ERRATA QA Contact: Gurenko Alex <agurenko>
Severity: medium Docs Contact:
Priority: medium    
Version: 14.0 (Rocky)CC: mburns, slinaber
Target Milestone: betaKeywords: Triaged
Target Release: 14.0 (Rocky)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-common-9.3.1-0.20180923215327.d22cb3e.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-11 11:53:35 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 James Slagle 2018-10-03 17:48:06 UTC 
The tarball of the config-download output that we put into the overcloud-config container is getting added to the git repo we create for the config-download contents.

We have code to add *.tar.gz to .gitignore, however when we use GitPython and run repo.index.add, this defaults to using force=True which the equivalent of git add -f, which adds even ignored files to the index.

The docs at
https://gitpython.readthedocs.io/en/stable/reference.html#git.index.base.IndexFile.add

actually say that the force keyword argument doesn't currently work.

So as a workaround we'll need to use the GitCmd interface to run a git command directly.
Comment 4 Gurenko Alex 2018-12-17 12:49:52 UTC 
Verified on puddle 2018-12-14.1

openstack-tripleo-common-9.4.1-0.20181012010884.el7ost.noarch
Comment 6 errata-xmlrpc 2019-01-11 11:53:35 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/RHEA-2019:0045