Uploaded image for project: 'Indy Node'
  1. Indy Node
  2. INDY-1905

Unable to use numeric namespace name using pool automation scripts

    XMLWordPrintable

Details

    • Bug
    • Status: New
    • Low
    • Resolution: Unresolved
    • None
    • None
    • None
    • None

    Description

      Steps to Reproduce:
      1. Run `python ./scripts/namespace-config.py conf --localhosts.aws_regions us-east-1 us-west-2 --aws_clients_provisioner.aws_instance_count 1 --aws_clients_provisioner.aws_ec2_type t3.micro --aws_clients_provisioner.aws_ebs_volume_size 8 --aws_nodes_provisioner.aws_instance_count 4 --aws_nodes_provisioner.aws_ec2_type m5.large --aws_nodes_provisioner.aws_ebs_volume_size 24 --nodes.indy_node_channel master --clients.perf_scripts_libindy_ver 1.6.8~884 --clients.indy_cli_ver 1.6.8~884 --nodes.indy_node_ver 1.6.725 --nodes.indy_plenum_ver 1.6.628 --nodes.python_indy_crypto_ver 0.4.5 --nodes.libindy_crypto_ver 0.4.5`
      2. Run `ansible-playbook -i conf/inventory provision.yml` several times.

      Actual Results:
      There are ansible errors about node ssh key during first run, about client ssh key second time and about `Unexpected Exception, this is probably a bug: expected string or buffer` the third and all the next times.

      Expected Results:
      There should be no errors or we should forbid numeric namespaces' names.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              VladimirWork Vladimir Shishkin
              Vladimir Shishkin
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: