Bug 1957144

Summary:	[RFE] Should not be able to publish the content view while repository sync is in progress.
Product:	Red Hat Satellite	Reporter:	rakesh kumar <rakumar>
Component:	Content Views	Assignee:	Samir Jha <sajha>
Status:	CLOSED MIGRATED	QA Contact:	David Moore <damoore>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.9.0	CC:	ahumbe, damoore, dsinglet, onerleka, rlavi, sajha, saydas
Target Milestone:	Unspecified	Keywords:	FutureFeature, MigratedToJIRA, PrioBumpGSS, Reopened, Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-06 00:47:59 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 rakesh kumar 2021-05-05 09:10:34 UTC

Description of problem:

Should not be allowed to publish the content view while the repository attached to the content view is getting sync as this can cause incorrect metadata in the content view. 


Version-Release number of selected component (if applicable):
Satellite 6

How reproducible:
Always.

Steps to Reproduce:
1. Start repo sync for RHEL7
2. While sync is in progress, publish a content view that has RHEL7 repo in it.

Actual results:
We are able to publish the content view.

Expected results:
We should not be allowed to publish the content or there should be a warning message saying 'Repository sync is in progress, publish the content view while the sync is in progress is not recommended and can cause incorrect metadata'


Additional info:

Comment 2 Ashish Humbe 2022-07-05 09:11:28 UTC

*** Bug 2100423 has been marked as a duplicate of this bug. ***

Comment 4 Brad Buckingham 2022-11-03 21:48:51 UTC

Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 5 Brad Buckingham 2022-12-02 17:27:05 UTC

Thank you for your interest in Red Hat Satellite. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you.

Comment 7 Brad Buckingham 2023-10-30 11:29:29 UTC

Bulk setting Target Milestone = 6.15.0 where sat-6.15.0+ is set.

Comment 10 Eric Helms 2024-06-06 00:47:59 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.