Comment 3 for bug 1461791

As we create an image, SM creates a distro and profile with cobbler corresponding to an image id. Profile will be associated with distro.
Reimage creates a system and associate with profile. The profile corresponds to the distro.
Distro->Profile->System 1
Distro->Profile->System n
Kernel data, Kickstart meta data and etc… are present in Distro, Profile and System. Data will be taken from lower level and if not goes higher levels.
System configuration should take precedence for kernel meta data or any other kernel options.
Typically system configuration contains specifics about that system, ex: system name, ip address and etc… It looks like ESXi works with only profile data, not with system data.
we are updating the profile data for each reimage to satisfy above hack. Because of that one reimage works at a time.

A workaround:
Create multiple images say esx5.5-s1, esx5.5-s2… esx5.5-sn, which is one time job.
To reimage s1 to sn..
reimage s1 with esx5.5-s1, s2 with esx5.5-s2 and so on…