-
Bug
-
Resolution: Done-Errata
-
Normal
-
None
-
False
-
-
False
-
QE - Ack
-
oadp-operator-bundle-container-1.3.1-42
-
ToDo
-
-
-
0
-
Very Likely
-
0
-
None
-
Unset
-
Unknown
-
No
- add UI rendering to fields https://github.com/openshift/console/blob/master/frontend/packages/operator-lifecycle-manager/src/components/descriptors/reference/reference.md
- add all maintainers to operator list https://github.com/openshift/oadp-operator/blob/master/config/manifests/bases/oadp-operator.clusterserviceversion.yaml#L365
- <Rayford> should we consider a list address similar to MTA’s approach here?[ |https://github.com/openshift/oadp-operator/blob/master/config/manifests/bases/oadp-operator.clusterserviceversion.yaml#L39]
- add more keywords https://github.com/openshift/oadp-operator/blob/master/config/manifests/bases/oadp-operator.clusterserviceversion.yaml#L358
- add more categories? https://github.com/openshift/oadp-operator/blob/master/config/manifests/bases/oadp-operator.clusterserviceversion.yaml#L6 (first filter in OperatorHub UI)
- <Rayford> operator-framework/api operatorhub.go’s validCategories
- change order of OADP CRDs (Provided APIs in UI) https://github.com/openshift/oadp-operator/blob/master/bundle/manifests/oadp-operator.clusterserviceversion.yaml#L187
- problem: the change does not persist after `make bundle` and is not applied (if trying to run without `make bundle`) and the UI team have not considered this problem, I think (should we open an issue?)
- talk with forum-ocp-console about OCP UI https://redhat-internal.slack.com/archives/C6A3NV5J9/p1696629223714509
- change order of fields in form view? https://github.com/dora-metrics/pelorus/pull/869
- Comment<Michal>: search about a way of showing errors messages to users (like backup failed)
- clones
-
-
- Closed
-
- links to
-
RHSA-2023:112677
OpenShift API for Data Protection (OADP) 1.3.0 release advisory
-
RHSA-2024:126995
OpenShift API for Data Protection (OADP) 1.3.1 security and bug fix update
- mentioned on
(2 links to, 2 mentioned on)
[OADP-3055] UI/UX improvements for the OADP operator
Sachin Singla
added a comment - Verified with OADP 1.3.1-57
Reviewed all the descriptions for the objects. They don't require any further updates. Screenshot attached.
The last point is to render all the fields of the DPA in the UI, however I am unsure if we miss any.
good progress here, rhn-engineering-mpryc let's try to close this out since it's very achievable.
I think the following categories OADP should be in:
- Cloud Provider
- integrations with various cloud providers to facilitate backup and restore operations
- Developer Tools
- used in development and operations workflows for managing backups and restores
- Modernization & Migration
- used during migration and modernization efforts when moving applications to and from OCP clusters
- OpenShift Optional
- current category, won't be changing that
- Storage
- closely associated with storage-related operations
Since the problem described in this issue should be resolved in a recent advisory, it has been closed.
For information on the advisory (Moderate: OpenShift API for Data Protection (OADP) 1.3.1 security and bug fix 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-2024:1859