• Icon: Bug Bug
    • Resolution: Test Pending
    • Icon: Normal Normal
    • None
    • None
    • Sandboxed Containers
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • HCIDOCS 2025#1, HCIDOCS 2025#2, HCIDOCS 2025#3
    • 3

      Ensure peer pods CM image ID is empty

      Issues to fix:

      Title

      • Improve title by using a gerund.
      • Change CM to "config map" per OCP doc guidelines.
      • Do not string 4 adjectives together because this creates localization issues.
      • Suggestion: "Verifying empty image ID in peer pods config map"

      Text

      • Spell out "CR" the first time it occurs.
      • Do not abbreviate "config map" as "CM".
      • "When you delete the KataConfig CR, it should delete the peer pods CM image ID. For AWS and Azure deployments, check to ensure that the peer pods CM image ID is empty." Not very clear. Suggestion: "After you delete the KataConfig custom resource, you must verify that the image ID parameter in the peer pods config map is empty."
      • "oc get cm -n openshift-sandboxed-containers-operator peer-pods-cm -o jsonpath="{.data.AZURE_IMAGE_ID}" - Use a callout for this command. Phrase the options correctly: "Specify x for X or y for Y".
      • Replace AZURE_IMAGE_ID in the command with a user-entered parameter like "<image_id>". Same in patch command.
      • Remove "Check the status stanza of the YAML file." because it duplicates the following step "If the PODVM_AMI_ID parameter...".
      • Last two steps (set value to "", patch command) are really a single step. The value is set to "" by the patch command so they need to be combined.
        Suggestion:
        If the PODVM_AMI_ID  or AZURE_IMAGE_ID  parameter is not empty, clear the parameter by running the following command:

      $ oc patch configmap peer-pods-cm -n openshift-sandboxed-containers-operator -p '{"data":{"<image_id>":""}}'

              rhn-support-jowilkin John Wilkins
              apinnick@redhat.com Avital Pinnick
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: