Last updated date for a resource provisioned using an Operator is older than the Updated date against tasks for that resource

[mayur-raja]

The Last updated date against a resource provisioned using an Operator is older than the Updated date against tasks for that resource (it looks like the resource has been reconciled and the tasks re-run). Should the dates not match ? Surely it would make sense to show the latest last updated date against the resource too ?

Is this WAD (working as designed) or is this an OpenShift console bug please ?

If required, the issue should be very easy to recreate by creating a resource using any installed operator.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[mayur-raja]

/remove-lifecycle stale

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale