Skip to content

Commit 8b9216e

Browse files
committed
OSDOCS-7596: correct space in attribute code block notation
1 parent 240107f commit 8b9216e

File tree

80 files changed

+234
-234
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

80 files changed

+234
-234
lines changed

_unused_topics/microshift-man-config-ovs-bridge.adoc

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -7,31 +7,31 @@
77

88
//* Initiate OVS:
99
//+
10-
//[source, terminal]
10+
//[source,terminal]
1111
//----
1212
//$ sudo systemctl enable openvswitch --now
1313
//----
1414
//* Add the network bridge:
1515
//+
16-
//[source, terminal]
16+
//[source,terminal]
1717
//----
1818
//$ sudo ovs-vsctl add-br br-ex
1919
//----
2020
//* Add the interface to the network bridge:
2121
//+
22-
//[source, terminal]
22+
//[source,terminal]
2323
//----
2424
//$ sudo ovs-vsctl add-port br-ex <physical-interface-name>
2525
//----
2626
//The `<physical-interface-name>` is the network interface name where the node IP address is assigned.
2727
//* Get the bridge up and running:
2828
//+
29-
//[source, terminal]
29+
//[source,terminal]
3030
//----
3131
//$ sudo ip link set br-ex up
3232
//----
3333
//* After `br-ex up` is running, assign the node IP address to `br-ex` bridge:
34-
//[source, terminal]
34+
//[source,terminal]
3535
//----
3636
//$ sudo ...
3737
//----

_unused_topics/microshift-nodeport-unreachable-workaround.adoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -21,21 +21,21 @@ Run the commands listed in each step that follows to restore the `NodePort` serv
2121

2222
. Find the name of the ovn-master pod that you want to restart by running the following command:
2323
+
24-
[source, terminal]
24+
[source,terminal]
2525
----
2626
$ pod=$(oc get pods -n openshift-ovn-kubernetes | grep ovnkube-master | awk -F " " '{print $1}')
2727
----
2828

2929
. Force a restart of the of the ovnkube-master pod by running the following command:
3030
+
31-
[source, terminal]
31+
[source,terminal]
3232
----
3333
$ oc -n openshift-ovn-kubernetes delete pod $pod
3434
----
3535

3636
. Optional: To confirm that the ovnkube-master pod restarted, run the following command:
3737
+
38-
[source, terminal]
38+
[source,terminal]
3939
----
4040
$ oc get pods -n openshift-ovn-kubernetes
4141
----

