Skip to content
This repository has been archived by the owner on Jan 25, 2023. It is now read-only.

Pull request to fix #191 #192

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

jholloway7
Copy link

This fixes the --agent-ca-cert-file flag leaving handling of the typo in place for backward compatibility.

I also noticed another typo in the documentation --dynamo--table that is fixed here as well. This one was just an echo bug, so it didn't seem necessary to try to handle the typo.

https://github.com/hashicorp/terraform-aws-vault/blob/master/modules/run-vault/run-vault#L48

I also noticed the README.md was out of date with the new flags, so did my best to update that documentation accordingly.

I don't think there are any unit tests that apply here so I didn't run anything, but I did test the script for backward compatibility in my environment and both versions of the flag worked as expected.

@hashicorp-cla
Copy link

hashicorp-cla commented Apr 2, 2020

CLA assistant check
All committers have signed the CLA.

Copy link
Collaborator

@brikis98 brikis98 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is great work, thank you 👍

I'll kick off tests shortly.

@brikis98
Copy link
Collaborator

brikis98 commented Apr 3, 2020

Hm, many of the tests failed:

TestMainVaultCluster/group/TestEnterpriseInstallationWithvaultEnterpriseOnAmazonLinuxAmi - test
TestMainVaultCluster/group/TestVaultAgentWithvaultOpenSourceOnAmazonLinuxAmi - test
TestMainVaultCluster/group/TestVaultAutoUnsealWithvaultOpenSourceOnAmazonLinuxAmi - test
TestMainVaultCluster/group/TestVaultAgentWithvaultOpenSourceOnAmazonLinuxAmi - test
Failed
TestMainVaultCluster/group/TestVaultAutoUnsealWithvaultOpenSourceOnAmazonLinuxAmi - test
Failed
TestMainVaultCluster/group/TestVaultEC2AuthWithvaultOpenSourceOnAmazonLinuxAmi - test
Failed
TestMainVaultCluster/group/TestVaultIAMAuthWithvaultOpenSourceOnAmazonLinuxAmi - test
Failed
TestMainVaultCluster/group/TestVaultIAMAuthWithvaultOpenSourceOnUbuntu18Ami - test
Failed
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi - test
Failed
TestMainVaultCluster/group/TestVaultPublicClusterWithvaultOpenSourceOnAmazonLinuxAmi - test
TestMainVaultCluster/group/TestVaultPublicClusterWithvaultOpenSourceOnAmazonLinuxAmi TestMainVaultCluster/group/TestVaultWithS3BackendWithvaultOpenSourceOnAmazonLinuxAmi - test

From what I can see, it's able to build the AMI and run apply without issues, but the sever isn't starting correctly:

TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:43:48Z command.go:158: Apply complete! Resources: 41 added, 0 changed, 0 destroyed.�[0m
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:43:48Z command.go:158: �[0m�[1m�[32m
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:43:48Z command.go:158: Outputs:
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:43:48Z command.go:158: 
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:43:48Z command.go:158: asg_name_consul_cluster = consul-test-UnYVK120200403084300158200000009
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:43:48Z command.go:158: asg_name_vault_cluster = vault-test-evQzch2020040308430067440000000a
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:43:48Z command.go:158: aws_region = us-east-1
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:43:48Z command.go:158: consul_cluster_cluster_tag_key = consul-test-UnYVK1
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:43:48Z command.go:158: consul_cluster_cluster_tag_value = consul-test-UnYVK1
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:43:48Z command.go:158: iam_role_arn_consul_cluster = arn:aws:iam::087285199408:role/consul-test-UnYVK120200403084249142900000004
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:43:48Z command.go:158: iam_role_arn_servers = arn:aws:iam::087285199408:role/consul-test-UnYVK120200403084249142900000004
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:43:48Z command.go:158: iam_role_arn_vault_cluster = arn:aws:iam::087285199408:role/vault-test-evQzch20200403084249135500000001
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:43:48Z command.go:158: iam_role_id_consul_cluster = consul-test-UnYVK120200403084249142900000004
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:43:48Z command.go:158: iam_role_id_servers = consul-test-UnYVK120200403084249142900000004
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:43:48Z command.go:158: iam_role_id_vault_cluster = vault-test-evQzch20200403084249135500000001
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:43:48Z command.go:158: launch_config_name_consul_cluster = consul-test-UnYVK1-20200403084251298100000008
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:43:48Z command.go:158: launch_config_name_servers = consul-test-UnYVK1-20200403084251298100000008
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:43:48Z command.go:158: launch_config_name_vault_cluster = vault-test-evQzch-20200403084251289000000007
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:43:48Z command.go:158: security_group_id_consul_cluster = sg-0aaaeff9c100a7940
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:43:48Z command.go:158: security_group_id_servers = sg-0aaaeff9c100a7940
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:43:48Z command.go:158: security_group_id_vault_cluster = sg-0b45b8854d4bc2da7
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:43:48Z command.go:158: ssh_key_name = evQzch
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:43:48Z command.go:158: vault_cluster_size = 3
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:43:48Z command.go:158: vault_servers_cluster_tag_key = Name
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:43:48Z command.go:158: vault_servers_cluster_tag_value = vault-test-evQzch�[0m
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:43:48Z test_structure.go:23: The 'SKIP_validate' environment variable is not set, so executing stage 'validate'.
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:43:48Z save_test_data.go:195: Loading test data from /tmp/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi460019382/terraform-aws-vault/examples/vault-cluster-private/.test-data/TerraformOptions.json
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:43:48Z save_test_data.go:195: Loading test data from /tmp/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi460019382/terraform-aws-vault/examples/vault-cluster-private/.test-data/Ec2KeyPair.json
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:43:48Z retry.go:72: terraform [output -no-color asg_name_vault_cluster]
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:43:48Z command.go:87: Running command terraform with args [output -no-color asg_name_vault_cluster]
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:43:48Z command.go:158: vault-test-evQzch2020040308430067440000000a
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:43:49Z vault_helpers.go:225: Trying to establish SSH connection to 34.230.12.243
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:43:49Z retry.go:72: Trying to establish SSH connection to 34.230.12.243
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:43:49Z ssh.go:414: Running command 'exit' on ec2-user@34.230.12.243
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:43:59Z retry.go:84: Trying to establish SSH connection to 34.230.12.243 returned an error: dial tcp 34.230.12.243:22: i/o timeout. Sleeping for 10s and will try again.
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:44:09Z retry.go:72: Trying to establish SSH connection to 34.230.12.243
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:44:09Z ssh.go:414: Running command 'exit' on ec2-user@34.230.12.243
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:44:10Z retry.go:84: Trying to establish SSH connection to 34.230.12.243 returned an error: dial tcp 34.230.12.243:22: connect: connection refused. Sleeping for 10s and will try again.
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:44:20Z retry.go:72: Trying to establish SSH connection to 34.230.12.243
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:44:20Z ssh.go:414: Running command 'exit' on ec2-user@34.230.12.243
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:44:21Z vault_helpers.go:225: Trying to establish SSH connection to 3.227.0.125
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:44:21Z retry.go:72: Trying to establish SSH connection to 3.227.0.125
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:44:21Z ssh.go:414: Running command 'exit' on ec2-user@3.227.0.125
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:44:21Z retry.go:84: Trying to establish SSH connection to 3.227.0.125 returned an error: dial tcp 3.227.0.125:22: connect: connection refused. Sleeping for 10s and will try again.
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:44:31Z retry.go:72: Trying to establish SSH connection to 3.227.0.125
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:44:31Z ssh.go:414: Running command 'exit' on ec2-user@3.227.0.125
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:44:33Z vault_helpers.go:225: Trying to establish SSH connection to 3.82.207.95
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:44:33Z retry.go:72: Trying to establish SSH connection to 3.82.207.95
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:44:33Z ssh.go:414: Running command 'exit' on ec2-user@3.82.207.95
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:44:34Z vault_helpers.go:242: Waiting for Vault to boot the first time on host 34.230.12.243. Expecting it to be in uninitialized status (501).
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:44:34Z vault_helpers.go:403: Check that the Vault node 34.230.12.243 has status 501
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:44:34Z retry.go:72: Check that the Vault node 34.230.12.243 has status 501
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:44:34Z vault_helpers.go:426: Using curl to check status of Vault server 34.230.12.243: curl -s -o /dev/null -w '%{http_code}' https://127.0.0.1:8200/v1/sys/health
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:44:34Z ssh.go:414: Running command curl -s -o /dev/null -w '%{http_code}' https://127.0.0.1:8200/v1/sys/health on ec2-user@34.230.12.243
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:44:35Z retry.go:84: Check that the Vault node 34.230.12.243 has status 501 returned an error: Process exited with status 7. Sleeping for 10s and will try again.
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:44:45Z retry.go:72: Check that the Vault node 34.230.12.243 has status 501
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:44:45Z vault_helpers.go:426: Using curl to check status of Vault server 34.230.12.243: curl -s -o /dev/null -w '%{http_code}' https://127.0.0.1:8200/v1/sys/health
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:44:45Z ssh.go:414: Running command curl -s -o /dev/null -w '%{http_code}' https://127.0.0.1:8200/v1/sys/health on ec2-user@34.230.12.243
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:44:45Z retry.go:84: Check that the Vault node 34.230.12.243 has status 501 returned an error: Process exited with status 7. Sleeping for 10s and will try again.
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:44:55Z retry.go:72: Check that the Vault node 34.230.12.243 has status 501
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:44:55Z vault_helpers.go:426: Using curl to check status of Vault server 34.230.12.243: curl -s -o /dev/null -w '%{http_code}' https://127.0.0.1:8200/v1/sys/health
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:44:55Z ssh.go:414: Running command curl -s -o /dev/null -w '%{http_code}' https://127.0.0.1:8200/v1/sys/health on ec2-user@34.230.12.243
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:44:55Z retry.go:84: Check that the Vault node 34.230.12.243 has status 501 returned an error: Process exited with status 7. Sleeping for 10s and will try again.
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:45:05Z retry.go:72: Check that the Vault node 34.230.12.243 has status 501
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:45:05Z vault_helpers.go:426: Using curl to check status of Vault server 34.230.12.243: curl -s -o /dev/null -w '%{http_code}' https://127.0.0.1:8200/v1/sys/health
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:45:05Z ssh.go:414: Running command curl -s -o /dev/null -w '%{http_code}' https://127.0.0.1:8200/v1/sys/health on ec2-user@34.230.12.243
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:45:06Z retry.go:84: Check that the Vault node 34.230.12.243 has status 501 returned an error: Process exited with status 7. Sleeping for 10s and will try again.
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:45:16Z retry.go:72: Check that the Vault node 34.230.12.243 has status 501
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:45:16Z vault_helpers.go:426: Using curl to check status of Vault server 34.230.12.243: curl -s -o /dev/null -w '%{http_code}' https://127.0.0.1:8200/v1/sys/health
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:45:16Z ssh.go:414: Running command curl -s -o /dev/null -w '%{http_code}' https://127.0.0.1:8200/v1/sys/health on ec2-user@34.230.12.243
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:45:16Z retry.go:84: Check that the Vault node 34.230.12.243 has status 501 returned an error: Process exited with status 7. Sleeping for 10s and will try again.
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:45:26Z retry.go:72: Check that the Vault node 34.230.12.243 has status 501
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:45:26Z vault_helpers.go:426: Using curl to check status of Vault server 34.230.12.243: curl -s -o /dev/null -w '%{http_code}' https://127.0.0.1:8200/v1/sys/health
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:45:26Z ssh.go:414: Running command curl -s -o /dev/null -w '%{http_code}' https://127.0.0.1:8200/v1/sys/health on ec2-user@34.230.12.243
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:45:26Z retry.go:84: Check that the Vault node 34.230.12.243 has status 501 returned an error: Process exited with status 7. Sleeping for 10s and will try again.
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:45:36Z retry.go:72: Check that the Vault node 34.230.12.243 has status 501
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:45:36Z vault_helpers.go:426: Using curl to check status of Vault server 34.230.12.243: curl -s -o /dev/null -w '%{http_code}' https://127.0.0.1:8200/v1/sys/health
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:45:36Z ssh.go:414: Running command curl -s -o /dev/null -w '%{http_code}' https://127.0.0.1:8200/v1/sys/health on ec2-user@34.230.12.243
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:45:37Z retry.go:84: Check that the Vault node 34.230.12.243 has status 501 returned an error: Process exited with status 7. Sleeping for 10s and will try again.
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:45:47Z retry.go:72: Check that the Vault node 34.230.12.243 has status 501
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:45:47Z vault_helpers.go:426: Using curl to check status of Vault server 34.230.12.243: curl -s -o /dev/null -w '%{http_code}' https://127.0.0.1:8200/v1/sys/health
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:45:47Z ssh.go:414: Running command curl -s -o /dev/null -w '%{http_code}' https://127.0.0.1:8200/v1/sys/health on ec2-user@34.230.12.243
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:45:47Z retry.go:84: Check that the Vault node 34.230.12.243 has status 501 returned an error: Process exited with status 7. Sleeping for 10s and will try again.
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:45:57Z retry.go:72: Check that the Vault node 34.230.12.243 has status 501
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:45:57Z vault_helpers.go:426: Using curl to check status of Vault server 34.230.12.243: curl -s -o /dev/null -w '%{http_code}' https://127.0.0.1:8200/v1/sys/health
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:45:57Z ssh.go:414: Running command curl -s -o /dev/null -w '%{http_code}' https://127.0.0.1:8200/v1/sys/health on ec2-user@34.230.12.243
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 2020-04-03T08:45:57Z retry.go:84: Check that the Vault node 34.230.12.243 has status 501 returned an error: Process exited with status 7. Sleeping for 10s and will try again.
TestMainVaultCluster/group/TestVaultPrivateClusterWithvaultOpenSourceOnAmazonLinuxAmi 

It basically is looking for a 501 over and over again and never getting it. Could you run one of these examples and see what the issue is?

@jholloway7
Copy link
Author

These tests are pretty slick. I think I've got things set up to run them locally now. I'll give it a shot and report my findings.

@jholloway7
Copy link
Author

jholloway7 commented Apr 3, 2020

@brikis98 I was able to recreate these errors with my branch, but not being able to connect any dots, I tried to run the entire suite against the master branch I forked -- i.e. without my commits -- and got the same errors. I think some of them are failing because I don't have autoseal keys setup, but I'm definitely seeing the 501 error in there as well.

Another interesting thing is if I pick one of the failing tests (that don't use autoseal) and target it individually with -run it will pass. I've run it three times to see if I could get a fail, but it seems to pass that way.

I don't know if that means there's a race condition in the failing tests or something to do with running all the tests in parallel?

Is there a way you can trigger the circleci tests against master and see if I'm looking at things correctly that the issue is upstream from my branch?

@brikis98
Copy link
Collaborator

brikis98 commented Apr 6, 2020

Thanks for taking a look! I'll try to dig in this week to see if things are working on master.

@brikis98
Copy link
Collaborator

There are indeed some issues on master. WIP is here: #195.

Copy link
Collaborator

@brikis98 brikis98 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, thank you for your patience! We merged fixes in #195. Could you rebase?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants