Galaxy ansible installation is not compliant with Amazon instances whose IP address may change about galaxykickstart HOT 11 CLOSED

Well, in principle I agree, and I don't know where in the playbook @fabiorjvieira is using the IP address.
Normally the only place should be in the instructions for the FTP server, and perhaps, in nginx.
Maybe the slurm setup script ( which the galaxy guys developed ) is hardcoding IP addresses.
But, if we think ahead, the slurm clients should one day need to contact the slurm daemon through ipv4 address. Yet, this should probably happen through VPN tunnels which would allow fixing a private subnet ip.
Point is, 127.0.0.1 should be the way to go.
But before doing further coding! it should be mandatory to have a regular feature -> PR -> review process. So perhaps @fabiorjvieira can create a 0.4 milestone for this issue.

from galaxykickstart.

Nothing on my ansible scripts, except the ftp message and uwsgi can be different from localhost.
Now uwsgi is pointing constantly to localhost.
Searching in galaxy-extras (where slurm ansible scripts are) to if there is a ref to the public ip or name.

from galaxykickstart.

This issue is now linked to the dev branch https://github.com/ARTbio/ansible-artimed/tree/dev.public_ip

from galaxykickstart.

@fabiorjvieira for your information: the issue is just by adding 127.0.0.1 ip-172-30-0-107 in the /etc/hosts file of the VM

127.0.0.1 localhost
127.0.0.1 ip-172-30-0-107

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

from galaxykickstart.

Is the issue was provoked by or it was solved by the addition of 127...?
Also, my bank card was canceled and amazon wants me to update my "Modes de paiement" before start using it again, so I cannot use amazon any more.

from galaxykickstart.

Sorry, the issue was fixed by adding 127.0.0.1 ip-172-30-0-107 in the /etc/hosts file of the VM

from galaxykickstart.

Please keep the track of each issue. I see no reason to mention your Amazon account issue here

from galaxykickstart.

Is this still current @drosofff @fabiorjvieira ?
If not, please close the issue.

from galaxykickstart.

I think this is still the same issue as in #52 that we just saw. Amazon specific I suppose

from galaxykickstart.

@drosofff so we figured this out yesterday right? Close when okay :)

from galaxykickstart.

I'm going ahead and close this, re-open if there is a re-curring problem

from galaxykickstart.