search cancel

DS 8.6 RU2 - Cloning existing Script OS Install task, would duplicate OS Key and OS Definition - resulting in broken dependencies and associations

book

Article ID: 237923

calendar_today

Updated On:

Products

IT Management Suite Deployment Solution

Issue/Introduction

After upgrade to ITMS 8.6 RU2 and performing a test to deploy new OS, rather than using new Job/task for Scripted OS Install, you would normally Clone existing SOI task and then modify based on your needs or changes (for example just changing the Answer file).

In 8.6 RU2 - due to the regression, it would result in duplication created for OS Definition, OS Licenses and thus corrupting the task association.

Even if when you try to Clone SOI task with a Shallow clone - Packages are also getting duplicated:

Additionally, after cloning any SOI Task, the ability to add new SOI package from DS > OS files page would not be possible, due to corruption of existing amount of Unique OS Flavors:

Resulting in error when trying to add new OS files:

 

Cause

Product defect

Environment

Deployment Solution 8.6 RU2

Resolution

This issue has been reported to our Broadcom Dev team. A fix is targeted for ITMS 8.6 RU3. 

8.6 RU2: A point fix is currently available. See KB 235538 "CUMULATIVE POST ITMS 8.6 RU2 POINT FIXES"

Attachments