v1.9.1 release candidate is available

[Michael Creel]

There is a release candidate available. Some testing would be appreciated, if you can. I'll release in a week or so, unless I receive reports of problems.

64 bit (recommended)
http://pareto.uab.es/mcreel/PelicanHPC/download/pelicanhpc-v1.9.1_64bit_rc1.iso

32 bit
http://pareto.uab.es/mcreel/PelicanHPC/download/pelicanhpc-v1.9.1_32bit_rc1.iso

[eropp]

i've countered an interesting'n'suprising trouble...
Trying resize already existing static-ip-configured
cluster with home-shared-unpassworded-ssh i've seen
that if this shared home being mounted at pelican-booted-node,
i've got well shared home, no problems with ownership and
permissions but PASSWORDED ssh connection from server.
/var/log/auth.log shows that the pelican-booted-node treats
server's ssh key as BLACKLISTED. i'm still shocked. why?????
being unable to solve this problem in other way i expect
make_pelican should contain string
-----echo "PermitBlacklistedKeys yes" >> /etc/ssh/ssh_config---
after line 267 (----echo "StrictHostKeyChecking no" >> /etc/ssh/ssh_config----)

trying to aid, eropp

[Michael Creel]

To make sure I understand correctly, you have a normal PelicanHPC cluster, you add a node, and then you run pelican_restarthpc, and the frontend node is blacklisted on the new compute node. Is that correct? I don't know anything about blacklisted ssh keys, and I've never seen this problem before, so I'm not sure what's going on.

fail2ban is installed, but it blacklists IP addresses, I believe.

I don't have any idea what's up, at the moment, but I'll try to look into it. Thanks for the heads up.

[eropp]

my main cluster is not based on pelican. i use pelican to resize'em (add tmp nodes). pelican-booted-nodes tell me smthng about blacklisted ssh key if i use ssh connection from main (not pelican) server.
eropp

[Michael Creel]

Given that you're using the scripts in a way they're not designed for, the results are a little unpredictable. The whole set of script is intended to be used only on a PelicanHPC cluster, so I don't consider this to be a bug. If you find out the cause, I would be interested to know. Thanks, M.