1414392 – Confusing parameter --contents

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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 1414392 - Confusing parameter --contents

Summary: Confusing parameter --contents

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	Red Hat Enterprise Linux 6
Classification:	Red Hat
Component:	preupgrade-assistant
Sub Component:
Version:	6.9
Hardware:	Unspecified
OS:	Unspecified
Priority:	unspecified
Severity:	unspecified
Target Milestone:	rc
Target Release:	---
Assignee:	Michal Bocek
QA Contact:	Alois Mahdal
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2017-01-18 12:08 UTC by Tereza Cerna
Modified:	2017-03-21 12:10 UTC (History)
CC List:	3 users (show)
Fixed In Version:	preupgrade-assistant-2.3.2-1.el6
Doc Type:	No Doc Update
Doc Text:	undefined
Clone Of:
Environment:
Last Closed:	2017-03-21 12:10:42 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2017:0819	0	normal	SHIPPED_LIVE	preupgrade-assistant bug fix and enhancement update	2017-03-21 12:53:47 UTC

Comment 4 Alois Mahdal 2017-01-24 02:27:04 UTC

Seems to me that intent could be to have -s to select path from "installed" ones, and -c to select another ("custom") path.  This is unnecessary duplication, though:  we could just always talk about upgrade paths in terms of directories, making following specifications valid:

    preupg -x /usr/lib/preupgrade/foo
    preupg -x ./bar/baz

and of course, the XML filename is outright superfluous.

That said, there are many more things confusing and inconsistent about the CLI, so I'd prefer for this to be solved as part of greater CLI overhaul, eg. bug 1398488 - [RFE] split preupg binary.

Comment 5 Michal Bocek 2017-02-07 23:25:22 UTC

There is much to be desired in terms of CLI options. I agree the CLI needs and overhaul. Also that options -s and -c are more or less duplicate and there can be just one.

In the meantime, I updated the help and man page so it says what the options actually do: https://github.com/upgrades-migrations/preupgrade-assistant/pull/219.

Comment 7 Alois Mahdal 2017-03-07 23:54:23 UTC

preupgrade-assistant-2.3.2-2.el6 now makes it clear:

      -c ALL_XCCDF_PATH, --contents=ALL_XCCDF_PATH
                            Provide path to all-xccdf.xml of the set of modules
                            which is to be used for assesing the system. By
                            default, if there is just one set in
                            /usr/share/preupgrade, Preupgrade Assistant uses that

Comment 9 errata-xmlrpc 2017-03-21 12:10:42 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://rhn.redhat.com/errata/RHBA-2017-0819.html

Note You need to log in before you can comment on or make changes to this bug.