Bug 1467941

Summary:	Refresh of ansible repostiory doesnot update the timestamp.
Product:	Red Hat CloudForms Management Engine	Reporter:	Neha Chugh <nchugh>
Component:	Providers	Assignee:	James Wong <jwong>
Status:	CLOSED NOTABUG	QA Contact:	Dave Johnson <dajohnso>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.8.0	CC:	gblomqui, jfrey, jhardy, obarenbo, sacpatil
Target Milestone:	GA
Target Release:	cfme-future
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-07-13 19:22:11 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	Ansible	Target Upstream Version:
Embargoed:

Description Neha Chugh 2017-07-05 14:47:55 UTC

Description of problem:
Refresh of ansible repostiory doesnot update the timestamp.

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

How reproducible:
Always

Steps to Reproduce:
1. Add a repository
2. Navigate to Ansible -> Repository -> click on any repository
3. Go to configuration -> refresh and after successful refresh the "Updated on" time will be same as the created on time.

Actual results:
Updated timestamp is same as created timestamp
Expected results:
It should update the timestamp

Additional info:

Comment 4 James Wong 2017-07-13 19:22:11 UTC

Hi Neha,

The updated timestamp is reflecting when Tower refreshes the repo. It is not MIQ's refresh timestamp.

What you see is expected.

Let's close this for now. We can reopen if there's other contradictory findings.

regards,
James