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.
DescriptionPatrick C. F. Ernzer
2021-02-24 15:31:52 UTC
Description of problem:
if I use satellite maintain backup via cron, the notification mails I get are very large (multiple hundreds of KB)
it would be nice if the tool had a commandline flag that makes it less chatty (e.g. --cron)
Version-Release number of selected component (if applicable):
satellite-maintain-0.0.1-1.el7sat.noarch
How reproducible:
always
Steps to Reproduce:
1. have a cron job that runs `satellite maintain backup …`
2. receive cron email
3. look at size of email
Actual results:
this
50 15 * * * root satellite-maintain backup offline --assumeyes --skip-pulp-content --preserve-directory --include-db-dumps /var/sat-backup-test
just produced a 941 KiB email. Because the used spinner animation (very useful when using the backup tool interactively) produces a lot output like the following
===8<---
| Compressing backup of Mongo DB
/ Compressing backup of Mongo DB
- Compressing backup of Mongo DB
\ Compressing backup of Mongo DB
| Compressing backup of Mongo DB
/ Compressing backup of Mongo DB
- Compressing backup of Mongo DB
\ Compressing backup of Mongo DB
| Compressing backup of Mongo DB
--->8===
Expected results:
it would be nice if there was a --cron or similar option that still gets me the needed output but suppresses the spinner animation
Additional info:
I expect most users will just redirect all output to /dev/null, but that makes it hard to notice a problem with the cron job.
Description of problem: if I use satellite maintain backup via cron, the notification mails I get are very large (multiple hundreds of KB) it would be nice if the tool had a commandline flag that makes it less chatty (e.g. --cron) Version-Release number of selected component (if applicable): satellite-maintain-0.0.1-1.el7sat.noarch How reproducible: always Steps to Reproduce: 1. have a cron job that runs `satellite maintain backup …` 2. receive cron email 3. look at size of email Actual results: this 50 15 * * * root satellite-maintain backup offline --assumeyes --skip-pulp-content --preserve-directory --include-db-dumps /var/sat-backup-test just produced a 941 KiB email. Because the used spinner animation (very useful when using the backup tool interactively) produces a lot output like the following ===8<--- | Compressing backup of Mongo DB / Compressing backup of Mongo DB - Compressing backup of Mongo DB \ Compressing backup of Mongo DB | Compressing backup of Mongo DB / Compressing backup of Mongo DB - Compressing backup of Mongo DB \ Compressing backup of Mongo DB | Compressing backup of Mongo DB --->8=== Expected results: it would be nice if there was a --cron or similar option that still gets me the needed output but suppresses the spinner animation Additional info: I expect most users will just redirect all output to /dev/null, but that makes it hard to notice a problem with the cron job.