Bug #14331
closedusing id param to add a puppet module to a content view working incorrectly
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
Updated by The Foreman Bot almost 9 years ago
- Status changed from New to Ready For Testing
- Assignee set to John Mitsch
- Pull request https://github.com/Katello/katello/pull/5912 added
Updated by John Mitsch almost 9 years ago
- Status changed from Ready For Testing to Resolved
- Assignee deleted (
John Mitsch) - Pull request deleted (
https://github.com/Katello/katello/pull/5912)
fixed in hammer (with a separate issue) https://github.com/Katello/hammer-cli-katello/pull/368
Updated by Eric Helms almost 9 years ago
- Status changed from Resolved to Rejected
- Translation missing: en.field_release set to 114
Updated by Jonathon Turel over 4 years ago
- Target version changed from Katello Backlog to Katello Recycle Bin