Bug #16309
closedCannot add Puppet module to content view if there are too many to choose from
Description
Open your content view and click on the "Puppet Modules" tab
Click "Add New Module"
Filter/find your module and click "Select a Version"
It appears that the maximum rows that will be displayed is 39, there is no pagination, and filtering only takes into account the current records in view. So if there are several options to choose from and the one you want is by an author at the end of the alphabet you're out of luck.
Search for the "postfix" module for an example. The last one I see is authored by "thias". The postfix module I want comes from my local repository and the author is set to "tresgeek" and doesn't appear in the list (it would be #40 and 41). If I change the "author" of my postfix module to "atresgeek" it appears near the top of the list (and the "thias" ones fall off the list - still only 39 appear).
Files
Updated by Dominic Cleal about 8 years ago
- Project changed from Foreman to Katello
Updated by Justin Sherrill about 8 years ago
- Category set to Content Views
- Status changed from New to Need more information
What version of katello are you on?
Updated by Justin Sherrill about 8 years ago
Can you paste a screenshot as well?
Updated by Jason Nance about 8 years ago
Katello version is 3.1rc2 (katello-3.1.0-4.rc2.el7.noarch).
Attaching screen shot. The content area is quite large so I had to cut it off. Please let me know if there is a different region you are interested in.
Updated by Justin Sherrill about 8 years ago
- Status changed from Need more information to Assigned
Updated by Justin Sherrill about 8 years ago
- Assignee set to John Mitsch
- Target version set to 126
Updated by John Mitsch about 8 years ago
- Status changed from Assigned to Closed
In master, I was able to search to the end of the list http://www.clipular.com/c/5773140185841664.png?k=WMWJysYrljP9q4AY9LIEh-Q-XbQ Either I am misunderstanding what you are saying (feel free to re-open) or something changed since 3.1. I'm going to close since if something fixed this, it will be in 3.2.
Updated by Eric Helms about 8 years ago
- Status changed from Closed to Assigned
- Translation missing: en.field_release set to 162
Updated by Jason Nance about 8 years ago
Since this has been changed from closed to assigned does that mean that we're on the same page now and that this is going to be looked into?
Updated by Brad Buckingham about 8 years ago
- Target version changed from 126 to 129
Updated by Brad Buckingham about 8 years ago
- Target version changed from 129 to 133
Updated by Eric Helms about 8 years ago
- Translation missing: en.field_release changed from 162 to 197
Updated by Brad Buckingham about 8 years ago
- Target version changed from 133 to 140
Updated by Brad Buckingham almost 8 years ago
- Target version changed from 140 to 147
Updated by Eric Helms almost 8 years ago
- Translation missing: en.field_release changed from 197 to 208
Updated by Jason Nance almost 8 years ago
Is this issue more complicated than it appears on the surface? I realize that there is a finite amount of time but I've watched this get pushed out several times already and it seems like it wouldn't be that complicated to fix. Is there some additional information I can provide or testing I can do to help get this resolved?
Updated by John Mitsch almost 8 years ago
Jason,
We know what needs to change, but its just been "on the back burner" due to some more important issues that have taken precedent. We will get to it soon, thanks for the reminder.
-John
Updated by Brad Buckingham almost 8 years ago
- Target version changed from 147 to 151
Updated by Jason Nance almost 8 years ago
Turns out this is pretty easy to work around via API calls if anyone else is interested:
import getpass import requests apiUser = 'admin' apiPass = getpass.getpass() apiAuth = requests.auth.HTTPBasicAuth(apiUser, apiPass) apiURL = 'https://katello.host.org/katello/api/content_views' cvID = 15 modName = 'mymod' modAuthor = 'myauthor' postData = { 'content_view_id': cvID, 'name': modName, 'author': modAuthor } response = requests.post( '{}/{}/content_view_puppet_modules'.format(apiURL, cvID), json=postData, auth=apiAuth, verify=False )
Just replace the values for apiUser
, apiURL
(the host name portion), cvID
(content view ID), modName
, and modAuthor
.
With verify=False
you will get the following warning based on your Python version:
/usr/lib/python2.7/site-packages/urllib3/connectionpool.py:769: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.org/en/latest/security.html InsecureRequestWarning)
If everything worked response.status_code
should be 200
(and your module will show up in your content view).
Once it is in your content view you can manage the module version from the web UI.
Updated by John Mitsch almost 8 years ago
- Translation missing: en.field_release changed from 208 to 214
Updated by Justin Sherrill almost 8 years ago
- Translation missing: en.field_release changed from 214 to 222
Updated by Jason Nance over 7 years ago
- Has duplicate Bug #17930: unable to add a puppet module from GUI added
Updated by John Mitsch over 7 years ago
- Status changed from Assigned to Duplicate