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

DOC Bug for installing SNO using cloud-provider

XMLWordPrintable

    • Moderate
    • No
    • 1
    • T&PS 2023 #7
    • 1
    • False
    • Hide

      None

      Show
      None

      As per the OCP 4.13 release notes Installing an OpenShift Container Platform cluster on AWS with a single node and documentation Installing a cluster on a single node, SNO can be installed over AWS now.

      However, if we see the documentation Requirements for installing OpenShift on a single node, specifically 3rd point where following is mentioned.
      --> Supported platforms: Installing OpenShift Container Platform on a single node is supported on bare metal, vSphere, AWS, Red Hat OpenStack, and Red Hat Virtualization platforms. In all cases, you must specify the platform.none: {} parameter in the install-config.yaml configuration file.

      It seems like the "platform.none: {}" shouldn't be there as I tried the installation over AWS using that parameter and the installation failed.

      additionalTrustBundlePolicy: Proxyonly
      apiVersion: v1
      baseDomain: indiashift.support
      compute:
      - architecture: amd64
        hyperthreading: Enabled
        name: worker
        platform: {}
        replicas: 0 
      controlPlane:
        architecture: amd64
        hyperthreading: Enabled
        name: master
        platform:
          aws:
            rootVolume:
              size: 120
            type: m6a.2xlarge
        replicas: 1 
      metadata:
        creationTimestamp: null
        name: aygarg
      networking:
        clusterNetwork:
        - cidr: 10.128.0.0/14
          hostPrefix: 23
        machineNetwork:
        - cidr: 10.0.0.0/16
        networkType: OVNKubernetes
        serviceNetwork:
        - 172.30.0.0/16
      platform:
        none: {}
      bootstrapInPlace:
        installationDisk: /dev/xvda
      publish: External
      pullSecret: '{"auths": ...}'
      sshKey: |
        ssh-ed25519 AAAA...
      
      
      > ./openshift-install create cluster --dir=config  --log-level=debug
      DEBUG OpenShift Installer 4.13.0                   
      DEBUG Built from commit 44db7b2959d97ecc9b7b14785ce092640fc87941 
      DEBUG Fetching Metadata...                         
      DEBUG Loading Metadata...                          
      DEBUG   Loading Cluster ID...                      
      DEBUG     Loading Install Config...                
      DEBUG       Loading SSH Key...                     
      DEBUG       Loading Base Domain...                 
      DEBUG         Loading Platform...                  
      DEBUG       Loading Cluster Name...                
      DEBUG         Loading Base Domain...               
      DEBUG         Loading Platform...                  
      DEBUG       Loading Networking...                  
      DEBUG         Loading Platform...                  
      DEBUG       Loading Pull Secret...                 
      DEBUG       Loading Platform...                    
      ERROR failed to fetch Metadata: failed to load asset "Install Config": failed to create install config: invalid "install-config.yaml" file: controlPlane.platform.aws: Invalid value: aws.MachinePool{Zones:[]string(nil), InstanceType:"m6a.2xlarge", AMIID:"", EC2RootVolume:aws.EC2RootVolume{IOPS:0, Size:120, Type:"", KMSKeyARN:""}, EC2Metadata:aws.EC2Metadata{Authentication:""}, IAMRole:""}: cannot specify "aws" for machine pool when cluster is using "none"
      

      When I specified the platform as AWS, the SNO deployed. I have documented the steps in the following KCS.
      --> https://access.redhat.com/solutions/7018963

            rhn-support-amolnar Alexandra Molnar
            rhn-support-aygarg Ayush Garg
            Gaoyun Pei Gaoyun Pei
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: