-
Bug
-
Resolution: Duplicate
-
Major
-
ACM 2.10.0, ACM 2.11.0
-
None
Note: Doc team updates the current version of the documentation and the
two previous versions (n-2), but we address *only high-priority, or
customer-reported issues* for -2 releases in support.
Describe the changes in the doc and link to your dev story:
1. - [ ] Mandatory: Add the required version to the Fix version/s field.
- All versions (At least 2.11 and 2.10)
2. - [ ] Mandatory: Choose the type of documentation change or review.
- We need to update to an existing topic
3. - [ ] *Mandatory: *Use the following link to open the doc and find where the
documentation update should go. Note: As the feature and doc is
understood and developed, this placement decision may change:
- Published doc: https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.11/html-single/clusters/index
4. - [ ] Mandatory for GA content:
5. - [ ] Mandatory for bugs: What is the diff? Clearly define what the
problem is, what the change is, and link to the current documentation. Only
use this for a documentation bug.
As the following items describe, currently it's not supported to mix the Discovery ISO boot method[1] and the BareMetalHost resource method[2] in the same InfraEnv resource.
I think the ACM document should mention this point.
Especially, the following document instruct us to use the Discovery ISO method.
I think we should state that Discovery ISO method doesn't work when we already used the BareMetalHost method.
In this case, we should create a BareMetalHost resource instead of using the Discovery ISO.
[1]https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.11/html-single/clusters/index#add-host-host-inventory
[2]https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.11/html-single/clusters/index#auto-add-host-host-inventory