Skip to content

New AMI, error provisionning #2

@Dnd-Jack

Description

@Dnd-Jack

Hi Dominic,

Your solution is great. But what happens if the AMI changes?

Following an update of the AMI it seems that it is not correctly reprovisioning the server.
It declares "aws_instance.openvpn must be replaced" then it crashes because it cannot find the script "update_users.sh"
null_resource.openvpn_update_users_script (remote-exec): User: ec2-user null_resource.openvpn_update_users_script (remote-exec): Password: false null_resource.openvpn_update_users_script (remote-exec): Private key: true null_resource.openvpn_update_users_script (remote-exec): Certificate: false null_resource.openvpn_update_users_script (remote-exec): SSH Agent: false null_resource.openvpn_update_users_script (remote-exec): Checking Host Key: false null_resource.openvpn_update_users_script (remote-exec): Connected! null_resource.openvpn_update_users_script (remote-exec): sudo: /home/ec2-user/update_users.sh: command not found Error: error executing "/tmp/terraform_51813320.sh": Process exited with status 1 Cleaning up file based variables

What solution do you suggest?

thank you!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions