Project

General

Profile

Bug #25232

CV History: Incorrect API call due to parsing error (page=NaN)

Added by Mirosław Zalewski 6 months ago. Updated 3 months ago.

Status:
Resolved
Priority:
Normal
Category:
Content Views
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

Content view History tab sends following API request:
/katello/api/v2/content_views/4/history?organization_id=1&page=NaN&paged=true&per_page=20&search=&sort_by=created_at&sort_order=DESC

This is currently shadowed by issue #25231, but once it is fixed, we will see UI complaining about invalid value for Integer(): "NaN".

Katello git commit id: 77a4d76db2d1524f152281a78ef8d17f4fdfa646
Foreman git commit id: 9ccfbde5c417ed466b21c997d01d4608cc4e8c57

Steps to reproduce:
1. Create new content view
2. Open this content view and navigate to History tab

Expected results:
There is no error notification; history data is displayed in table (if there is any history to display).


Related issues

Related to Katello - Bug #25231: "the field 'created_at' in the order statement is not valid field for search" on content view history tabClosed

History

#1 Updated by Mirosław Zalewski 6 months ago

  • Related to Bug #25231: "the field 'created_at' in the order statement is not valid field for search" on content view history tab added

#2 Updated by Tomer Brisker 6 months ago

  • Category deleted (Web Interface)
  • Project changed from Foreman to Katello

#3 Updated by John Mitsch 6 months ago

  • Triaged changed from No to Yes
  • Target version set to Katello 3.11.0
  • Category set to Content Views

#4 Updated by Jonathon Turel 3 months ago

  • Assignee set to Jonathon Turel

#5 Updated by Jonathon Turel 3 months ago

Hey Mirek, I think there was a corresponding Foreman bug which has been addressed and fixed this issue. Take another look and we can close this one if it's taken care of.

#6 Updated by Mirosław Zalewski 3 months ago

  • Status changed from New to Resolved

Jonathon,

I can no longer reproduce it as of:
Foreman git id 15ac394288f0719f4d738301370836ed0a7007f5
Katello git id 6dd89e862945a20e56d972a4b030868ac744b66b

You are right, this must have been addressed by another commit already.

Downstream Satellite is not affected either.

Also available in: Atom PDF