Bug 1467941 - Refresh of ansible repostiory doesnot update the timestamp.
Summary: Refresh of ansible repostiory doesnot update the timestamp.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.8.0
Hardware: All
OS: All
medium
medium
Target Milestone: GA
: cfme-future
Assignee: James Wong
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-05 14:47 UTC by Neha Chugh
Modified: 2020-09-10 10:51 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-13 19:22:11 UTC
Category: ---
Cloudforms Team: Ansible
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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
Note You need to log in before you can comment on or make changes to this bug.