What do you learn when everything works perfectly during a system build? That you followed directions? That the installation test team did their homework? That you wore your lucky suspenders?
Is it possible to be too smart in an automated provisioned world? Here anything is possible.
When a system admin gets a set of installation media, the first thing they do is check boxes for a lot of the optional stuff, thinking it will save time down the line. They also go through basic configuration steps they have memorized from years of installs to "get things working right." It could be anything from setting a time offset, the default prompt, reverse name resolution, secure communications, or expanding the default logical volumes.
The question is, what is the cloud software going to do? How will it react when something it wants to install and configure is already done? Will it search a name resolution lookup table for an existing IP address, or will the script just add another? No telling. If the code was ported from one OS to another, something simple like email defaults can become an issue.
The answer is, therefore, the code is not broken but the system administrator was too smart.
I recommend that you leave things in the default status until you know exactly how things work, then go from there. Otherwise, make sure you have plenty of free time to figure out what went wrong.