Description of problem:
The 'Last Analysis' field will always be different between any two drift states for a VM. Given a VM has experienced no workload drift (other than the Last Analysis field), the drift report will still show a change in the workload drift.
Requesting to have 'Last Analysis' field omitted from the Workload section of the Drift Analysis, as this will always cause the Workload to show a change between drifts.
I have labeled this an RFE as I am not sure if this was designed intentionally or not.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Take 2 snapshots of a VM one right after the other
2. Create a drift analysis with the drifts
3. View that the workload will always be different because of Last Analysis field
Workload is always different because of Last Analysis field
If no other drift is reported, other than Last Analysis, than the workload drift should show as no change.
New commit detected on ManageIQ/manageiq/master:
Author: Hilda Stastna <firstname.lastname@example.org>
AuthorDate: Mon May 14 12:27:39 2018 -0400
Commit: Hilda Stastna <email@example.com>
CommitDate: Mon May 14 12:27:39 2018 -0400
Excluding 'Last Analysis' field from Drift Workload Section
product/compare/vms.yaml | 3 -
1 file changed, 3 deletions(-)
Performed SSA twice on VM and saw 'Last Analysis' Drift section removed.
Verified Version: 126.96.36.199.20180705151325_ce4d2b5
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.