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.

Bug 857842

Summary:	CLI: "/usr/share/katello/script/katello-debug --notar" does not generate packages dir
Product:	Red Hat Satellite	Reporter:	Hayk Hovsepyan <hhovsepy>
Component:	API	Assignee:	Martin Bacovsky <mbacovsk>
Status:	CLOSED ERRATA	QA Contact:	Hayk Hovsepyan <hhovsepy>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	6.0.0	CC:	achan, asettle, dmacpher, mbacovsk, mmccune, msuchy, omaciel
Target Milestone:	Unspecified	Keywords:	Regression, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	The command /usr/share/katello/script/katello-debug --notar failed to generate the packages directory. This fix corrects the syntax errors that caused the issue. The command now successfully creates the packages sub-directory, obtains all the packages and lists all the packages correctly.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-12-04 19:53:47 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 Hayk Hovsepyan 2012-09-17 08:13:27 UTC

Description of problem:

When you execute "/usr/share/katello/script/katello-debug --notar", in tmp it generates some directory where should be "packages" subdirectory. But "packages" does not exist.

Version-Release number of selected component (if applicable):
katello-1.1.12-5.el6cf
katello-cli-1.1.8-4.el6cf.

Comment 3 Martin Bacovsky 2012-09-18 11:35:27 UTC

Fixed in Katello in 4f937b5

Comment 6 Mike McCune 2012-09-21 21:06:56 UTC

New PR to get the original intended list of *all* packages:

https://github.com/Katello/katello/pull/732

merged to master with: 49c73a8cd0408837a23e171540bf1766ca72677b

Comment 9 Hayk Hovsepyan 2012-09-25 13:14:13 UTC

Verified on revision:
katello-certs-tools-1.1.8-1.el6cf.noarch
katello-glue-pulp-1.1.12-9.el6cf.noarch
katello-qpid-broker-key-pair-1.0-1.noarch
katello-agent-1.1.2-1.el6cf.noarch
katello-configure-1.1.9-4.el6cf.noarch
katello-glue-candlepin-1.1.12-9.el6cf.noarch
katello-candlepin-cert-key-pair-1.0-1.noarch
katello-selinux-1.1.1-1.el6cf.noarch
katello-common-1.1.12-9.el6cf.noarch
katello-1.1.12-9.el6cf.noarch
katello-qpid-client-key-pair-1.0-1.noarch
katello-cli-common-1.1.8-5.el6cf.noarch
katello-cli-1.1.8-5.el6cf.noarch
pulp-selinux-server-1.1.12-1.el6cf.noarch
katello-glue-pulp-1.1.12-9.el6cf.noarch
pulp-common-1.1.12-1.el6cf.noarch
python-isodate-0.4.4-4.pulp.el6.noarch
pulp-1.1.12-1.el6cf.noarch
m2crypto-0.21.1.pulp-7.el6.x86_64
python-oauth2-1.5.170-2.pulp.el6.noarch
mod_wsgi-3.3-3.pulp.el6.x86_64

Now it works correctly and shows the list of all packages.

Comment 11 errata-xmlrpc 2012-12-04 19:53:47 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.

http://rhn.redhat.com/errata/RHSA-2012-1543.html