Bug 1589828

Summary:	6.2.14 --> 6.3 Upgrade sometimes does not transport user_mail_notifications
Product:	Red Hat Satellite	Reporter:	wclark
Component:	Installer	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED WONTFIX	QA Contact:	Devendra Singh <desingh>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.3.0	CC:	ehelms, wclark
Target Milestone:	Unspecified	Keywords:	Triaged, Upgrades
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:	2020-02-03 16:27:50 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 wclark 2018-06-11 13:18:15 UTC

Description of problem:

Sometimes after the installer is run, the mail notifications do not survive the upgrade to Satellite 6.3 either in the WebUI or in the user_mail_notifications table in postgres foreman DB.

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

6.2.14 --> 6.3.x

How reproducible:

Happens some of the time

Steps to Reproduce:
1. Configure a user to have mail notifications (e.g. on repo sync) on Satellite 6.2.14
2. Upgrade Satellite to 6.3.x
3. Observe whether mail notifications were persisted on Satellite WebUI and/or on user_mail_notifications table

Actual results:

some user_mail_notifications did not survive the upgrade

Expected results:

user_mail_notifications are the same post upgrade as they were configured pre upgrade

Additional info:

Somtimes this appears to affect only what is displayed in the WebUI, in other cases it appears to affect the actual contents of the DB

Comment 1 Brad Buckingham 2018-06-12 17:18:52 UTC

Do we have an internal reproducer to debug this issue?

Comment 3 wclark 2018-11-01 17:54:22 UTC

(In reply to Brad Buckingham from comment #1)
> Do we have an internal reproducer to debug this issue?

Brad, I have attempted to reproduce the issue internally but was not successful.

Comment 5 Bryan Kearney 2020-01-15 21:00:34 UTC

The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.

Comment 6 Bryan Kearney 2020-02-03 16:27:50 UTC

Thank you for your interest in Satellite 6. 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, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.