• Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • False
    • None
    • False
    • OCPSTRAT-767 - Add support to NAT Gateway as outboundType for clusters in Azure (GA)
    • CLOUD Sprint 239, CLOUD Sprint 240, CLOUD Sprint 241, CLOUD Sprint 242, CLOUD Sprint 243, CLOUD Sprint 244, CLOUD Sprint 245

      Below are few scenarios done - one subnet added to cpms cluster yaml , no effect on cluster , no new machines provisioning happened.

      spec:
        replicas: 3
        selector:
          matchLabels:
            machine.openshift.io/cluster-api-cluster: miyadav-0111v1-78n2d
            machine.openshift.io/cluster-api-machine-role: master
            machine.openshift.io/cluster-api-machine-type: master
        state: Active
        strategy:
          type: RollingUpdate
        template:
          machineType: machines_v1beta1_machine_openshift_io
          machines_v1beta1_machine_openshift_io:
            failureDomains:
              azure:
              - subnet: miyadav-0111v1-78n2d-master-subnet
                zone: "1"
              - zone: "2"
              - zone: "3"
              platform: Azure 

       The subnet used above was same as available at installation 
      Added invalid subnet and reconcilation started but machine provisioning failed with below error , on co status 

      control-plane-machine-set                  4.15.0-0.nightly-2023-10-31-054858   True        False         True       105m    Observed 1 replacement machine(s) in error state
      

      status on failed machine 

      Status:
        Conditions:
          Last Transition Time:  2023-11-01T05:17:45Z
          Message:               Drain operation currently blocked by: [{Name:EtcdQuorumOperator Owner:clusteroperator/etcd}]
          Reason:                HookPresent
          Severity:              Warning
          Status:                False
          Type:                  Drainable
          Last Transition Time:  2023-11-01T05:17:44Z
          Message:               Instance has not been created
          Reason:                InstanceNotCreated
          Severity:              Warning
          Status:                False
          Type:                  InstanceExists
          Last Transition Time:  2023-11-01T05:17:44Z
          Status:                True
          Type:                  Terminable
        Error Message:           failed to reconcile machine "miyadav-0111v1-78n2d-master-vmdvb-1": network.SubnetsClient#Get: Failure responding to request: StatusCode=404 -- Original Error: autorest/azure: Service returned an error. Status=404 Code="NotFound" Message="Resource /subscriptions/53b8f551-f0fc-4bea-8cba-6d1fefd54c8a/resourceGroups/miyadav-0111v1-78n2d-rg/providers/Microsoft.Network/virtualNetworks/miyadav-0111v1-78n2d-vnet/subnets/miyadav-0111v1-78n2d-master-subnet1 not found." Details=[]
        Error Reason:            InvalidConfiguration
        Last Updated:            2023-11-01T05:17:45Z
        Phase:                   Failed
        Provider Status:
          Conditions:
            Last Transition Time:  2023-11-01T05:17:45Z
            Message:               failed to create nic miyadav-0111v1-78n2d-master-vmdvb-1-nic for machine miyadav-0111v1-78n2d-master-vmdvb-1: unable to create VM network interface: subnet miyadav-0111v1-78n2d-master-subnet1 not found: network.SubnetsClient#Get: Failure responding to request: StatusCode=404 -- Original Error: autorest/azure: Service returned an error. Status=404 Code="NotFound" Message="Resource /subscriptions/53b8f551-f0fc-4bea-8cba-6d1fefd54c8a/resourceGroups/miyadav-0111v1-78n2d-rg/providers/Microsoft.Network/virtualNetworks/miyadav-0111v1-78n2d-vnet/subnets/miyadav-0111v1-78n2d-master-subnet1 not found." Details=[]
            Reason:                MachineCreationFailed
            Status:                False
            Type:                  MachineCreated
          Metadata:
      Events:
        Type     Reason        Age                From              Message
        ----     ------        ----               ----              -------
        Warning  FailedCreate  53s (x2 over 53s)  azure-controller  InvalidConfiguration: failed to reconcile machine "miyadav-0111v1-78n2d-master-vmdvb-1": network.SubnetsClient#Get: Failure responding to request: StatusCode=404 -- Original Error: autorest/azure: Service returned an error. Status=404 Code="NotFound" Message="Resource /subscriptions/53b8f551-f0fc-4bea-8cba-6d1fefd54c8a/resourceGroups/miyadav-0111v1-78n2d-rg/providers/Microsoft.Network/virtualNetworks/miyadav-0111v1-78n2d-vnet/subnets/miyadav-0111v1-78n2d-master-subnet1 not found." Details=[]
       

      once cpms yaml corrected , cluster back to normal all co good.

      These are the basic scenarios I tested till now , let me know if we can check any other scenario ,
      I think we can try creating a different and one more subnet on Azure portal for master , and update them in cpms ,  checked with installation we can have a scenario once https://issues.redhat.com/browse/CORS-2658 is ready to go.
      cc rmanak@redhat.com joelspeed 
      cluster version - 4.15.0-0.nightly-2023-10-31-054858

       

            rh-ee-miyadav Milind Yadav
            rh-ee-miyadav Milind Yadav
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: