Bug 2166875

Summary:	[DDF] This section is missing the actual information on how to install the package that provides the resource agents
Product:	Red Hat Enterprise Linux 9	Reporter:	Direct Docs Feedback <ddf-bot>
Component:	Documentation	Assignee:	Jiri Herrmann <jherrman>
Documentation sub component:	DDF	QA Contact:	Brandon Perkins <bperkins>
Status:	POST ---	Docs Contact:
Severity:	unspecified
Priority:	high	CC:	bperkins, fdanapfe, rhel-docs, slevine
Version:	unspecified	Keywords:	Documentation
Target Milestone:	rc	Flags:	jherrman: needinfo? (bperkins) jherrman: needinfo? (bperkins)
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Direct Docs Feedback 2023-02-03 10:23:02 UTC

This section is missing the actual information on how to install the package that provides the resource agents mentioned later on.

For RHEL 9 the cloud-specific resource agents like awsvip have apparently been moved to a separate resource-agents-cloud package: https://access.redhat.com/downloads/content/resource-agents-cloud/4.10.0-23.el9_1.3/x86_64/fd431d51/package

Therefore customers actually need to install the resource-agents-cloud package instead of the resource-agents package,

Reported by: rhn-engineering-fdanapfel

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/deploying_red_hat_enterprise_linux_9_on_public_cloud_platforms/configuring-a-red-hat-high-availability-cluster-on-aws_deploying-a-virtual-machine-on-aws#annotations:7dd73dab-2024-4ff9-84d0-ed0364ed0aac

Comment 14 Jiri Herrmann 2023-05-04 10:28:23 UTC

*** Bug 2163334 has been marked as a duplicate of this bug. ***

Comment 15 Jiri Herrmann 2023-05-04 10:30:55 UTC

*** Bug 2166873 has been marked as a duplicate of this bug. ***