Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CNV-39940: UI does not show installed version #1968

Merged
merged 1 commit into from
May 22, 2024

Conversation

avivtur
Copy link
Member

@avivtur avivtur commented May 22, 2024

📝 Description

The UI assumes that the subscription that holds the version metadata has a unique name.
Since the name of the subscription CR is arbitrary, we now check if the subscription is from the package of kubevirt-hyperconverged or in some community upstream cases the package named community-kubevirt-hyperconverged.

🎥 Demo

Before:
version-missing

After:
version-missing-after

@openshift-ci-robot
Copy link
Collaborator

openshift-ci-robot commented May 22, 2024

@avivtur: This pull request references CNV-39940 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.17.0" version, but no target version was set.

In response to this:

📝 Description

The UI assumes that the subscription that holds the version metadata has a unique name.
Since the name of the subscription CR is arbitrary, we now check if the subscription is from the package of kubevirt-hyperconverged.

🎥 Demo

Before:
version-missing

After:
version-missing-after

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 openshift-ci bot requested review from hstastna and vojtechszocs May 22, 2024 12:03
@openshift-ci openshift-ci bot added the approved This issue is something we want to fix label May 22, 2024
});

const subscription = useMemo(
() => subscriptions?.find((sub) => sub?.spec?.name === KUBEVIRT_HYPERCONVERGED),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

community-kubevirt-hyperconverged in case of isUpstream == true

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@orenc1 I changed it to check if the string ends with "kubevirt-hyperconverged" to cover both cases , sounds ok with you?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, that will work either 👍

@openshift-ci-robot
Copy link
Collaborator

openshift-ci-robot commented May 22, 2024

@avivtur: This pull request references CNV-39940 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.17.0" version, but no target version was set.

In response to this:

📝 Description

The UI assumes that the subscription that holds the version metadata has a unique name.
Since the name of the subscription CR is arbitrary, we now check if the subscription is from the package of kubevirt-hyperconverged or in some community upstream cases the package named community-kubevirt-hyperconverged.

🎥 Demo

Before:
version-missing

After:
version-missing-after

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.

@avivtur avivtur force-pushed the version-keeps-loading branch from bba1b8c to b40e6e4 Compare May 22, 2024 13:24
@openshift-ci openshift-ci bot added the lgtm Passed code review, ready for merge label May 22, 2024
Copy link
Contributor

openshift-ci bot commented May 22, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: avivtur, hstastna

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

The pull request process is described here

Needs approval from an approver in each of these files:

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

@openshift-merge-bot openshift-merge-bot bot merged commit 10ad594 into kubevirt-ui:main May 22, 2024
10 checks passed
@gouyang
Copy link
Member

gouyang commented May 24, 2024

/cherry-pick release-4.16

@gouyang
Copy link
Member

gouyang commented May 24, 2024

/cherry-pick release-4.15

@openshift-cherrypick-robot
Copy link
Collaborator

@gouyang: new pull request created: #1973

In response to this:

/cherry-pick release-4.16

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.

@openshift-cherrypick-robot
Copy link
Collaborator

@gouyang: new pull request created: #1974

In response to this:

/cherry-pick release-4.15

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved This issue is something we want to fix jira/valid-reference lgtm Passed code review, ready for merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants