Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1690490

Summary:	Can't check a RHEL8 system for insights client installation
Product:	Red Hat Satellite 5	Reporter:	Lukáš Hellebrandt <lhellebr>
Component:	redhat-access-plugin-sat5	Assignee:	Michael Mráka <mmraka>
Status:	CLOSED ERRATA	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	580	CC:	rdrazny, robwilli, tkasparek, tlestach
Target Milestone:	---	Keywords:	Regression, Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	redhat-access-plugin-sat5-2.1.0-62.el6sat spacewalk-java-2.5.14-132-sat	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-19 18:11:14 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 Lukáš Hellebrandt 2019-03-19 15:02:10 UTC

Description of problem:
In Admin -> Insights -> Setup, I can't check a RHEL8 system (grey checkbox). That is most likely because Satellite checks whether the system has rhn-tools channel. However, there is no rhn-tools channel for RHEL8 and insights client packages are in Appstream.

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

How reproducible:
Deterministic

Steps to Reproduce:
1. Have a Sat with RHEL8 BaseOS and Appstream synced
2. Register a RHEL8 client
3. Go to Admin -> Insights -> Setup

Actual results:
Can't check the system

Expected results:
Can check the system and the insights-client package gets installed

Additional info:
Marking as regression because this will hit the customers who start using RHEL8

Somewhat related BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1686046

Comment 2 Lukáš Hellebrandt 2019-03-20 11:20:38 UTC

Closing NOTABUG based on https://bugzilla.redhat.com/show_bug.cgi?id=1577203#c15

Comment 3 Tomas Lestach 2019-05-14 16:03:58 UTC

Reopening.

Comment 4 Michael Mráka 2019-05-31 08:58:07 UTC

Fixed by
commit ecdacbf4fc2fcd0be34b078bb9f0e98c243bfb43
    1690490 - client rpm has been renamed to insights-client

Comment 7 Radovan Drazny 2019-06-04 15:23:35 UTC

    Tested with redhat-access-plugin-sat5-2.1.0-61. A RHEL8 system can be checked now, but trying to apply the scheduling fails with the following error in the /var/log/tomcat6/catalina.out:

    <...>
    .ModulesNotAllowedException: At least one of the channels this system is subscribed to contains modules. If you have activated modules on this system, please refrain from using Red Hat Satellite for package operations. Instead, perform all package actions from the client using dnf.
    <...>

    This is actually probably expected, as we usually don't want to schedule package install from a repo with modular content using the Sat 5 WebUI. But it is an issue for insights-client installation scheduling in this scenario.

Comment 9 Michael Mráka 2019-06-11 07:28:13 UTC

API issue fixed in spacewalk git by
commit 94d6c60ccbb70bd8bbf350332d9a54033d46018e
    1690490 - fix API to use objects as params

Comment 10 Michael Mráka 2019-06-11 07:32:02 UTC

Backported to SATELLITE-5.8 as
commit 74ec91e7569e7b95ef9ebfaf74945a83c18d9971
    1690490 - fix API to use objects as params

Comment 12 Radovan Drazny 2019-06-14 11:42:39 UTC

Verified with redhat-access-plugin-sat5-2.1.0-62.el6sat and spacewalk-java-2.5.14-132-sat. I was able to check a RHEL 8 system for Insights setup, and after running rhn_check, the insights-client package has been correctly installed and is able to register into Sat 5 server working as an Insights proxy. 

VERIFIED

Comment 14 errata-xmlrpc 2019-06-19 18:11:14 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/RHBA-2019:1551