microshift_troubleshooting/microshift-troubleshoot-backup-restore.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ Data backups are automatic on `rpm-ostree` systems. If you are not using an `rpm
2424
* Logs print to the console during manual backups.
2525
* Logs are automatically generated for `rpm-ostree` system automated backups as part of the {product-title} journal logs. You can check the logs by running the following command:
2626
+
27-
[source, terminal]
27+
[source,terminal]
2828
----
2929
$ sudo journalctl -u microshift
3030
----

modules/architecture-rhcos-updating-bootloader.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ Component EFI
3939
ifndef::openshift-origin[]
4040
+
4141
.Example output for `aarch64`
42-
[source, terminal]
42+
[source,terminal]
4343
----
4444
Component EFI
4545
Installed: grub2-efi-aa64-1:2.02-99.el8_4.1.aarch64,shim-aa64-15.4-2.el8_1.aarch64

modules/cleaning-crio-storage.adoc

Lines changed: 15 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -6,14 +6,14 @@
66
You can manually clear the CRI-O ephemeral storage if you experience the following issues:
77

88
* A node cannot run on any pods and this error appears:
9-
[source, terminal]
9+
[source,terminal]
1010
+
1111
----
1212
Failed to create pod sandbox: rpc error: code = Unknown desc = failed to mount container XXX: error recreating the missing symlinks: error reading name of symlink for XXX: open /var/lib/containers/storage/overlay/XXX/link: no such file or directory
1313
----
1414
+
1515
* You cannot create a new container on a working node and the “can’t stat lower layer” error appears:
16-
[source, terminal]
16+
[source,terminal]
1717
+
1818
----
1919
can't stat lower layer ... because it does not exist. Going through storage to recreate the missing symlinks.
@@ -35,14 +35,14 @@ Follow this process to completely wipe the CRI-O storage and resolve the errors.
3535
.Procedure
3636

3737
. Use `cordon` on the node. This is to avoid any workload getting scheduled if the node gets into the `Ready` status. You will know that scheduling is disabled when `SchedulingDisabled` is in your Status section:
38-
[source, terminal]
38+
[source,terminal]
3939
+
4040
----
4141
$ oc adm cordon <nodename>
4242
----
4343
+
4444
. Drain the node as the cluster-admin user:
45-
[source, terminal]
45+
[source,terminal]
4646
+
4747
----
4848
$ oc adm drain <nodename> --ignore-daemonsets --delete-emptydir-data
@@ -54,15 +54,15 @@ The `terminationGracePeriodSeconds` attribute of a pod or pod template controls
5454
====
5555

5656
. When the node returns, connect back to the node via SSH or Console. Then connect to the root user:
57-
[source, terminal]
57+
[source,terminal]
5858
+
5959
----
6060
6161
$ sudo -i
6262
----
6363
+
6464
. Manually stop the kubelet:
65-
[source, terminal]
65+
[source,terminal]
6666
+
6767
----
6868
# systemctl stop kubelet
@@ -71,65 +71,65 @@ $ sudo -i
7171
. Stop the containers and pods:
7272

7373
.. Use the following command to stop the pods that are not in the `HostNetwork`. They must be removed first because their removal relies on the networking plugin pods, which are in the `HostNetwork`.
74-
[source, terminal]
74+
[source,terminal]
7575
+
7676
----
7777
.. for pod in $(crictl pods -q); do if [[ "$(crictl inspectp $pod | jq -r .status.linux.namespaces.options.network)" != "NODE" ]]; then crictl rmp -f $pod; fi; done
7878
----
7979

8080
.. Stop all other pods:
81-
[source, terminal]
81+
[source,terminal]
8282
+
8383
----
8484
# crictl rmp -fa
8585
----
8686
+
8787
. Manually stop the crio services:
88-
[source, terminal]
88+
[source,terminal]
8989
+
9090
----
9191
# systemctl stop crio
9292
----
9393
+
9494
. After you run those commands, you can completely wipe the ephemeral storage:
95-
[source, terminal]
95+
[source,terminal]
9696
+
9797
----
9898
# crio wipe -f
9999
----
100100
+
101101
. Start the crio and kubelet service:
102-
[source, terminal]
102+
[source,terminal]
103103
+
104104
----
105105
# systemctl start crio
106106
# systemctl start kubelet
107107
----
108108
+
109109
. You will know if the clean up worked if the crio and kubelet services are started, and the node is in the `Ready` status:
110-
[source, terminal]
110+
[source,terminal]
111111
+
112112
----
113113
$ oc get nodes
114114
----
115115
+
116116
.Example output
117-
[source, terminal]
117+
[source,terminal]
118118
+
119119
----
120120
NAME STATUS ROLES AGE VERSION
121121
ci-ln-tkbxyft-f76d1-nvwhr-master-1 Ready, SchedulingDisabled master 133m v1.27.3
122122
----
123123
+
124124
. Mark the node schedulable. You will know that the scheduling is enabled when `SchedulingDisabled` is no longer in status:
125-
[source, terminal]
125+
[source,terminal]
126126
+
127127
----
128128
$ oc adm uncordon <nodename>
129129
----
130130
+
131131
.Example output
132-
[source, terminal]
132+
[source,terminal]
133133
+
134134
----
135135
NAME STATUS ROLES AGE VERSION

modules/cnf-logging-associated-with-adjusting-nic-queues.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,13 +9,13 @@ Log messages detailing the assigned devices are recorded in the respective Tuned
99

1010
* An `INFO` message is recorded detailing the successfully assigned devices:
1111
+
12-
[source, terminal]
12+
[source,terminal]
1313
----
1414
INFO tuned.plugins.base: instance net_test (net): assigning devices ens1, ens2, ens3
1515
----
1616
* A `WARNING` message is recorded if none of the devices can be assigned:
1717
+
18-
[source, terminal]
18+
[source,terminal]
1919
----
2020
WARNING tuned.plugins.base: instance net_test: no matching devices available
2121
----

modules/cnf-performing-end-to-end-tests-running-cyclictest.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -78,7 +78,7 @@ FAIL
7878
The same output can indicate different results for different workloads. For example, spikes up to 18μs are acceptable for 4G DU workloads, but not for 5G DU workloads.
7979

8080
.Example of good results
81-
[source, terminal]
81+
[source,terminal]
8282
----
8383
running cmd: cyclictest -q -D 10m -p 1 -t 16 -a 2,4,6,8,10,12,14,16,54,56,58,60,62,64,66,68 -h 30 -i 1000 -m
8484
# Histogram
@@ -111,7 +111,7 @@ More histogram entries ...
111111
----
112112

113113
.Example of bad results
114-
[source, terminal]
114+
[source,terminal]
115115
----
116116
running cmd: cyclictest -q -D 10m -p 1 -t 16 -a 2,4,6,8,10,12,14,16,54,56,58,60,62,64,66,68 -h 30 -i 1000 -m
117117
# Histogram

modules/cnf-performing-end-to-end-tests-running-hwlatdetect.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -122,7 +122,7 @@ You can capture the following types of results:
122122
* The combined set of the rough tests with the best results and configuration settings.
123123
124124
.Example of good results
125-
[source, terminal]
125+
[source,terminal]
126126
----
127127
hwlatdetect: test duration 3600 seconds
128128
detector: tracer
@@ -142,7 +142,7 @@ Samples recorded: 0
142142
The `hwlatdetect` tool only provides output if the sample exceeds the specified threshold.
143143
144144
.Example of bad results
145-
[source, terminal]
145+
[source,terminal]
146146
----
147147
hwlatdetect: test duration 3600 seconds
148148
detector: tracer

modules/configuring-default-seccomp-profile.adoc

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -15,21 +15,21 @@
1515

1616
.. Verify what pods are running in the namespace:
1717
+
18-
[source, terminal]
18+
[source,terminal]
1919
----
2020
$ oc get pods -n <namespace>
2121
----
2222
+
2323
For example, to verify what pods are running in the `workshop` namespace run the following:
2424
+
25-
[source, terminal]
25+
[source,terminal]
2626
----
2727
$ oc get pods -n workshop
2828
----
2929
+
3030
.Example output
3131
+
32-
[source, terminal]
32+
[source,terminal]
3333
----
3434
NAME READY STATUS RESTARTS AGE
3535
parksmap-1-4xkwf 1/1 Running 0 2m17s
@@ -38,14 +38,14 @@ parksmap-1-deploy 0/1 Completed 0 2m22s
3838
+
3939
.. Inspect the pods:
4040
+
41-
[source, terminal]
41+
[source,terminal]
4242
----
4343
$ oc get pod parksmap-1-4xkwf -n workshop -o yaml
4444
----
4545
+
4646
.Example output
4747
+
48-
[source, terminal]
48+
[source,terminal]
4949
----
5050
apiVersion: v1
5151
kind: Pod
@@ -97,13 +97,13 @@ Conversely with a workload that requires `privilegeEscalation: true` this worklo
9797
[id="newly_installed_{context}"]
9898
== Newly installed cluster
9999

100-
For newly installed {product-title} 4.11 or later clusters, the `restricted-v2` replaces the `restricted` SCC as an SCC that is available to be used by any authenticated user. A workload with `privilegeEscalation: true`, is not admitted into the cluster since `restricted-v2` is the only SCC available for authenticated users by default.
100+
For newly installed {product-title} 4.11 or later clusters, the `restricted-v2` replaces the `restricted` SCC as an SCC that is available to be used by any authenticated user. A workload with `privilegeEscalation: true`, is not admitted into the cluster since `restricted-v2` is the only SCC available for authenticated users by default.
101101

102102
The feature `privilegeEscalation` is allowed by `restricted` but not by `restricted-v2`. More features are denied by `restricted-v2` than were allowed by `restricted` SCC.
103103

104104
A workload with `privilegeEscalation: true` may be admitted into a newly installed {product-title} 4.11 or later cluster. To give access to the `restricted` SCC to the ServiceAccount running the workload (or any other SCC that can admit this workload) using a RoleBinding run the following command:
105105

106-
[source, terminal]
106+
[source,terminal]
107107
----
108108
$ oc -n <workload-namespace> adm policy add-scc-to-user <scc-name> -z <serviceaccount_name>
109109
----

modules/configuring-haproxy-interval.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ Setting a large value for the minimum HAProxy reload interval can cause latency
2121

2222
* Change the minimum HAProxy reload interval of the default Ingress Controller to 15 seconds by running the following command:
2323
+
24-
[source, terminal]
24+
[source,terminal]
2525
----
2626
$ oc -n openshift-ingress-operator patch ingresscontrollers/default --type=merge --patch='{"spec":{"tuningOptions":{"reloadInterval":"15s"}}}'
2727
----

0 commit comments

Comments
 (0)