Bug 2221983

Summary:	Satellite throws error undefined method `html_safe' for nil:NilClass when autoprovision/provision is initiated for a discovered host
Product:	Red Hat Satellite	Reporter:	addubey
Component:	Discovery Plugin	Assignee:	Leos Stejskal <lstejska>
Status:	VERIFIED ---	QA Contact:	addubey
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.14.0	CC:	lstejska, nalfassi, shwsingh, zhunting
Target Milestone:	6.14.0	Keywords:	AutomationBlocker, Regression, Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	rubygem-katello-4.9.0.4-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		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 addubey 2023-07-11 12:12:19 UTC

Description of problem: Satellite throws error undefined method `html_safe' for nil:NilClass when autoprovision/provision is initiated for a discovered host


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


How reproducible: Always


Steps to Reproduce:
1. Create a discovered host.
2. Try to provision or auto-provision the host.


Actual results: The server throws undefined method `html_safe' for nil:NilClass


Expected results: It should proceed for further provisioning 


Additional info:

Comment 2 addubey 2023-07-11 12:34:17 UTC

Works well with 6.13

Comment 3 Leos Stejskal 2023-07-17 06:46:08 UTC

Hi,
do you have a site where I can reproduce the issue? I tried to reproduce it on foreman+discovery but it's working for me.
I guess the error is coming from somewhere other than Foreman / Discovery.

Comment 5 Leos Stejskal 2023-07-18 08:00:24 UTC

Created redmine issue https://projects.theforeman.org/issues/36601 from this bug

Comment 6 Bryan Kearney 2023-07-18 16:03:41 UTC

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