SC-NAME:
New:

<a tabindex="-1" data-ouia-component-type="PF4/DropdownItem" data-ouia-safe="true" data-ouia-component-id="OUIA-Generated-DropdownItem-1" aria-disabled="false" class="pf-c-dropdown__menu-item"><div><span class="co-resource-item"><span class="sr-only">SC</span><span class="co-m-resource-icon" title="StorageClass">SC</span>thin</span></div><div><span class="text-muted">(default) | kubernetes.io/vsphere-volume</span></div></a>

Old:
id="thin-link"

data-test-id="dropdown-button" attribute deleted on OSD size

<button id="pf-select-toggle-id-32" aria-labelledby="requested-capacity-dropdown pf-select-toggle-id-32" aria-expanded="false" aria-haspopup="listbox" type="button" class="pf-c-select__toggle" aria-label="Options menu"><div class="pf-c-select__toggle-wrapper"><span class="pf-c-select__toggle-text">2 TiB</span></div><span class="pf-c-select__toggle-arrow"><svg fill="currentColor" height="1em" width="1em" viewBox="0 0 320 512" aria-hidden="true" role="img" style="vertical-align: -0.125em;"><path d="M31.3 192h257.3c17.8 0 26.7 21.5 14.1 34.1L174.1 354.8c-7.8 7.8-20.5 7.8-28.3 0L17.2 226.1C4.6 213.5 13.5 192 31.3 192z"></path></svg></span></button>

Deployment type:
new:
<button id="pf-select-toggle-id-10" aria-labelledby=" pf-select-toggle-id-10" aria-expanded="false" aria-haspopup="listbox" type="button" class="pf-c-select__toggle" aria-label="Options menu"><div class="pf-c-select__toggle-wrapper"><span class="pf-c-select__toggle-text">Full deployment</span></div><span class="pf-c-select__toggle-arrow"><svg fill="currentColor" height="1em" width="1em" viewBox="0 0 320 512" aria-hidden="true" role="img" style="vertical-align: -0.125em;"><path d="M31.3 192h257.3c17.8 0 26.7 21.5 14.1 34.1L174.1 354.8c-7.8 7.8-20.5 7.8-28.3 0L17.2 226.1C4.6 213.5 13.5 192 31.3 192z"></path></svg></span></button>
old:
input[id="bs-existing"]

OSD size changed:
New:
<button id="pf-select-toggle-id-16" aria-labelledby="requested-capacity-dropdown pf-select-toggle-id-16" aria-expanded="true" aria-haspopup="listbox" type="button" class="pf-c-select__toggle" aria-label="Options menu"><div class="pf-c-select__toggle-wrapper"><span class="pf-c-select__toggle-text">0.5 TiB</span></div><span class="pf-c-select__toggle-arrow"><svg fill="currentColor" height="1em" width="1em" viewBox="0 0 320 512" aria-hidden="true" role="img" style="vertical-align: -0.125em;"><path d="M31.3 192h257.3c17.8 0 26.7 21.5 14.1 34.1L174.1 354.8c-7.8 7.8-20.5 7.8-28.3 0L17.2 226.1C4.6 213.5 13.5 192 31.3 192z"></path></svg></span></button>

Old:

    "512": ('button[data-test-dropdown-menu="512Gi"]', By.CSS_SELECTOR),
    "2048": ('button[data-test-dropdown-menu="2Ti"]', By.CSS_SELECTOR),
    "4096": ('button[data-test-dropdown-menu="4Ti"]', By.CSS_SELECTOR),

