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 1021039 - hammer CLI: All subcommands associated with "organization" and "location" fail
Summary: hammer CLI: All subcommands associated with "organization" and "location" fail
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Provisioning
Version: 6.0.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Martin Bacovsky
QA Contact: Katello QA List
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-18 20:22 UTC by Apurva Bhole
Modified: 2019-09-26 13:43 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-04-24 17:07:24 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 3370 0 Normal Resolved All subcommands associated with "organization" fail 2020-06-30 12:31:11 UTC

Description Apurva Bhole 2013-10-18 20:22:46 UTC 
Description of problem:
All subcommands associated with hammer organization fail with message "The server does not support such operation."

Version-Release number of selected component (if applicable):
# rpm -qa | grep foreman
katello-configure-foreman-1.4.7-5.el6sat.noarch
foreman-1.3.0-18.el6sat.noarch
foreman-proxy-1.3.0-3.el6sat.noarch
ruby193-rubygem-foreman-katello-engine-0.0.17-6.el6sat.noarch
ruby193-rubygem-katello-foreman-engine-0.0.11-3.el6sat.noarch
katello-foreman-all-1.4.6-39.el6sat.noarch
ruby193-rubygem-foreman_api-0.1.6-1.el6sat.noarch
rubygem-foreman_api-0.1.6-1.el6sat.noarch
rubygem-hammer_cli_foreman-0.0.7-2.el6sat.noarch
foreman-postgresql-1.3.0-18.el6sat.noarch
katello-configure-foreman-proxy-1.4.7-5.el6sat.noarch

How reproducible:
always

Steps to Reproduce:
1. hammer organization create --name sampleOrg
2. hammer organization list

Actual results:
The server does not support such operation.

Expected results:
The commands must work normally
Comment 2 Martin Bacovsky 2013-10-21 15:29:24 UTC 
The issue here is that in katello cli the organizations are under 'org' command while in Foreman it is the 'organization' command. If you change the organization in your commands to 'org' it should work. I'll check why the server replied it doesn't support such op. Might be orgs turned off or some error.

For the user this may be awkward and the question is how we want it to behave.
Comment 3 Apurva Bhole 2013-10-22 19:40:14 UTC 
The same issue exist with the 'location' command as well.

Steps to Reproduce:
1. hammer location create --name sampleLocation
2. hammer location list

Actual results:
The server does not support such operation.

Expected results:
The commands must work normally
Comment 4 Apurva Bhole 2013-10-22 20:27:44 UTC 
rpm -qa | grep hammer
rubygem-hammer_cli-0.0.7-2.el6sat.noarch
rubygem-hammer_cli_foreman-0.0.7-2.el6sat.noarch
Comment 5 Martin Bacovsky 2013-10-23 13:00:39 UTC 
This is caused by rubygem-foreman_api that was generated with apipie lib with a bug. I'll update hammer CLI foreman deps. It will need version 0.1.7.

As a workaround you could try; gem install foreman_api && service httpd restart
Comment 6 Martin Bacovsky 2013-10-23 18:03:07 UTC 
rubygem-hammer_cli_foreman >= 0.0.8 fixes this issue. This package and related rubygem-foreman_api should be part of Snap 7
Comment 8 Corey Welton 2013-10-25 16:34:47 UTC 
The initial report for 'organization' appears to be fixed. This does not appeared fixed for comment #3 ('location'), however.

[root@cloud-qe-21 ~]# hammer location create --name sampleLocation
The server does not support such operation.
[root@cloud-qe-21 ~]#  hammer location list
The server does not support such operation.

[root@cloud-qe-21 ~]# rpm -qa | grep hammer
rubygem-hammer_cli-0.0.7-2.el6sat.noarch
rubygem-hammer_cli_foreman-0.0.8-2.el6sat.noarch

Satellite-6.0.2-RHEL-6-20131023.1
Comment 9 Dominic Cleal 2013-10-25 16:39:38 UTC 
(In reply to Corey Welton from comment #8)
> The initial report for 'organization' appears to be fixed. This does not
> appeared fixed for comment #3 ('location'), however.
> 
> [root@cloud-qe-21 ~]# hammer location create --name sampleLocation
> The server does not support such operation.

Sat6 doesn't ship with locations enabled: check /etc/foreman/settings.yaml, it should have ":locations_enabled: false", but organisations enabled.

I think this error message is accurate.
Comment 10 Corey Welton 2013-10-25 16:47:16 UTC 
Indeed, that makes sense. There is presently no "locations_enabled" in the settings.yaml, so it defaults to false.  Locations being enabled is not really in scope for testing atm, so I think we can consider this one Verified.

Satellite-6.0.2-RHEL-6-20131023.1
Comment 14 Bryan Kearney 2014-04-24 17:07:24 UTC 
This was verified and delivered with MDP2. Closing it out.
Note You need to log in before you can comment on or make changes to this bug.