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

DFBUGS-1719: [release-4.18] Fix 'NaN' issue with 'Estimated days until full' (Capacity Trends) #1892

Open
wants to merge 1 commit into
base: release-4.18
Choose a base branch
from

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #1891

/assign SanjalKatiyar

Copy link
Contributor

openshift-ci bot commented Mar 7, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

The full list of commands accepted by this bot can be found 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-ci-robot
Copy link

openshift-ci-robot commented Mar 7, 2025

@openshift-cherrypick-robot: [Jira Issue DFBUGS-1779](https://issues.redhat.com//browse/DFBUGS-1779) has been cloned as [Jira Issue DFBUGS-1786](https://issues.redhat.com//browse/DFBUGS-1786). Will retitle bug to link to clone.
/retitle [release-4.18] DFBUGS-1786: Fix 'NaN' issue with 'Estimated days until full' (Capacity Trends)

In response to this:

This is an automated cherry-pick of #1891

/assign SanjalKatiyar

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 changed the title [release-4.18] DFBUGS-1779: Fix 'NaN' issue with 'Estimated days until full' (Capacity Trends) [release-4.18] DFBUGS-1786: Fix 'NaN' issue with 'Estimated days until full' (Capacity Trends) Mar 7, 2025
@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid jira ticket of any type jira/invalid-bug Indicates that the referenced jira bug is invalid for the branch this PR is targeting labels Mar 7, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 7, 2025

@openshift-cherrypick-robot: This pull request references [Jira Issue DFBUGS-1786](https://issues.redhat.com//browse/DFBUGS-1786), which is invalid:

  • expected the bug to target the "odf-4.18" 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.

In response to this:

This is an automated cherry-pick of #1891

/assign SanjalKatiyar

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.

@SanjalKatiyar
Copy link
Collaborator

SanjalKatiyar commented Mar 7, 2025

/retitle DFBUGS-1719: [release-4.18] Fix 'NaN' issue with 'Estimated days until full' (Capacity Trends)

@openshift-ci openshift-ci bot changed the title [release-4.18] DFBUGS-1786: Fix 'NaN' issue with 'Estimated days until full' (Capacity Trends) DFBUGS-1719: [release-4.18] Fix 'NaN' issue with 'Estimated days until full' (Capacity Trends) Mar 7, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 7, 2025

@openshift-cherrypick-robot: This pull request references [Jira Issue DFBUGS-1719](https://issues.redhat.com//browse/DFBUGS-1719), which is invalid:

  • expected the bug to target the "odf-4.18" 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.

In response to this:

This is an automated cherry-pick of #1891

/assign SanjalKatiyar

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
jira/invalid-bug Indicates that the referenced jira bug is invalid for the branch this PR is targeting jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid jira ticket of any type
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants