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:
If you run katello-backup from cron then it fails with
'sorry, you must have a tty to run sudo'
Version-Release number of selected component (if applicable):
Satellite 6.2.13
How reproducible:
100%
Steps to Reproduce:
Put this line to crontab
33 15 * * * root /usr/bin/katello-backup /var/sat-content --online-backup --skip-pulp-content >> /var/log/satellite/backups.log 2>&1
Actual results:
Starting backup: 2018-01-27 15:33:02 +1100
Creating backup folder /var/sat-content/katello-backup-20180127153302
sudo: sorry, you must have a tty to run sudo
****cancelled****
Expected results:
Completed backup
I also found that adding this line to /etc/sudoers help to avoid the error but this workaround is unacceptable in secured environments.
Default !requiretty
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://access.redhat.com/errata/RHBA-2018:2550
Comment 18Red Hat Bugzilla
2023-09-15 00:06:20 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days