Bug 2108339 - datasource does not provide timestamp when updated
Summary: datasource does not provide timestamp when updated
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Storage
Version: 4.10.2
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: 4.12.0
Assignee: Arnon Gilboa
QA Contact: Yan Du
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-18 21:42 UTC by joherr
Modified: 2023-01-24 13:39 UTC (History)
5 users (show)

Fixed In Version: v4.12.0-351
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-01-24 13:38:02 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github kubevirt containerized-data-importer pull 2381 0 None Merged Update DataSource LastTransitionTime when populated PVC is updated 2022-08-09 16:47:11 UTC
Red Hat Issue Tracker CNV-19908 0 None None None 2023-01-09 22:14:55 UTC
Red Hat Product Errata RHSA-2023:0408 0 None None None 2023-01-24 13:39:44 UTC

Description joherr 2022-07-18 21:42:51 UTC 
Description of problem:
The DataSource does not show a timestamp as to when it is updated. It only shows a timestamp for when it is initially populated.

Version-Release number of selected component (if applicable):
OpenShift 4.10.18
Virtualization 10.2

How reproducible:
always

Steps to Reproduce:
1. Create a imagestream
2. create an datacrontemplate in hyperconverged to populate a datasource
3. update container image the imagestreampoints to

Actual results:
The datasource updates, but  the status.conditions do not indicate it updated or changed. Only the pvc name changes.


Expected results:

To have a condition that provides a date/time when the DataSource is updated.
Comment 1 Jan Safranek 2022-07-19 08:07:22 UTC 
Moving to CNV
Comment 2 Yan Du 2022-08-16 08:52:30 UTC 
Test on CNV-v4.12.0-363, lastTransitionTime has been changed after updating dataImportCronTemplates

Before update:

-------8<------------
spec:
  source:
    pvc:
      name: custom-data-source-947541648d7f
      namespace: openshift-virtualization-os-images
status:
  conditions:
  - lastHeartbeatTime: "2022-08-16T04:28:51Z"
    lastTransitionTime: "2022-08-16T04:28:51Z"
    message: DataSource is ready to be consumed
    reason: Ready
    status: "True"
    type: Ready
  source:
    pvc:
      name: custom-data-source-947541648d7f
      namespace: openshift-virtualization-os-images

After update:

-------8<------------
spec:
  source:
    pvc:
      name: custom-data-source-6f58b5a089be
      namespace: openshift-virtualization-os-images
status:
  conditions:
  - lastHeartbeatTime: "2022-08-16T04:33:53Z"
    lastTransitionTime: "2022-08-16T04:33:53Z"
    message: DataSource is ready to be consumed
    reason: Ready
    status: "True"
    type: Ready
  source:
    pvc:
      name: custom-data-source-6f58b5a089be
      namespace: openshift-virtualization-os-images
Comment 6 errata-xmlrpc 2023-01-24 13:38:02 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 (Important: OpenShift Virtualization 4.12.0 Images security update), 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/RHSA-2023:0408
Note You need to log in before you can comment on or make changes to this bug.