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 something disrupts an upload of a foreman debug file, script still says it is successful, even when it isn't.
Version-Release number of selected component (if applicable):
snap 6 RHEL7
How reproducible:
Steps to Reproduce:
1. foreman-debug -g -v -a -d /tmp/test
2. view results
3.
Actual results:
A debug directory has been created: /tmp/test
You may want to upload the tarball to our public server via rsync. There is a
write only directory (readable only by Foreman core developers) for that. Note
the rsync transmission is UNENCRYPTED:
rsync /tmp/test.tar.xz rsync://theforeman.org/debug-incoming
Do you want to do this now? [y/N] y
Uploading...
rsync: link_stat "/tmp/test.tar.xz" failed: No such file or directory (2)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1052) [sender=3.0.9]
The tarball has been uploaded, please contact us on mailing list or IRC.
Expected results:
If there is a failure in send, it should not says "The tarball has been uploaded".
Additional info:
Comment 1RHEL Program Management
2015-05-28 18:52:27 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
This has been reported usptream as an issue, and will no longer be tracked it downstream. I am therefore closing this out. If you feel this was done incorrecty, please feel free to re-open with additional data.