Ok, I mucked around with this for a bit.
I think there two issues here:
1. VIM25Stub.pm defines KeyAnyValue->value as a single value. As a very unsupported workaround, the KeyAnyValue definition in VIM25Stub.pm was changed to:
##################################################################################
package KeyAnyValue;
our @ISA = qw(DynamicData);
our @property_list = (
['key', undef, undef, 1],
['value', 'anyType', 1, 1],
);
VIMRuntime::make_get_set('KeyAnyValue', 'key', 'value');
sub get_property_list {
my $class = shift;
my @super_list = $class->SUPER::get_property_list();
return (@super_list, @property_list);
}
1;
##################################################################################
Particularly the change is in the ['value', 'anyType', undef, 1] to ['value', 'anyType', 1, 1]. That change turns the value property into an array. Without this change, the SOAP module will toss out parser errors.
2. The SDK HostProfile interface seems sensitive to the xsi:type declaration. The ComplexType::serialize code in VICommon.pm basically falls back to 'xsi:string' for any non-specific values. Without the fix below, I was getting %d format expected number not string errors. In this case, I don't believe it was related to the KeyAnyValue issue, but just a more strict type check than normally expected from the Perl SDK.
if ($class_name ne $obj_type_name) {
$show_type = 1;
if ($class_name eq 'anyType' && ! $obj_type_name) {
# primitive going out as any -- treat them as xsd:string
if (defined ($_) && isdigit($_)) {
$serialized_string .=
"<$property_name xsi:type=\"xsd:int\">" .
XmlUtil::escape_xml_string($_) . "</$property_name>";
} elsif (defined ($_)) {
$serialized_string .=
"<$property_name xsi:type=\"xsd:string\">" .
XmlUtil::escape_xml_string($_) . "</$property_name>";
}
next;
}
}
I used a simple Login Banner + Advanced Configuration Option enabled HostProfile with these changes successfully.
I've attached the script I used with the simple profile setting. To run it, you'll need to CPAN install 'Sub::Override'. It's a source module IIRC, so you can copy and paste it into a module file in your path if CPAN isn't an option.
> profiletest.pl --username=administrator --password=****** --server=172.16.254.50 --host=vlab5-esx-03.vlab5.local --profile=VLAB5-P2
I don't check the task status in the script, I did validations visually in the vCenter Client UI.
I'm not sure it will be of much use, particularly with the modification to the VIM25Stub.pm file. Since it's going to require some more robust determination of the xsi:type in the serialization functions in the toolkit, it will need some testing before being production worthy.
Also, just to feed some information. I did manage to get one of my hosts in a state where I get general errors anytime I try to apply a HostProfile (even a simple one). I can't seem to recover it, and it was the result of a applying a very complex HostProfile with some input answers. It's possible this xsi:type issue caused the problem, but I feel the HostProfile system shouldn't be that easily laid out. It may be a related bug.
Reuben Stump | http://www.virtuin.com | @ReubenStump
