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 1091313 - trying to promote default content view just says Bad Request
Summary: trying to promote default content view just says Bad Request
Keywords:
Status: CLOSED DUPLICATE of bug 1088442
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hammer
Version: 6.0.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: David Davis
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-25 10:56 UTC by Kedar Bidarkar
Modified: 2014-07-24 13:23 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Kedar Bidarkar 2014-04-25 10:56:02 UTC 
Description of problem:

When trying to promote default content view via CLI, we only get a message saying:  "Error: 400 Bad Request"

This needs to be handled more gracefully by letting the end user know that,
"The default content view cannot be promoted"

Version-Release number of selected component (if applicable):
Satellite-6.0.3-RHEL-6-20140404.0/

How reproducible:
When trying to promote default content-view in any org.

Steps to Reproduce:
1. 
2. 
3.

Actual results:

~]# hammer content-view version promote --id 878 --environment-id 938
Could not promote the content view:
  Error: 400 Bad Request

Expected results:

The user should be displayed a message saying.

"The default content view cannot be promoted"

Additional info:
Comment 1 Kedar Bidarkar 2014-04-25 11:25:46 UTC 
The same applies when we edit, publish or try deleting via cli.

*** ERROR: The default content view cannot be edited, published, or deleted. (400) ***
REQUEST URL: /katello/api/content_views/241
Katello::HttpErrors::BadRequest: The default content view cannot be edited, published, or deleted.


For all such above scenarios we need to inform the end user gracefully.
Comment 3 David Davis 2014-07-23 18:15:18 UTC 
I believe this is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1088442. Let me check.
Comment 4 David Davis 2014-07-24 13:22:31 UTC 
There is a message that's being returned in the API ("The default content view cannot be edited, published, or deleted.") but hammer is not displaying it. This is due to https://bugzilla.redhat.com/show_bug.cgi?id=1088442. Closing as a duplicate of 1088442.

*** This bug has been marked as a duplicate of bug 1088442 ***
Comment 5 David Davis 2014-07-24 13:22:31 UTC 
There is a message that's being returned in the API ("The default content view cannot be edited, published, or deleted.") but hammer is not displaying it. This is due to https://bugzilla.redhat.com/show_bug.cgi?id=1088442. Closing as a duplicate of 1088442.

*** This bug has been marked as a duplicate of bug 1088442 ***
Comment 6 David Davis 2014-07-24 13:23:30 UTC 
Sorry, the message is actually "The default content view cannot be promoted".
Note You need to log in before you can comment on or make changes to this bug.