Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

The 'origin' and 'divergence time' of a snap volume should be recorded.
- Initially divergence time is the same as the creation time.
- If origin is deleted; origin should be updated to grand parent (origin -> origin)
divergence time should be updated to the most recent of (divergence time, origin divergence time)

- Show when a snapshot diverged from each of it's ancestors (a tree view would be nice)

This needs to be moved out from 7.3 - we already do have infrastructure for tracking LV ancestry, but we still need a way to track when the snapshot got written first after its creation (and hence tracking the divergence times). Probably requires also support on kernel side.

*** Bug 1240555 has been marked as a duplicate of this bug. ***

(In reply to Peter Rajnoha from comment #1)
> This needs to be moved out from 7.3 - we already do have infrastructure for
> tracking LV ancestry, but we still need a way to track when the snapshot got
> written first after its creation (and hence tracking the divergence times).
> Probably requires also support on kernel side.

I don't see us adding kernel support for a feature like this.  If users can tell when they created a snapshot, that's probably good enough.  If it turns out that customers are clamoring for this feature, we can reopen the bug and determine the best way to proceed.