OCPBUGS-77349: Show "No description available" instead of "Not available" for CRD cards

[harche]

Summary

• When a CRD in spec.customresourcedefinitions.owned doesn't have a description field, the Operator details page shows "Not available" under the CRD name. This is confusing because it looks like the CRD itself isn't available, when really it's just the description that's missing.
• This caused OCPBUGS-65849 — the reporter saw "Not available" for DASOperator, AllocationClaim, and NodeAccelerator, verified the CRDs were running via oc get, and filed a bug thinking something was broken.
• This changes the CRD card fallback from the generic "Not available" (set by SyncMarkdownView) to "No description available", which makes it clear what's actually missing. The global SyncMarkdownView default is unchanged.

Jira: https://issues.redhat.com/browse/OCPBUGS-77349

Test plan

• Existing tests pass
• New test: renders CRD description when provided
• New test: renders "No description available" when CRD description is missing

🤖 Generated with Claude Code

Summary by CodeRabbit

Release Notes

• Bug Fixes

  • Custom Resource Definition (CRD) cards now display a "No description available" message when descriptions are missing, providing clearer feedback instead of showing empty content areas.

• Tests

  • Expanded test coverage to verify CRDCard renders correctly both when descriptions are provided and when they are unavailable.

[openshift-ci-robot]

@harche: This pull request references Jira Issue OCPBUGS-77349, which is invalid:

• expected the bug to target the "4.22.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Summary

• When a CRD in spec.customresourcedefinitions.owned doesn't have a description field, the Operator details page shows "Not available" under the CRD name. This is confusing because it looks like the CRD itself isn't available, when really it's just the description that's missing.
• This caused OCPBUGS-65849 — the reporter saw "Not available" for DASOperator, AllocationClaim, and NodeAccelerator, verified the CRDs were running via oc get, and filed a bug thinking something was broken.
• This changes the CRD card fallback from the generic "Not available" (set by SyncMarkdownView) to "No description available", which makes it clear what's actually missing. The global SyncMarkdownView default is unchanged.

Jira: https://issues.redhat.com/browse/OCPBUGS-77349

Test plan

• Existing tests pass
• New test: renders CRD description when provided
• New test: renders "No description available" when CRD description is missing

🤖 Generated with Claude Code

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: harche
Once this PR has been reviewed and has the lgtm label, please assign rhamilto for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• frontend/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between 9459e3a and 02e2993.

📒 Files selected for processing (2)

• frontend/packages/operator-lifecycle-manager/src/components/__tests__/clusterserviceversion.spec.tsx
• frontend/packages/operator-lifecycle-manager/src/components/clusterserviceversion.tsx

---

📝 Walkthrough

Walkthrough

The pull request modifies test mocks and component props to address empty or missing CRD descriptions. The AsyncComponent mock in tests is updated to accept content and emptyMsg props instead of children, changing how test data is exposed. New test cases validate CRDCard rendering with and without descriptions. The CRDCard component is updated to pass a localized "No description available" message to MarkdownView via a new optional emptyMsg prop.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title directly and specifically describes the main change: updating CRD card messaging from 'Not available' to 'No description available', which aligns with both the file modifications and PR objectives.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[harche]

@harche: This pull request references Jira Issue OCPBUGS-77349, which is invalid:

• expected the bug to target the "4.22.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

I will file the bug for 4.22, if the team thinks this is a valid issue.

[openshift-ci]

@harche: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.