ECS CE 3.5: step1 command fails at "Distribute rsa ssh key" task

Adding further information about this use case, ECS CE 3.5 deployment is easier: Single-Node installation on the same local VM (IP address is 172.16.0.12 as well as it is indicated in logs).

Looking forward to your kind reply

SG

Hello SG81,

Which ECS system do you have?

Including additional data about this utilization case, ECS CE 3.5 sending is simpler: Single-Node establishment on a similar neighborhood VM

The VM dedicated for ECS CE is unique, the same where we perform the installation and it can access to Internet. We desire to have the easier installation: are single-node or all-in-one installation the same? How do we choose this option when we run step1 command?  

ECS CE 3.5 is used as testing environment only, deployed in single-node installation mode on a unique VM where we launch step1 command. Our aim is to upgrade to 3.5 version in production (current version is 3.2.x.x., two VDC with 8 nodes each one) but we have to run no regression tests on Community Edition in order to verify API compatibility for developed software.  

The environment for ECS CE 3.5 is the following:

- CentOS 7.8 with 4CPU, 16GB di RAM, 50GB (for s.o.)+200GB (unpartitioned unit, sdb) 

- Internet connection

- admin user with sudoer permissions to run all commands 

- We desire to have the easier installation, single-node or all-in-one installation.

- The path /opt/ssh/ where we encounter the error is missing. Should we create it?

Below, it is indicated the content of deploy.yml  

Thank you for support

SG

# deploy.yml reference implementation v2.8.0

# [Optional]
# By changing the license_accepted boolean value to "true" you are
# declaring your agreement to the terms of the license agreement
# contained in the license.txt file included with this software
# distribution.
licensing:
  license_accepted: true

#autonames:
#  custom:
#    - ecs01
#    - ecs02
#    - ecs03
#    - ecs04
#    - ecs05
#    - ecs06

# [Required]
# Deployment facts reference
facts:

  # [Required]
  # Node IP or resolvable hostname from which installations will be launched
  # The only supported configuration is to install from the same node as the
  # bootstrap.sh script is run.
  # NOTE: if the install node is to be migrated into an island environment,
  #       the hostname or IP address listed here should be the one in the
  #       island environment.
  install_node: 172.16.0.12

  # [Required]
  # IPs of machines that will be whitelisted in the firewall and allowed
  # to access management ports of all nodes. If this is set to the
  # wildcard (0.0.0.0/0) then anyone can access management ports.
  management_clients:
    - 0.0.0.0/0

  # [Required]
  # These credentials must be the same across all nodes. Ansible uses these credentials to
  # gain initial access to each node in the deployment and set up ssh public key authentication.
  # If these are not correct, the deployment will fail.
  ssh_defaults:
    # [Required]
    # Username to use when logging in to nodes
    ssh_username: admin
    # [Required]
    # Password to use with SSH login
    # *** Set to same value as ssh_username to enable SSH public key authentication ***
    ssh_password: ChangeMe
    # [Required when enabling SSH public key authentication]
    # Password to give to sudo when gaining root access.
    ansible_become_pass: ChangeMe
    # [Required]
    # Select the type of crypto to use when dealing with ssh public key
    # authentication. Valid values here are:
    #  - "rsa" (Default)
    #  - "ed25519"
    ssh_crypto: rsa

  # [Required]
  # Environment configuration for this deployment.
  node_defaults:
    dns_domain: local
    dns_servers:
      - 151.99.125.1 
    ntp_servers:
      - 85.199.214.99
    #
    # [Optional]
    # VFS path to source of randomness
    # Defaults to /dev/urandom for speed considerations.  If you prefer /dev/random, put that here.
    # If you have a /dev/srandom implementation or special entropy hardware, you may use that too
    # so long as it implements a /dev/random type device.
    entropy_source: /dev/urandom
    #
    # [Optional]
    # Picklist for node names.
    # Available options:
    #  - "moons" (ECS CE default)
    #  - "cities" (ECS SKU-flavored)
    #  - "custom" (uncomment and use the top-level autonames block to define these)
    # autonaming: custom

    #
    # [Optional]
    # If your ECS comes with differing default credentials, you can specify those here
    # ecs_root_user: root
    # ecs_root_pass: ChangeMe

  # [Optional]
  # Storage pool defaults. Configure to your liking.
  # All block devices that will be consumed by ECS on ALL nodes must be listed under the
  # ecs_block_devices option. This can be overridden by the storage pool configuration.
  # At least ONE (1) block device is REQUIRED for a successful install. More is better.
  storage_pool_defaults:
    is_cold_storage_enabled: false
    is_protected: false
    description: Default storage pool description
    ecs_block_devices:
      - /dev/sdb

  # [Required]
  # Storage pool layout. You MUST have at least ONE (1) storage pool for a successful install.
  storage_pools:
    - name: sp1
      members:
        - 172.16.0.12
      options:
        is_protected: false
        is_cold_storage_enabled: false
        description: My First SP
        ecs_block_devices:
          - /dev/sdb

  # [Optional]
  # VDC defaults. Configure to your liking.
  virtual_data_center_defaults:
    description: Default virtual data center description

  # [Required]
  # Virtual data center layout. You MUST have at least ONE (1) VDC for a successful install.
  # Multi-VDC deployments are not yet implemented
  virtual_data_centers:
    - name: vdc1
      members:
        - sp1
      options:
        description: My First VDC

  # [Optional]
  # Replication group defaults. Configure to your liking.
  replication_group_defaults:
    description: Default replication group description
    enable_rebalancing: true
    allow_all_namespaces: true
    is_full_rep: false

  # [Optional, required for namespaces]
  # Replication group layout. You MUST have at least ONE (1) RG to provision namespaces.
  replication_groups:
    - name: rg1
      members:
        - vdc1
      options:
        description: My First RG
        enable_rebalancing: true
        allow_all_namespaces: true
        is_full_rep: false

  # [Optional]
  # Management User defaults
  management_user_defaults:
    is_system_admin: false
    is_system_monitor: false

  # [Optional]
  # Management Users
  management_users:
    - username: admin1
      password: ChangeMe
      options:
        is_system_admin: true
    - username: monitor1
      password: ChangeMe
      options:
        is_system_monitor: true

  # [Optional]
  # Namespace defaults
  namespace_defaults:
    is_stale_allowed: false
    is_compliance_enabled: false

  # [Optional]
  # Namespace layout
  namespaces:
    - name: ns1
      replication_group: rg1
      administrators:
        - root
      options:
        is_stale_allowed: false
        is_compliance_enabled: false

  # [Optional]
  # Object User defaults
  object_user_defaults:
    # Comma-separated list of Swift authorization groups
    swift_groups_list:
      - users
    # Lifetime of S3 secret key in minutes
    s3_expiry_time: 2592000

  # [Optional]
  # Object Users
  object_users:
    - username: object_admin1
      namespace: ns1
      options:
        swift_password: ChangeMe
        swift_groups_list:
          - admin
          - users
        s3_secret_key: ChangeMeChangeMeChangeMeChangeMeChangeMe
        s3_expiry_time: 2592000
    - username: object_user1
      namespace: ns1
      options:
        swift_password: ChangeMe
        s3_secret_key: ChangeMeChangeMeChangeMeChangeMeChangeMe

  # [Optional]
  # Bucket defaults
  bucket_defaults:
    namespace: ns1
    replication_group: rg1
    head_type: s3
    filesystem_enabled: False
    stale_allowed: False
    encryption_enabled: False
    owner: object_admin1

  # [Optional]
  # Bucket layout (optional)
  buckets:
    - name: bucket1
      options:
        namespace: ns1
        replication_group: rg1
        owner: object_admin1
        head_type: s3
        filesystem_enabled: False
        stale_allowed: False
        encryption_enabled: False

I fixed it. Before I runned bootstrap.sh in this way:  ./bootstrap.sh –g -c deploy.yml and that error occurred.

Instead, the bootstrap command to use is:

./bootstrap.sh –vm-tools -c deploy.yml

so, after that, step1 has been completed with success.

SG