Bug 1132676

Summary: Any hammer command which shows progress bar in output will work only for the first time
Product: Red Hat Satellite Reporter: sthirugn <sthirugn>
Component: HammerAssignee: David Davis <daviddavis>
Status: CLOSED ERRATA QA Contact: jcallaha
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.0.3CC: bbuckingham, jcallaha
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/7248
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-12 05:12:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description sthirugn@redhat.com 2014-08-21 19:35:51 UTC
Description of problem:
hammer shell failed

Version-Release number of selected component (if applicable):
Version Tested:
GA Snap 6 - Satellite-6.0.4-RHEL-6-20140820.1

* apr-util-ldap-1.3.9-3.el6_0.1.x86_64
* candlepin-0.9.23-1.el6_5.noarch
* candlepin-common-1.0.1-1.el6_5.noarch
* candlepin-scl-1-5.el6_4.noarch
* candlepin-scl-quartz-2.1.5-5.el6_4.noarch
* candlepin-scl-rhino-1.7R3-1.el6_4.noarch
* candlepin-scl-runtime-1-5.el6_4.noarch
* candlepin-selinux-0.9.23-1.el6_5.noarch
* candlepin-tomcat6-0.9.23-1.el6_5.noarch
* elasticsearch-0.90.10-6.el6sat.noarch
* foreman-1.6.0.41-1.el6sat.noarch
* foreman-compute-1.6.0.41-1.el6sat.noarch
* foreman-gce-1.6.0.41-1.el6sat.noarch
* foreman-libvirt-1.6.0.41-1.el6sat.noarch
* foreman-ovirt-1.6.0.41-1.el6sat.noarch
* foreman-postgresql-1.6.0.41-1.el6sat.noarch
* foreman-proxy-1.6.0.29-1.el6sat.noarch
* foreman-selinux-1.6.0.7-1.el6sat.noarch
* foreman-vmware-1.6.0.41-1.el6sat.noarch
* katello-1.5.0-29.el6sat.noarch
* katello-ca-1.0-1.noarch
* katello-certs-tools-1.5.6-1.el6sat.noarch
* katello-installer-0.0.60-1.el6sat.noarch
* openldap-2.4.23-34.el6_5.1.x86_64
* openldap-devel-2.4.23-34.el6_5.1.x86_64
* pulp-katello-0.3-3.el6sat.noarch
* pulp-nodes-common-2.4.0-0.30.beta.el6sat.noarch
* pulp-nodes-parent-2.4.0-0.30.beta.el6sat.noarch
* pulp-puppet-plugins-2.4.0-0.30.beta.el6sat.noarch
* pulp-puppet-tools-2.4.0-0.30.beta.el6sat.noarch
* pulp-rpm-plugins-2.4.0-0.30.beta.el6sat.noarch
* pulp-selinux-2.4.0-0.30.beta.el6sat.noarch
* pulp-server-2.4.0-0.30.beta.el6sat.noarch
* python-ldap-2.3.10-1.el6.x86_64
* ruby193-rubygem-net-ldap-0.3.1-3.el6sat.noarch
* ruby193-rubygem-runcible-1.1.0-2.el6sat.noarch



How reproducible:


Steps to Reproduce:
1. Create a content view - add repos - publish and promote to three different environments.
2. Login to hammer shell and list the content view [PASS]

# hammer -u admin -p changeme shell
Welcome to the hammer interactive shell
Type 'help' for usage information
Command completion is disabled on ruby < 1.9 due to compatibility problems.
hammer> content-view info --id=19
ID:                 19
Name:               testenvbugcv
Label:              testenvbugcv
Composite:          
Description:        
Content Host Count: 
Organization:       rhcorp
Repositories:       
 1) ID:    143
    Name:  testenvbugrepo
    Label: testenvbugrepo
Puppet Modules:     

Environments:       
 1) ID:   4
    Name: QE
 2) ID:   3
    Name: DEV
 3) ID:   2
    Name: Library
Versions:           
 1) ID:        17
    Version:   2
    Published: 2014/08/21 14:13:17
 2) ID:        18
    Version:   3
    Published: 2014/08/21 15:54:19

3. remove from environment- DEV [PASS]
hammer> content-view remove-from-environment --id 19 --lifecycle-environment DEV --organization-id 3
[....................................................................................] [100%]
Task 7994bdb7-3781-4cfc-be95-fc454a03c9a0: success

4. remove from environment - QE [FAIL]
hammer> content-view remove-from-environment --id 19 --lifecycle-environment QE --organization-id 3
Could not remove the content view from environment:
  Error: The server does not support such operation.

