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:
Yuko raised an issue with the current version of the guide when she was translating it, under "6.2. Upgrading a Red Hat Enterprise Virtualization Hypervisor with local media" the following text appears in the html (and no doubt other output formats):
Once prepared the local media is used to boot the Hypervisor with the upgrade parameter as described in Procedure 6.1, “”.
It appears the procedure being referred to is the one directly after this text, which doesn't have a title. In this situation it's likely the best resolution will be to remove the link and reword the sentence to cater for the change.
Version-Release number of selected component (if applicable):
Red_Hat_Enterprise_Linux-Hypervisor_Deployment_Guide-6-en-US-2-2
Additional info:
> I picked up one more error during proofreading:
>
> File: Upgrading
> String:Once prepared the local media is used to boot the Hypervisor
> with the <literal>upgrade</literal>
> parameter as described in <xref
> linkend="proc-Deployment_Guide-Upgrading_Red_Hat_Enterprise_Virtualization_Hypervisors-With_Local_Media"
> />.
> Comment: The link appears empty when built.
>
> Will you check the file for me and let me know how to fix it?
Description of problem: Yuko raised an issue with the current version of the guide when she was translating it, under "6.2. Upgrading a Red Hat Enterprise Virtualization Hypervisor with local media" the following text appears in the html (and no doubt other output formats): Once prepared the local media is used to boot the Hypervisor with the upgrade parameter as described in Procedure 6.1, “”. It appears the procedure being referred to is the one directly after this text, which doesn't have a title. In this situation it's likely the best resolution will be to remove the link and reword the sentence to cater for the change. Version-Release number of selected component (if applicable): Red_Hat_Enterprise_Linux-Hypervisor_Deployment_Guide-6-en-US-2-2 Additional info: > I picked up one more error during proofreading: > > File: Upgrading > String:Once prepared the local media is used to boot the Hypervisor > with the <literal>upgrade</literal> > parameter as described in <xref > linkend="proc-Deployment_Guide-Upgrading_Red_Hat_Enterprise_Virtualization_Hypervisors-With_Local_Media" > />. > Comment: The link appears empty when built. > > Will you check the file for me and let me know how to fix it?