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.
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
(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.
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.
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.