Bug 1522734

Summary:	Upgrade to 6.3 hides ReX templates
Product:	Red Hat Satellite	Reporter:	Lukas Zapletal <lzap>
Component:	Remote Execution	Assignee:	Adam Ruzicka <aruzicka>
Status:	CLOSED ERRATA	QA Contact:	Lukas Pramuk <lpramuk>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.3.0	CC:	aruzicka, bbuckingham, bkearney, brubisch, dnagarat, ehelms, inecas, lpramuk, lzap, mhulan, mmccune, peter.vreman
Target Milestone:	Unspecified	Keywords:	PrioBumpField, PrioBumpQA, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tfm-rubygem-foreman_remote_execution-1.3.7.2-1.fm1_14	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-02-21 16:54:17 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:
Bug Depends On:
Bug Blocks:	1122832, 1533259

Description Lukas Zapletal 2017-12-06 10:44:34 UTC

Due to taxonomy changes in 6.3, templates without any taxonomy are no longer visible. Users after upgrade won't see them anymore in the UI.

According to Marek, the solution for ReX is to explicitly associate with all Orgs/Locs during migration:

https://github.com/theforeman/foreman/pull/3416/files#diff-151633105c29141fe3aac7603de185a5

Comment 4 Adam Ruzicka 2017-12-06 12:20:38 UTC

Created redmine issue http://projects.theforeman.org/issues/21888 from this bug

Comment 5 Adam Ruzicka 2017-12-17 16:43:04 UTC

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

Comment 6 Mike McCune 2018-01-04 01:29:48 UTC

Is this not a regression post-upgrade?

Comment 8 Ivan Necas 2018-01-08 14:39:03 UTC

I think it a regression, we are looking into it this iteration

Comment 9 Satellite Program 2018-01-10 15:19:39 UTC

Upstream bug assigned to aruzicka

Comment 10 Satellite Program 2018-01-10 15:19:49 UTC

Upstream bug assigned to aruzicka

Comment 11 Satellite Program 2018-01-16 17:19:37 UTC

Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/21888 has been resolved.

Comment 13 Lukas Pramuk 2018-02-01 11:08:55 UTC

VERIFIED.

@satellite-6.3.0-23.0.el7sat.noarch
tfm-rubygem-foreman_remote_execution-1.3.7.2-1.fm1_15.el7sat.noarch

by this manual reproducer: 

1. On Sat 6.2 disassociate the chosen job template with all orgs/locs

2. Upgrade to 6.3

3. Check if the job template is visible at UI with "Any Context" set

>>> template is visible

Comment 14 Lukas Pramuk 2018-02-01 12:09:56 UTC

Fixed reproducer:

1. Upgrade 

2. Check if the usual job templates are visible at UI with "Default Organization" context

Comment 15 Satellite Program 2018-02-21 16:54:17 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, 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-2018:0336