Deployment type:
New:
<input name="backing-storage-radio-group" id="bs-existing" class="pf-c-radio__input" type="radio" aria-invalid="false" data-ouia-component-type="PF4/Radio" data-ouia-safe="true" data-ouia-component-id="OUIA-Generated-Radio-1" value="existing" checked="">
OLD:

    "choose_lso_deployment": ('input[id="bs-local-devices"]', By.CSS_SELECTOR),```
**********************************************************************************************************************

OCP Version:
OCP Version: 4.11.0-0.nightly-2022-06-04-014713
ODF Version: 4.11.0-85

https://docs.google.com/document/d/1-yHsQwbf7aAGnxMr8Ycg0bJx2NPT3Z-60L2ZYS1b6sI/edit

https://v4.webpack.js.org/loaders/file-loader/
https://webpack.js.org/guides/asset-modules/

Currently used:
https://github.com/red-hat-storage/odf-console/blob/master/packages/odf/components/topology/Topology.tsx#L502
https://github.com/red-hat-storage/odf-console/blob/master/packages/mco/components/mco-dashboard/data-policy/dr-dashboard.tsx#L163

Refer: https://reactjs.org/docs/context.html#contextprovider
All consumers that are descendants of a Provider will re-render whenever the Provider’s value prop changes.
Whenever Provider’s value prop changes all the child FCs will get re-rendered (irrespective of whether a child is a consumer of the context or not). This will cause unnecessary re-renders for those FCs which are not consuming any state from the context.
To avoid that use composition: create a separate FC which will provide the context and pass the consumer FCs as its "children".
example: https://github.com/openshift/console/blob/master/frontend/public/components/app.jsx#L241

• Breadcrumb missing "link" like styling.
• FieldLevelHelp on aligned with card title.
• Status icon on properly aligned with card title (status and details card).
• "Utilization" card header size is different from other card's title.
• Chart legends + corresponding text are missing.
• Add capacity modal: "Raw capacity" is not center-ed and x 3 replicas is rendered in separate row.
• Configure performance dropdown.
• Spacing between buttons.
• Multus radio and TP badge.

Make StorageClassProvisioners enums to help with dealing with them in multiple places efficiently.
We could come up with utility functions to help users filter provisioners easily.

there are 2 different directories: i18n-scripts & scripts
structure should be:

scripts

generatePluginPackage.ts
i18n

SelectorInput (https://github.com/red-hat-storage/odf-console/blob/master/packages/shared/modals/Selector.tsx#L173): used in add labels modal and apply-policy (mco) modal.

Priority of issue is "low" for now, still it is an anti-pattern and may cause bug moving forward if this component is used at multiple places.
Check demo: https://codesandbox.io/s/m3w9zn1z8x (same case can happen with SelectorInput as well)
Refer: https://reactjs.org/blog/2018/06/07/you-probably-dont-need-derived-state.html#common-bugs-when-using-derived-state

While providing more input in EditLabelModel dialog, it keeps stacking letters or overprinting on the control buttons without expanding the dialog.

co- classes are defined in console project and can break at any time. We need to remove dependency on them and maintain our own CSS classes for long term stability.

Check: openshift/console@e026b15.
Needs a bit of investigation whether it is really needed or not.

Add Capacity Modal for CSVs should be pushed from this codebase for ODF 4.10

Currently we are setting this setODFflag to true however we improve here by setting the value after checking for the class definition or custom resource definition found or not.

https://github.com/red-hat-storage/odf-console/blob/master/plugins/mco/console-plugin.json#L14

[user@localhost packages]$ yarn i18n
yarn run v1.22.10
$ i18next "src/**/*.{js,ts,tsx}" [-oc] -c i18next-parser.config.js

  i18next Parser
  --------------
  Input:  src/**/*.{js,ts,tsx}, [-oc]
  Output: locales/$LOCALE/$NAMESPACE.json


  Stats:  0 files were parsed
Done in 0.44s.

0 files were parsed even though text has being externalized at multiple places.

This:

Reference: https://github.com/openshift/origin/blob/e6728e5e1d97886ba122ecca731716fc4d6e9ebf/LICENSE#L179

Currently only "mco" is using "default.conf" file during downstream build (image).
For "odf", it is now injected by the "odf-operator": red-hat-storage/odf-operator#305

We need to make similar changes for the "odf-multicluster-orchestrator": https://github.com/red-hat-storage/odf-multicluster-orchestrator as well and remove this "default.conf" file from this repo.

check: openshift/console@79c7bbb

useODFNamespace and useODFSystemFlags are 2 hooks at store info to the redux, add a documentation regarding the same and their general usage.

Need to add steps on how to perform (locally):

• end-to-end testing.

• unit testing.

example:

Key should be "namespace" not "ns" else useK8sWatchResource will return resources in every namespace.
Check for all such instances for useK8sWatchResource and fix at all places (if found at other places).

Following texts need to be externalized

• Create StorageSystem
• No StorageSystem found

For more details: https://issues.redhat.com/browse/RHSTOR-4515

• "Ready" label and close button overlapping in sidebar.
• No option to drill down the node.
• Search bar is too long and "Expand" button is rendered in separate row.

#854 >> reverted to ODF 4.13 as current 4.14 (which corresponds to master) has some issues.
To make ODF 4.13 work had to revert back to http server as well because ODF 4.13 do not have privileges config to work with "nginx-unprivileged" (was added for 4.14 only).

Once we move to ODF 4.14 for CI, we need to move back to nginx as well.

#862

Details: #836 (comment)

Refer: https://react.dev/learn/you-might-not-need-an-effect#fetching-data

We don't have such clean-ups for:
https://github.com/red-hat-storage/odf-console/blob/master/packages/shared/src/hooks/useK8sList.ts
https://github.com/red-hat-storage/odf-console/blob/master/packages/shared/src/hooks/k8s-get-hook.ts
https://github.com/red-hat-storage/odf-console/blob/master/packages/shared/src/hooks/custom-prometheus-poll/use-url-poll.ts

The way we are currently using these hooks in our repo, most probably we are safe for now as arguments passed to the dependency list of the useEffect are mostly static throughout the lifecycle of the component, but generic hooks should be agnostic of such assumptions.

For more details: https://issues.redhat.com/browse/RHSTOR-4531

https://github.com/red-hat-storage/odf-console/blob/master/.github/workflows/frontend-build.yml

add build step for mco as well, just like we have for odf currently.

"Block and file >> Details >> Service name" this link redirects to operator details page, add a test case to verify this.

Severity: Medium
Priority: Low

Current behaviour (checked on OCP/MCO 4.15):
Request URL: https://<OCP_BASE_URL>/api/plugins/odf-multicluster-console/exposed-features-chunk.js

Response headers:

content-type: application/javascript
x-content-type-options: nosniff

application/javascript is considered to be a legacy JavaScript MIME type but is still a valid one for now. Proper MIME type for JavaScript according to current HTML spec is text/javascript.

Refer: openshift/console#13637 (comment) for more details.

No need to "await" here: https://github.com/red-hat-storage/odf-console/blob/master/packages/mco/features.ts#L130
If we do, "intervalId" (here: https://github.com/red-hat-storage/odf-console/blob/master/packages/mco/features.ts#L131) will not be set until above "await" resolves, which will eventually lead to "featureDetector" be executed once again.
Without "await", "intervalId" will be set immediately and as soon as "featureDetector" gets resolved for the first time it will clear the interval as well (preventing callback in "setInterval" from being executed).

Node 18.18.0(https://nodejs.org/dist/v18.18.0/) was released recently on Sep 18, And it has an issue of breaking the thread loader at runtime. Due to this issue, our PR frontend build check keeps failing for the node 18 check. For a temporary fix, we are reverting to node 18.17.1. Once the fix is ready on the node Z stream version, We need to ever this temporary change.

node js issue to track: nodejs/node#49911
odf-console PR: #1068