UNSOLVED

_Armin_

updated

3 months ago

_

_Armin_

1 Rookie

•

17 Posts

•

65 Points

0

116

August 24th, 2026 16:32

UpdateManager firmware baseline invalid after deleting another baseline

This now happened a third time, so I think this is a bug:

Usually we have different firmware baselines via the update manager plugin configured. Some of those baselines share the same firmware images over time, probably somewhere in their change history. At some time, the old baselines don't receive updates anymore. After this happens, we usually delete those baselines and all of their versions. This seems to delete the referenced firmware images globally, even if they are used by a newer baseline. The result is, that the newer baseline is not usable anymore. OME complains that it can't find the firmware images anymore and can't upload it to the iDRACs.

There is no workaround. The only way to not run into this issue is to keep old baselines (and live with the errors that are generated in the update job log).

Did anybody see this issue? Do you have a different workaround? I'm currently recreating the baseline (if it's still possible), or creating a completely new baseline...

I saw this problem with 4.6 and 4.7 (maybe even earlier).

Dell: How can I report a bug?

(edited)

  • Dell-ArunK

    Moderator

    •

    31 Posts

    •

    93 Points

    0

    0

    Posted August 25th, 2026 02:03

    Hi _Armin_

     

    The behavior you describe is especially suspicious because:

    • Two or more baselines can reference the same firmware image.
    • Deleting an older baseline/version appears to remove the shared firmware image from the repository.
    • The newer baseline still contains a reference to that image, but the actual image is gone.
    • OME then reports that the firmware image cannot be found/uploaded to iDRAC.
    • Recreating the baseline appears to be the only practical recovery.
    • You have reproduced it multiple times on OME 4.6 and 4.7. 

    What I would recommend

    Before recreating the baseline again, collect evidence so Dell Engineering can verify the reference/deletion behavior:

    1. Capture the affected baseline details
      • Baseline name
      • Baseline version/history
      • Firmware components/images referenced
      • Devices associated with the baseline.
    2. Capture the older baseline before deletion, if possible.
      • Record the firmware image/version that is shared with the newer baseline.
      • Take screenshots showing the same firmware package/image being present in both baselines.
    3. Capture the failure after deleting the old baseline
      • Screenshot of the newer baseline showing the missing/invalid firmware image.
      • Screenshot of the update job failure.
      • Note the exact error message regarding the firmware image not being found/uploaded.
    4. Collect OME logs / Console Debug logs
      • These will be particularly important because Engineering needs to determine whether the repository image is actually deleted or whether the baseline merely retains an invalid reference.
    5. Document the reproduction sequence

      For example:

      Baseline A → Firmware image X
      Baseline B → Firmware image X
      Delete Baseline A + its versions
      Firmware image X is removed
      Baseline B → image X unavailable → baseline becomes invalid

    Regarding the workaround

    Unfortunately, if the shared image is actually being deleted when the old baseline is removed, keeping the old baseline is effectively a workaround, but obviously not a desirable one.

     

    If you're working through Dell Support, open a technical support case for OpenManage Enterprise / Update Manager and explicitly request a Product/Engineering escalation for a suspected software defect.

    Dell-ArunK

    Social Media and Communities Professional

    Dell Technologies | Enterprise Support Services

    #IWork4Dell

    Did I answer your query? Please click on ‘Mark as Accepted Answer’. ‘Thumbs up’ the posts you like!