Our automated tests found another problem in the new CDOT pack.
We create multiple LUNs in the same workflow using a loop and use previous LUN names to create "incrementing" LUN names. This specifically works because the first LUN would create a reservation so the second LUN sees the first LUN when the next name is created and so on.
That worked fine with the previous CDOT pack but fails with the 1.5.0 pack. My only explanation is a change I have found in the reservation, it starts as such:
INSERT
INTO
cm_storage.lun
SELECT
'${OSType}' /* os_type*/,
NULL /*id*/,
'${LunName}' /*name*/,
However, OSType is definitely not the first field in the dictionary entry for cm_storage.LUN. The correct reservation should start (as it did before) like this
INSERT
INTO
cm_storage.lun
SELECT
NULL, -- id
'${LunName}', -- name
'${OSType}', -- os_type
The workaround is obviously to clone the command and use the fixed reservation but I'd rather stick to certified commands.
@netapp: care to open up another bug for me? 😄
