Project

General

Profile

Actions
Copy link

Bug #14331

closed

using id param to add a puppet module to a content view working incorrectly

Added by John Mitsch almost 9 years ago. Updated over 4 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
API
Target version:
Katello Recycle Bin
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

If you use the id param on
POST /content_views/:content_view_id/content_view_puppet_modules

it will save that id under uuid, even though it is an active record id (and not a valid uuid)

Steps to replicate:
1) attach a puppet module to a content view with a puppet module id

you can use
hammer content-view puppet-module add --organization-id 1 --content-view-id CONTENT_VIEW_ID --id PUPPET_MODULE_ID
(replace PUPPET_MODULE_ID with the id of the puppet module, and CONTENT_VIEW_ID with the id of the content view)

2)check the api call on POST /content_views/:content_view_id/content_view_puppet_modules and the output of hammer -r content-view puppet-module list --organization-id 1 --content-view-id CONTENT_VIEW_ID

the puppet modules active record id will be in the uuid column, the uuid of the puppet module should be there

Actions
Copy link

Also available in: Atom PDF