Bug 1830825

Summary:	[RFE] Check for certain types of running Pulp related foreman tasks before starting an offline backup
Product:	Red Hat Satellite	Reporter:	Hao Chang Yu <hyu>
Component:	Satellite Maintain	Assignee:	Suraj Patil <supatil>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.7.0	CC:	ahumbe, apatel, aupadhye, dsinglet, ehelms, kgaikwad
Target Milestone:	Unspecified	Keywords:	FutureFeature, MigratedToJIRA, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-05 21:38:07 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Hao Chang Yu 2020-05-04 03:03:41 UTC

Description of problem:
If will be great if the backup script can check for certain types of running Pulp related task, such as CV publish/promote tasks, Repo sync tasks and Capsule sync tasks. If found any of these tasks are running then do not proceed to do the offline backup.

It may be a plus if user can have an option to set the maximum time (such as 1 hour) to wait for the tasks to finish. The backup will then wait and postpone until the time.

Use case:
User is doing a daily offline backup in the morning. One day, user started a full Capsule sync to fix the missing contents on the Capsule in the afternoon. Due to the large number of repositories to sync, the task is taking more than half day to complete. This causes the time overlap between the Satellite offline backup and Capsule sync.

Comment 3 Suraj Patil 2020-05-13 06:08:24 UTC

Created redmine issue https://projects.theforeman.org/issues/29760 from this bug

Comment 7 Bryan Kearney 2022-05-12 08:02:05 UTC

Upstream bug assigned to supatil

Comment 8 Bryan Kearney 2022-05-12 08:02:07 UTC

Upstream bug assigned to supatil

Comment 9 Bryan Kearney 2022-07-26 16:02:02 UTC

Upstream bug assigned to supatil

Comment 10 Bryan Kearney 2022-07-26 16:02:04 UTC

Upstream bug assigned to supatil

Comment 11 Eric Helms 2024-06-05 21:38:07 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.