Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-31297

typo for scheduable and succesfully

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor Minor
    • None
    • 4.13.z, 4.12.z, 4.14.z, 4.15.z
    • Documentation / CNF
    • Low
    • No
    • 1
    • T&PS 2024 #8
    • 1
    • False
    • Hide

      None

      Show
      None
    • Hide
      2024-08-05: Created CP PRs for 4.12 and 4.13.
      - Requested merge review.
      - PRs merged.

      2024-08-02: PR merged. CP required for 4.12 and 4.13

      2024-08-01: Peer review done

      2024-07-29: Created a PR - https://github.com/openshift/openshift-docs/pull/79611
      - Requested peer review





      Show
      2024-08-05: Created CP PRs for 4.12 and 4.13. - Requested merge review. - PRs merged. 2024-08-02: PR merged. CP required for 4.12 and 4.13 2024-08-01: Peer review done 2024-07-29: Created a PR - https://github.com/openshift/openshift-docs/pull/79611 - Requested peer review

      Description of problem:

      https://docs.openshift.com/container-platform/4.15/scalability_and_performance/cnf-numa-aware-scheduling.html

      Verify that NUMA-aware scheduable nodes have the noderesourcetopologies CR applied to them. Run the following command:

      scheduable should be schedulable

      Run the following command to check that the CRD is created succesfully: 

      succesfully should be successfully

      the issue is in 4.12+ docs, also checked in openshift-docs repo, same typo in files

       

      $ grep -r "succesfully"
      modules/cnf-checking-numa-aware-scheduler-logs.adoc:.. Run the following command to check that the CRD is created succesfully:
      modules/nodes-vsphere-machine-set-concept-static-ip.adoc:The machine controller updates the machine with a status of `IPAddressClaimed` to indicate that a static IP address has succesfully bound to the `IPAddressClaim` resource. The machine controller applies the same status to a machine with multiple `IPAddressClaim` resources that each contain a bound static IP address.The machine controller then creates a virtual machine and applies static IP addresses to any nodes listed in the `providerSpec` of a machine's configuration.
      modules/verifying-cluster-install-oci.adoc:Verify that your cluster was installed and is running effectively on {oci-first}. To succesfully install a cluster and deploy it on {oci-first}, you must create specific {oci} infrastucture resources. Additionally, you must ensure that the Assisted Installer can access these {oci} infrastucture resources.
      rest_api/console_apis/consolequickstart-console-openshift-io-v1.adoc:| success describes the succesfully passed task. 

      and

      $ grep -r "scheduable"
      modules/cnf-troubleshooting-numa-aware-workloads.adoc:. Verify that NUMA-aware scheduable nodes have the `noderesourcetopologies` CR applied to them. Run the following command:
      modules/cnf-troubleshooting-numa-aware-workloads.adoc:. Verify the NUMA zone granularity for all scheduable nodes by running the following command:
      modules/multi-architecture-modify-machine-set-aws.adoc:. You can check that the nodes are ready and scheduable with the following command:
      modules/multi-architecture-modify-machine-set-gcp.adoc:. You can check that the nodes are ready and scheduable with the following command:
      modules/multi-architecture-modify-machine-set.adoc:. You can check that the nodes are ready and scheduable with the following command: 

      Version-Release number of selected component (if applicable):

       

      4.12+

      How reproducible:

      always

      Steps to Reproduce:

      1. see the description

              rhn-support-srir Srikanth R
              juzhao@redhat.com Junqi Zhao
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: