Bug 2225423

Summary:	cloudInitNoCloud userdata exceeds 2048 byte limit
Product:	Red Hat Satellite	Reporter:	Wolfgang Marx <wmarx>
Component:	Compute Resources - CNV	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.13.2	CC:	ahumbe, bbuckingham.nc, lstejska, rlavi
Target Milestone:	Unspecified	Keywords:	MigratedToJIRA, Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-06 16:25:21 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 Wolfgang Marx 2023-07-25 09:52:07 UTC

Description of problem:
Bugs with Creating a host (RHEL8 or RHEL9) with in Openshift Virtualization:
cloudInitNoCloud userdata exceeds 2048 byte limit
Means I can only create one line when assuming right here. We have to deactivate cloud-init “User Data”, otherwise the host won't be created.

Error Message in the production Foreman Log:
cloudInitNoCloud userdata exceeds 2048 byte limit. Should use UserDataSecretRef for larger data. 


Version-Release number of selected component (if applicable):
I'm using Openshift-V Operator in V. 6.12.4 and Satellite 6.13.1/6.13.2. I tried this with creating a RHEL7/8/9 Hosts. Every time I got the same error as described above.

How reproducible:
Try to create a RHEL machine with Satellite on OCP-V, it won't fail - you have to deactivate the tab "user-data".


Actual results:
The RHEL Host won't be created

Expected results:
The RHEL Host should be created on the OCP-V env.

Additional info:

Comment 3 Eric Helms 2024-06-06 16:25:21 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.