Bug 1394194

Summary:	[CFME 5.7 beta] Removing tags from a github-hosted automate domain repository doesn't remove them from the list of available tags to import into automate
Product:	Red Hat CloudForms Management Engine	Reporter:	Peter McGowan <pmcgowan>
Component:	Automate	Assignee:	mkanoor
Status:	CLOSED WONTFIX	QA Contact:	Dmitry Misharov <dmisharo>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	5.7.0	CC:	cpelland, jhardy, mkanoor, obarenbo, tfitzger
Target Milestone:	GA
Target Release:	cfme-future
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	automate:git
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	CFME Core	Target Upstream Version:

Description Peter McGowan 2016-11-11 11:31:36 UTC

Description of problem:
I added a number of tagged commits to an upstream git repository, and used this as an import URL for a git-hosted automate domain. Automate sees all of the tags, and lets me import from any of them. I then removed the two most recent commits and tags from the source github repository, but they are still visible to automate if I attempt a domain refresh.

I have noticed that new tags are visible to automate if I attempt a domain refresh, so I would expect deleted tags to no longer be visible.

Version-Release number of selected component (if applicable):
5.7.0.10-beta3.20161109111947_9a61b18 

How reproducible:
Every time

Steps to Reproduce:
1. Create a github-hosted repository containing a correctly formatted automate domain. This repository should contain two or more tagged commits.
2. Import the git-hosted domain into automate. Note that the tags are visible to select from in the import dialog
3. Delete the most recent tagged commit and tag from the source github repository
4. In automate explorer, click on the domain and click Configuration -> Refresh with a new branch or tag
5. Observe the list of available tags to import from 

Actual results:
The deleted tag is still visible

Expected results:
The deleted tag should no longer be visible in the list of tags to refresh from

Additional info:

Comment 2 mkanoor 2017-01-03 16:06:21 UTC

Had discussions with Jason on this topic. One of his concerns was the model imported into Postgres could be at an older tag, which could get deleted in the remote. That doesn't mean we delete the model with the old tag from Postgres. This was changed into a non blocker bug awaiting further discussions.

Comment 3 Josh Carter 2018-10-02 14:33:07 UTC

Dear customer, 

The CloudForms team is reviewing the current CloudForms Bug(defect) backlog in order to target engineering efforts. We are closing any bugs for versions that no longer have an active errata stream or that have hit their age limit. We are committing to better management of the backlog as we move forward. If you have an bug that you are still able to reproduce on a current version of CloudForms please open a new bug. 

If you have any concerns about this, please let us know.

Thanks and regards!

Comment 4 Josh Carter 2018-10-02 14:33:54 UTC

Dear customer, 

The CloudForms team is reviewing the current CloudForms Bug(defect) backlog in order to target engineering efforts. We are closing any bugs for versions that no longer have an active errata stream or that have hit their age limit. We are committing to better management of the backlog as we move forward. If you have an bug that you are still able to reproduce on a current version of CloudForms please open a new bug. 

If you have any concerns about this, please let us know.

Thanks and regards!

Comment 5 Josh Carter 2018-10-02 14:35:20 UTC

Dear customer, 

The CloudForms team is reviewing the current CloudForms Bug(defect) backlog in order to target engineering efforts. We are closing any bugs for versions that no longer have an active errata stream or that have hit their age limit. We are committing to better management of the backlog as we move forward. If you have an bug that you are still able to reproduce on a current version of CloudForms please open a new bug. 

If you have any concerns about this, please let us know.

Thanks and regards!