Bug 1994022

Summary:	Total steps: 0/0 in sync status
Product:	Red Hat Satellite	Reporter:	Kenny Tordeurs <ktordeur>
Component:	Repositories	Assignee:	Justin Sherrill <jsherril>
Status:	CLOSED ERRATA	QA Contact:	addubey
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	6.10.0	CC:	addubey, jsherril, ttereshc, zhunting
Target Milestone:	6.10.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	tfm-rubygem-katello-4.1.1.22-1,tfm-rubygem-katello-4.1.1.28-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-11-16 14:13:10 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 Kenny Tordeurs 2021-08-16 14:23:38 UTC

Description of problem:
When syncing several repositories some of them are listed with a status 'Total steps: 0/0' 

Version-Release number of selected component (if applicable):
satellite-6.10.0-0.6.beta.el7sat.noarch

How reproducible:
100%

Steps to Reproduce:
1. Sync many repos
2.
3.

Actual results:
Sync status page will have some repositories showing with a status 'Total steps: 0/0' 

Expected results:
Something more accurate

Additional info:

Comment 3 Justin Sherrill 2021-08-31 20:22:04 UTC

we could easily show 'Not started' message if we're in a 0/0 situation.

Comment 4 Kenny Tordeurs 2021-09-01 07:17:16 UTC

I think 'Not started' or 'Queued' would be more indicative of what is going on.

Comment 5 Justin Sherrill 2021-09-13 18:57:46 UTC

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

Comment 8 addubey 2021-10-05 10:49:42 UTC

Verified.


Tested on: Satellite-6.10.0 Snap 21.0


Steps followed: 

1. Syncing many repositories.


Observation: Details column shows the "Waiting to start" message and initiates the Total steps count.

Comment 11 errata-xmlrpc 2021-11-16 14:13:10 UTC

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 (Moderate: Satellite 6.10 Release), 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/RHSA-2021:4702