-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.21.z
-
None
-
False
-
-
None
-
Moderate
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
Brief Description:
In section 6.8 (Manually creating IAM), the documented workflow first instructs running `openshift-install create manifests`, which consumes and removes the `install-config.yaml` file from the installation directory. However, a later step requires passing `--install-config=<path>/install-config.yaml` to the `oc adm release extract --credentials-requests` command. At this stage, the `install-config.yaml` file no longer exists, causing confusion and command failure. The documentation does not mention preserving a copy of the file or recreating it before this step.
Suggested Fix:
One of the following clarifications should be added before running `create manifests`:
Option 1 (Recommended - simplest):
Add an explicit note before Step 2:
> The `create manifests` command consumes the `install-config.yaml` file. Before running this command, create a backup copy of the file (for example, `cp install-config.yaml install-config.yaml.bak`) and use that backup when running the `oc adm release extract --credentials-requests` command.
Then update the example command to reference the backup file:
```
--install-config=<path>/install-config.yaml.bak
```
Option 2 (Alternative approach):
Reorder the steps so that the `oc adm release extract --credentials-requests` command is executed before running `openshift-install create manifests`, ensuring the `install-config.yaml` file is still present.
Either of these corrections would prevent command failure and remove ambiguity for users performing manual CCO setup on IBM Cloud VPC.