This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 2262120 - {Job|report|provisioning} templates from plugins not updated in database after upgrade
Summary: {Job|report|provisioning} templates from plugins not updated in database afte...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Reporting
Version: 6.14.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-01-31 17:25 UTC by Jeremy Lenz
Modified: 2024-06-06 17:01 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 17:01:19 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github theforeman foreman pull 10038 0 None open Fixes #37143 - Register plugin's template dirs for db:seed 2024-04-17 14:18:55 UTC
Red Hat Issue Tracker   SAT-23000 0 None Migrated None 2024-06-06 17:01:18 UTC

Description Jeremy Lenz 2024-01-31 17:25:19 UTC 
Description of problem:

The "Convert2RHEL analyze" was added in Satellite 6.14.1. However, when upgrading from 6.14.0 > 6.14.1, the job template does not show in the web UI.

This is because Foreman only re-seeds the database when seed files have changed, but does not check template files.

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

Satellite 6.14.0 > 6.14.1

How reproducible: always


Steps to Reproduce:
1. Upgrade to 6.14.1 from 6.14.0
2. Note that the following file is present: /usr/share/gems/gems/foreman_remote_execution-10.1.2/app/views/templates/script/convert2rhel_analyze.erb

Actual results:

Even though that file is present on the system, the "Convert2RHEL Analyze" job template does not show up in the web UI in the job wizard, or in Job Templates.

Expected results:

The "Convert2RHEL Analyze" job template (and any other new or changed templates) is present in the database and web UI


Additional info:

This bug applies to any template type (report, job, provisioning) and happens if none of the seed files change since the last upgrade
Comment 1 Jeremy Lenz 2024-01-31 17:28:40 UTC 
Workaround:

1. In foreman-rake console, run 

```
ForemanInternal.all.first.destroy
```

2. foreman-rake db:seed

This should force the new templates to show.
Comment 4 Eric Helms 2024-06-06 17:01:19 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.
Note You need to log in before you can comment on or make changes to this bug.