Bug 2176841

Summary:	Typo in provisioning template 'Linux host_init_config default'
Product:	Red Hat Satellite	Reporter:	mithun kalyat <mkalyat>
Component:	Provisioning Templates	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	low	Docs Contact:
Priority:	medium
Version:	6.11.4	CC:	lstejska, mhulan
Target Milestone:	Unspecified	Keywords:	EasyFix, MigratedToJIRA, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
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:10:40 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 mithun kalyat 2023-03-09 13:15:10 UTC

Description of problem:

The template "Linux host_init_config default" has a typo in its description section:

---
description: |
  This template is used during the host registration to perform the initial host configuration. After the host
  is created by starting the registration, the registration script asks for the host init config script, that
  is rendered based on this template. It is rendered for the specific host therefore it contains instructions
  specific for the OS of the host. It's content can differ based on any parameters applicable for the host.
---

The sentence beginning "It's content can differ based on any parameters applicable for the host." has an apostrophe in the "It's" - grammatically this should be "Its" and the apostrophe/quote mark renders the rest of the script as one long string (it is all 'yellow' in the template editor)


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

Satellite 6.11


Additional info:

Attaching screenshot for the reference.

Comment 2 Eric Helms 2024-06-06 16:10:40 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.