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

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

cloud-init-20.3-6.el8

Test result about checking typos in man page,
# man-page-corr.sh /usr/share/man-page-corr/qe-dictionary /usr/share/man/man1/cloud-id.1.gz
# man-page-corr.sh /usr/share/man-page-corr/qe-dictionary /usr/share/man/man1/cloud-init-per.1.gz
# man-page-corr.sh /usr/share/man-page-corr/qe-dictionary /usr/share/man/man1/cloud-init.1.gz

A typo is in /usr/share/man/man1/cloud-init.1.gz
---
Cloud-init provides a mechanism for cloud instance initialization.
This is done by identifying the cloud platform that is in use, reading
provided cloud metadata and optional vendor and user
data, and then intializing the instance as requested.
               ~~~~~~~~~~~

It should be 'initializing'.

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 (cloud-init bug fix and enhancement update), 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/RHEA-2021:1827

Thank you for bringing this to our attention! You’re absolutely right—the word should indeed be “initializing” instead of “intializing.” Typos can sometimes sneak past even the most careful eyes.

Here’s the corrected sentence: https://www.maxim-timeclock.com

“Cloud-init provides a mechanism for cloud instance initialization. This is done by identifying the cloud platform that is in use, reading provided cloud metadata and optional vendor and user data, and then initializing the instance as requested.”

Your keen eye for detail is appreciated!

I would like to point out that most of the users do NOT know that the operation completed. How will they know? They just get a time out error 

Usually getting an error like "Operation Timeout, error" or something like that means the operation DID not complete. 


So no one is using this bulk changing feature because they think it errors out. https://www.vanilla-giftcardbalance.com