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

[RFE] 4.11 Azure DiskEncryptionSet static validation does not support upper-case letters

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • 4.12, 4.11
    • None
    • Proposed
    • False
    • Hide

      None

      Show
      None
    • Hide
      Cause: validation prevented specifying Azure disk encryption sets with capital letters

      Consequence: encryption sets created with names with caps could not be specified

      Fix: update validation to allow capitalization

      Result: disk encryption sets with capital letters can be specified
      Show
      Cause: validation prevented specifying Azure disk encryption sets with capital letters Consequence: encryption sets created with names with caps could not be specified Fix: update validation to allow capitalization Result: disk encryption sets with capital letters can be specified
    • Bug Fix

      This is a clone of issue OCPBUGS-2895. The following is the description of the original issue:

      Description of problem:

      Current validation will not accept Resource Groups or DiskEncryptionSets which have upper-case letters.

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

      4.11

      How reproducible:

      Attempt to create a cluster/machineset using a DiskEncryptionSet with an RG or Name with upper-case letters

      Steps to Reproduce:

      1. Create cluster with DiskEncryptionSet with upper-case letters in DES name or in Resource Group name
      

      Actual results:

      See error message:
      
      encountered error: [controlPlane.platform.azure.defaultMachinePlatform.osDisk.diskEncryptionSet.resourceGroup: Invalid value: \"v4-e2e-V62447568-eastus\": invalid resource group format, compute[0].platform.azure.defaultMachinePlatform.osDisk.diskEncryptionSet.resourceGroup: Invalid value: \"v4-e2e-V62447568-eastus\": invalid resource group format]

      Expected results:

      Create a cluster/machineset using the existing and valid DiskEncryptionSet

      Additional info:

      I have submitted a PR for this already, but it needs to be reviewed and backported to 4.11: https://github.com/openshift/installer/pull/6513

            Unassigned Unassigned
            openshift-crt-jira-prow OpenShift Prow Bot
            May Xu May Xu
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: