Skip to content

Commit 8750178

Browse files
authored
Merge pull request #90177 from jldohmann/OSDOCS-3494
OSDOCS-3494: add live media validation procedure
2 parents 1fbf5ef + d4ca1e7 commit 8750178

File tree

2 files changed

+37
-1
lines changed

2 files changed

+37
-1
lines changed

installing/validation_and_troubleshooting/validating-an-installation.adoc

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,10 @@ include::_attributes/common-attributes.adoc[]
66

77
toc::[]
88

9-
You can check the status of an {product-title} cluster after an installation by following the procedures in this document.
9+
You can check the status of an {product-title} cluster after an installation or validate boot artifacts before an installation by following the procedures in this document.
10+
11+
//Validating RHCOS live media
12+
include::modules/rhcos-validate-live-media.adoc[leveloffset=+1]
1013

1114
//Reviewing the installation log
1215
include::modules/reviewing-the-installation-log.adoc[leveloffset=+1]
Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * installing/validation_and_troubleshooting/valiadting-an-installation.adoc
4+
5+
:_mod-docs-content-type: PROCEDURE
6+
[id="rhcos-validate-live-media_{context}"]
7+
8+
= Validating {op-system} live media
9+
10+
The {product-title} installation program contains pinned versions of {op-system} bootimages. Fully automated installations use these pinned artifacts by default. The mirror registry where you downloaded the installation program contains a `sha256sum` encrypted with the Red{nbsp}Hat product key.
11+
12+
For user-provisioned infrastructure installations, you can access information and use the {product-title} installer to indirectly validate {op-system} bootimage artifacts using their SHA-256 checksums.
13+
14+
.Procedure
15+
16+
* Run the following command to print the metadata for any bootimage artifact:
17+
+
18+
[source,terminal]
19+
----
20+
$ openshift-install coreos print-stream-json | jq <bootimage> <1>
21+
----
22+
<1> The query for the bootimage you want to obtain information on. For validation purposes, the bootimage artifact must have a generated `sha256sum`. This can include OVA, VHD, QCOW2 and others. For example, to get information on an `x86_64` architecture `iso` file for bare metal platforms, this value would be `.architectures.x86_64.artifacts.metal.formats.iso`.
23+
+
24+
.Example output
25+
[source,text]
26+
----
27+
{
28+
"disk": {
29+
"location": "<url>/art/storage/prod/streams/<release>/builds/rhcos-<release>-live.<architecture>.<artifact>",
30+
"sha256": "abc2add9746eb7be82e6919ec13aad8e9eae8cf073d8da6126d7c95ea0dee962"
31+
}
32+
}
33+
----

0 commit comments

Comments
 (0)