SubnetCheckupCall stuck on create_in_progress

Everpure Cloud Dedicated for AWS
Audience
Public
Technology Integrations
Amazon Web Services (AWS)
Source Type
Documentation

  1. If subnetcheckupCall hangs, this is an indication the array cannot reach Pure1. This lambda function performs a telnet over port 443 to Pure1. 
    
    PhoneHomeAddresses:
      Value:
        - 'rest.cloud-support.purestorage.com'
        - 'ra.cloud-support.purestorage.com'
    PhonehomeCidrIp:
      Value: '52.40.255.224/27'
  2. Check the Events for any details like the following in CloudWatch:

SubnetCheckupCall

2019/07/23/[$LATEST]baa52aafce9147a3a1ae837b9b4d221a

Confirm there is a valid route to the internet from deployment (system subnet).

CloudWatch logs

AZ selection explanation

The system subnet parameter on CF stack deployment, determines the Availability Zone (AZ) where the Everpure Cloud Dedicated stack is created. Everpure Cloud Dedicated internal resources including virtual drives and controllers are deployed into the system subnet.

When the system subnet was created as a prerequisite to Everpure Cloud Dedicated stack creation, it was linked to a single AZ in the deployment region.

The VPCInfo lambda function shown below, which is part of the Everpure Cloud Dedicated CF template, provides the AZ and VPC ID when querying a lambda endpoint for response data with the system subnet ID. This AZ information is then used elsewhere in the template when allocating additional resources.

Everpure Cloud Dedicated cloud formation deployment errors and steps to identify and fix.