Bug 1710206
| Summary: | The "Created time" in the federation operator ui is not correct | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Qin Ping <piqin> |
| Component: | Federation | Assignee: | Sohan Kunkerkar <skunkerk> |
| Status: | CLOSED ERRATA | QA Contact: | Qin Ping <piqin> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.1.0 | CC: | bbennett, bmcelvee, calfonso, pmorie |
| Target Milestone: | --- | ||
| Target Release: | 4.2.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-10-16 06:28:53 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Qin Ping
2019-05-15 05:53:02 UTC
There is not great guidance for what this value is actually supposed to represent. Would you expect: - The date the actual operator was originally created - The date the actual operator was originally published - The date that the operator was changed to the most recent version I think these are all valid choices but the documentation isn't especially clear: https://github.com/operator-framework/community-operators/blob/master/docs/required-fields.md What do you think it should be? I prefer "The date that the operator was changed to the most recent version". This is fix in the v0.1.0 CSV description. Verified with kubefed-operator v0.1.0 Does this bug require doc text? The Doc Type/Text field is not currently set. Thanks! 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. https://access.redhat.com/errata/RHBA-2019:2922 |