5. exit hammer shell [PASS]
hammer> exit

6. Try to remove enviroment - QE without using hammer shell: [PASS]

# hammer -p changeme content-view remove-from-environment --id=19 --lifecycle-environment=QE --organization-id=3
[....................................................................................] [100%]
Task 807df8a9-eb1e-44ee-a252-4519be66909f: success

Actual results:
Step 4 failed above

Expected results:
Step 4 should PASS since Step 6 PASSED

Additional info:

Comment 1 sthirugn@redhat.com 2014-08-21 19:54:06 UTC
An other one:
hammer> subscription refresh-manifest --organization-id=3
[....................................................................................] [100%]
Task 84b4cdd8-e207-4154-8f82-39d86d965467: success

hammer> subscription refresh-manifest --organization-id=3
Manifest refresh failed:
  Error: The server does not support such operation.

hammer> exit

[root@sat6 ~]# hammer -p changeme subscription refresh-manifest --organization-id=3
[....................................................................................] [100%]

Comment 3 sthirugn@redhat.com 2014-08-21 20:04:50 UTC
Other commands affected:
content-view remove-from-environment
subscription refresh-manifest
subscription upload
subscription delete-manifest
...
and I am sure there are more. I can add when I find them.

Comment 5 Dustin Tsang 2014-08-21 20:14:09 UTC
looks like issue seems may affect any of the async calls.
in hammer-cli/lib/hammer_cli/apipie/command.rb:44 in send_request

the resource is foreman_tasks instead of content_views
the action :remove_from_events does not exist for the resource for foreman_tasks

Comment 6 Partha Aji 2014-08-25 15:04:07 UTC
Created redmine issue http://projects.theforeman.org/issues/7248 from this bug

Comment 8 jcallaha 2014-11-21 19:49:56 UTC
"*** This bug is verified in upstream.  This fix should eventually land in future downstream builds ***

Version Tested:
RHEL66 / RHEL7

qe-foreman-rhel7.usersys.redhat.com-puppet-client-1.0-1.noarch
foreman-vmware-1.8.0-0.develop.201411201326giteaefbec.el7.noarch
qe-foreman-rhel7.usersys.redhat.com-qpid-broker-1.0-1.noarch
rubygem-hammer_cli_foreman-0.1.3-1.201411121216git9381fc5.el7.noarch
ruby193-rubygem-foreman_hooks-0.3.7-2.el7.noarch
foreman-postgresql-1.8.0-0.develop.201411201326giteaefbec.el7.noarch
qe-foreman-rhel7.usersys.redhat.com-qpid-client-cert-1.0-1.noarch
foreman-release-1.8.0-0.develop.201411201326giteaefbec.el7.noarch
foreman-libvirt-1.8.0-0.develop.201411201326giteaefbec.el7.noarch
foreman-compute-1.8.0-0.develop.201411201326giteaefbec.el7.noarch
foreman-ovirt-1.8.0-0.develop.201411201326giteaefbec.el7.noarch
foreman-selinux-1.8.0-0.develop.201410280941git10de1c5.el7.noarch
qe-foreman-rhel7.usersys.redhat.com-foreman-client-1.0-1.noarch
qe-foreman-rhel7.usersys.redhat.com-apache-1.0-1.noarch
qe-foreman-rhel7.usersys.redhat.com-parent-cert-1.0-1.noarch
ruby193-rubygem-foreman_discovery-1.4.0-2.el7.noarch
foreman-proxy-1.8.0-0.develop.201411201507gitfc67f91.el7.noarch
foreman-1.8.0-0.develop.201411201326giteaefbec.el7.noarch
ruby193-rubygem-foreman-tasks-0.6.9-1.el7.noarch
qe-foreman-rhel7.usersys.redhat.com-foreman-proxy-1.0-1.noarch
ruby193-rubygem-foreman_docker-0.2.0-2.el7.noarch
rubygem-hammer_cli_foreman_tasks-0.0.3-2.201409091410git163c264.git.0.988ca80.el7.noarch
foreman-gce-1.8.0-0.develop.201411201326giteaefbec.el7.noarch
ruby193-rubygem-foreman_bootdisk-4.0.2-1.el7.noarch

Comment 9 Bryan Kearney 2015-08-11 13:30:02 UTC
This bug is slated to be released with Satellite 6.1.

Comment 10 errata-xmlrpc 2015-08-12 05:12:50 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2015:1592