Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 987925 - Cannot create system via API - 404 on environment
Summary: Cannot create system via API - 404 on environment
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: Nightly
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Katello Bug Bin
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks: sam20-tracker
TreeView+ depends on / blocked
 
Reported: 2013-07-24 12:22 UTC by Jeff Weiss
Modified: 2019-09-26 13:41 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-29 12:43:24 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jeff Weiss 2013-07-24 12:22:22 UTC
Description of problem:


Version-Release number of selected component (if applicable):
1.4.2-1.git.961.e5d1bd2.el6

How reproducible:
always

Steps to Reproduce:
1. Create an env via API 
2. Get the id from the response
3. POST /katello/api/environments/[id]/systems

Actual results:
404 Couldn't find environment [id]

Expected results:
system created

Additional info:

Comment 1 Jeff Weiss 2013-07-24 12:34:36 UTC
You can also get this error in the UI - seems like candlepin is losing something.

For example, create an env in the UI and then a distributor in the UI.

"No such environment: 45" "Resources::Candlepin::Consumer: 404 Resource Not Found {\"displayMessage\":\"No such environment: 45\"}

Comment 2 Jeff Weiss 2013-08-08 18:04:20 UTC
Apparently the API call was missing a content view ID. which is now required.

However I think this is still a bug to throw a 404 error on the environment when what's actually wrong is that the caller forgot to specify a cv id.


Note You need to log in before you can comment on or make changes to this bug.