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.
Description of problem:
When running 'hammer import all' multiple times
(1st pass to trigger repository sync, 2nd pass to create content views, ...)
the 'hammer import user' complaints about password file being already created.
Since this is a recommended use case, hammer import should count with that and shall not complain.
Suggested approach:
If password file already exists, just append eventual new lines.
(in 99% cases all users will be created during the 1st pass and no append will happen anyway.)
Alternate proposal:
It would be nice if ".<n>" would be appended for least natural n such that
desired filename does not exist in case requested file exists.
This solution might be proffered as simply appending existing csv (or any other file) might lead to some complications (say in case users were deleted and re-imported, there will be two entries for the same user in single file).