Example from https://rhn.redhat.com/errata/RHBA-2016-0315.html : "This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/articles/11258" But the above link is for RHEL, and is irrelevant for RHEV. Instead, let's use RHEV upgrade processes: For minor releases upgrade: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.6/html-single/Upgrade_Guide/index.html#chap-Updates_between_Minor_Releases For major releases upgrade: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.6/html-single/Upgrade_Guide/index.html#chap-Upgrading_to_Red_Hat_Enterprise_Virtualization_3.6
And for 4.0 advisories: For updating between minor releases, see: https://access.redhat.com/documentation/en/red-hat-virtualization/4.0/single/upgrade-guide#chap-Updates_between_Minor_Releases For upgrading to a major release, see: https://access.redhat.com/documentation/en/red-hat-virtualization/4.0/single/upgrade-guide/#chap-Upgrading_to_Red_Hat_Virtualization_4.0
Joey, will this happen for 4.0.5?
Hi Lucy, Looking into how RHEL does it - they use this central KB: https://access.redhat.com/articles/11258 that they keep updated with each release. I think we should go this way as well. In addition, we can link the upgrade helper to that page as well, which would be twice beneficial. So yes, I am voting for this solution of having errata redirecting to 1 KB solution. Sorry for late response.
Too late for 4.0.6, moving to 4.0.7.
New errata created with template are using correct KB link