Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
I guess this can be switched to ON_QA: I have just used hammer to refresh manifest and it worked as expected. Used Satellite-6.1.0-RHEL-6-20150217.0-x86_64.
Created attachment 942321 [details] manifest refresh fails Description of problem: Manifest refresh fails Version-Release number of selected component (if applicable): ruby193-rubygem-foreman-tasks-0.6.9-1.1.el6sat.noarch foreman-compute-1.6.0.44-1.el6sat.noarch ruby193-rubygem-foreman_hooks-0.3.5-2.el6sat.noarch foreman-postgresql-1.6.0.44-1.el6sat.noarch foreman-1.6.0.44-1.el6sat.noarch foreman-vmware-1.6.0.44-1.el6sat.noarch ruby193-rubygem-foreman-redhat_access-0.0.4-1.el6sat.noarch rubygem-hammer_cli_foreman-0.1.1-16.el6sat.noarch cloud-qe-10.idmqe.lab.eng.bos.redhat.com-foreman-proxy-1.0-1.noarch foreman-selinux-1.6.0.14-1.el6sat.noarch foreman-gce-1.6.0.44-1.el6sat.noarch ruby193-rubygem-foreman_bootdisk-2.0.6-1.1.el6sat.noarch cloud-qe-10.idmqe.lab.eng.bos.redhat.com-foreman-client-1.0-1.noarch foreman-ovirt-1.6.0.44-1.el6sat.noarch ruby193-rubygem-foreman_discovery-1.3.0-2.el6sat.noarch foreman-proxy-1.6.0.30-1.el6sat.noarch rubygem-hammer_cli_foreman_tasks-0.0.3-3.el6sat.noarch foreman-libvirt-1.6.0.44-1.el6sat.noarch How reproducible: everytime Steps to Reproduce: 1.2014-09-26 12:24:06 - robottelo.common.ssh - DEBUG - >>> [cloud-qe-10.idmqe.lab.eng.bos.redhat.com] LANG=en_US hammer -v -u admin -p **** subscription refresh-manifest --organization-id='173' 2014-09-26 12:24:17 - robottelo.common.ssh - INFO - Instantiated Paramiko client 0x2bdcbd0 2014-09-26 12:24:25 - robottelo.common.ssh - INFO - Destroying Paramiko client 0x2bdcbd0 2014-09-26 12:24:25 - robottelo.common.ssh - INFO - Destroyed Paramiko client 0x2bdcbd0 2014-09-26 12:24:25 - robottelo.common.ssh - DEBUG - <<< Task f39a067b-b12b-46b8-bf17-57202d947a5a: warning 2. Screen shot attached 3. Actual results: manifest refresh fails Expected results: manifest refresh works as expected Additional info: