Launch esnode in staging

[pvisweswar]

Ticket : https://dimagi.atlassian.net/browse/SAAS-19069

Environments Affected : Staging

[gherceg]

@pvisweswar do you see the test failure?

Hey, did you edit inventory.ini when you should have edited inventory.ini.j2?
That's a common cause of this test failure.
If so, make your change to inventory.ini.j2 and run
cchq aws-fill-inventory --cached
to fix this test

I presume you just need to run aws-fill-inventory to resolve.

[pvisweswar]

@pvisweswar do you see the test failure?

Hey, did you edit inventory.ini when you should have edited inventory.ini.j2?
That's a common cause of this test failure.
If so, make your change to inventory.ini.j2 and run
cchq aws-fill-inventory --cached
to fix this test

I presume you just need to run aws-fill-inventory to resolve.

This is a common situation when launching a new server. The launch may initially fail because the required entries are not yet present in inventory.ini. However, to update inventory.ini, we first need to launch the server, since the IP addresses are generated only after the instance is created.