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 1861367 - Import Template sync never completes
Summary: Import Template sync never completes
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Templates Plugin
Version: 6.8.0
Hardware: All
OS: All
unspecified
low
Target Milestone: 6.8.0
Assignee: Ondřej Pražák
QA Contact: Ondrej Gajdusek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-07-28 12:25 UTC by Ranjan Kumar
Modified: 2020-10-27 13:05 UTC (History)
3 users (show)

Fixed In Version: tfm-rubygem-foreman_templates-9.0.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 13:04:48 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
screen (159.25 KB, image/png)
2020-07-28 12:25 UTC, Ranjan Kumar
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 30515 0 Normal Closed Import Template sync never completes 2020-10-28 17:45:24 UTC
Red Hat Product Errata RHSA-2020:4366 0 None None None 2020-10-27 13:05:14 UTC

Description Ranjan Kumar 2020-07-28 12:25:22 UTC
Created attachment 1702646 [details]
screen

Description of problem: Importing template using default sync form never completes. make sure the organization and location are select on the top left.


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


How reproducible: always


Steps to Reproduce:
1. Make sure Default organization and Default location is selected on top left
2. Go to Hosts -> Sync Templates
3. do not change anything in the form and press submit
4. Spinner is keep rotating and never completes

Actual results:  Spinner is keep rotating and never completes


Expected results:  Result should be displayed


Additional info:
Additional info:
[root@dhcp130-171 foreman]# rpm -qa satellite
satellite-6.8.0-0.7.beta.el7sat.noarch
[root@dhcp130-171 foreman]# rpm -qa foreman
foreman-2.1.0.1-1.el7sat.noarch
[root@dhcp130-171 foreman]# rpm -qa katello
katello-3.16.0-0.4.rc4.el7sat.noarch

Comment 1 Ondřej Pražák 2020-07-29 10:03:14 UTC
Created redmine issue https://projects.theforeman.org/issues/30515 from this bug

Comment 2 Bryan Kearney 2020-07-29 12:01:04 UTC
Upstream bug assigned to oprazak

Comment 3 Bryan Kearney 2020-07-29 12:01:08 UTC
Upstream bug assigned to oprazak

Comment 4 Ondrej Gajdusek 2020-09-04 11:11:48 UTC
Verified using tfm-rubygem-foreman_templates-9.0.1-1.fm2_1.el7sat.noarch

Comment 7 errata-xmlrpc 2020-10-27 13:04:48 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 (Important: Satellite 6.8 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-2020:4366


Note You need to log in before you can comment on or make changes to this bug.