Skip to content

[enterprise-4.5] BZ1851320 - updated metadata file extension #30063

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
codyhoag merged 1 commit into from
Mar 3, 2021
Merged

[enterprise-4.5] BZ1851320 - updated metadata file extension #30063

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion modules/installation-osp-creating-bootstrap-machine.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ Create a bootstrap machine and give it the network access it needs to run on {rh
.Prerequisites
* The `inventory.yaml` and `common.yaml` Ansible playbooks in a common directory
** If you need these files, copy them from *Creating network resources*
* The `metadata.yaml` file that the installation program created is in the same directory as the Ansible playbooks
* The `metadata.json` file that the installation program created is in the same directory as the Ansible playbooks

.Procedure

Expand Down
2 changes: 1 addition & 1 deletion modules/installation-osp-creating-compute-machines.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ After standing up the control plane, create compute machines.
.Prerequisites
* The `inventory.yaml` and `common.yaml` Ansible playbooks in a common directory
** If you need these files, copy them from *Creating network resources*
* The `metadata.yaml` file that the installation program created is in the same directory as the Ansible playbooks
* The `metadata.json` file that the installation program created is in the same directory as the Ansible playbooks
* The control plane is active

.Procedure
Expand Down