installation of a fan-in cluster fails when fan-in slave is not last in the host list

[GoogleCodeExporter]

What steps will reproduce the problem?

1. prepare installation on a 6-node cluster
2. let the fan-in slave be node #4 
3. Install a fan-in topology

What is the expected output?

Installation succeeds

What do you see instead?

Installation fails. The replicator complains about the same service being used 
twice

What is the possible cause?

In the fan-in installation template, the fan-in slave is the last node. This 
way, there is no issue with services being used twice. When the fan-in slave is 
in the middle of a masters list, the installer tried using the fan-in slave 
service to install twice

What is the proposed solution?

Check if the fan-in service is being used, and skip one position in the service 
list

Original issue reported on code.google.com by g.maxia on 28 Jul 2013 at 6:36

[GoogleCodeExporter]

Notice that the issue affects only installations with tungsten-installer + 
configure-service, as the logic is driven by a shell script, where the actual 
issue are. Installation with tpm works as expected

Original comment by g.maxia on 28 Jul 2013 at 6:38

[GoogleCodeExporter]

Original comment by g.maxia on 28 Jul 2013 at 6:56

• Added labels: Publish-Release-Note

[GoogleCodeExporter]

Fixed. Added an extra check for service name during the loop.

Original comment by g.maxia on 28 Jul 2013 at 7:36

[GoogleCodeExporter]

Original comment by g.maxia on 28 Jul 2013 at 7:36

• Changed state: Fixed