{"id":14489,"date":"2026-10-16T12:04:29","date_gmt":"2026-10-16T10:04:29","guid":{"rendered":"https:\/\/irg-net.com\/?p=14489"},"modified":"2026-10-16T13:06:56","modified_gmt":"2026-10-16T11:06:56","slug":"vks-update-fails-with-supervisor-content-is-being-processed","status":"publish","type":"post","link":"https:\/\/irg-net.com\/index.php\/vks-update-fails-with-supervisor-content-is-being-processed\/","title":{"rendered":"VKS Update fails with “supervisor content is being processed”"},"content":{"rendered":"
\n
\"\"<\/figure>\n<\/div>\n\n\n
<\/div>\n\n\n\n

While preparing an update of our Supervisor cluster (VKS01) from v1.32.9 to v1.33.13 on vSphere 9.1, the update wizard looked perfectly healthy at first: the pre-checks in step 1 turned green. Then, in step 2 (“Review”), the wizard refused to continue with this error:<\/p>\n\n\n\n

<\/div>\n\n\n\n
\"\"<\/figure>\n\n\n\n
<\/div>\n\n\n\n

A general system error occurred. Error message: supervisor content is being processed.<\/strong><\/p>\n\n\n\n

The message is generic and does not tell you what content is being processed, or why it never finishes. A search in the Broadcom Knowledge Base did not return an article for this exact wizard error, but the same string shows up in several related articles \u2013 always in connection with the Supervisor Content Library.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Finding the real error<\/h2>\n\n\n\n

The wizard error is only a symptom. The actual cause is displayed one level up: in the vSphere Client under Supervisor Management > Updates, a red banner appears at the top of the page:<\/p>\n\n\n\n

<\/div>\n\n\n\n
\"\"<\/figure>\n\n\n\n
<\/div>\n\n\n\n

Error processing Content Library 2b654261-0890-4ceb-b767-f1a71ba7403e, Error: malformed Supervisor OVF template name<\/strong> ‘ob-24773265-ubuntu-2204-amd64-v1.28.15—vmware.3-fips-vkr.3’. The template name must be in the format ‘supervisor-<supervisor version>’. Example: supervisor-9.1.0.0-25004320.<\/p>\n\n\n\n

This is the key. The Content Library that is assigned for Supervisor content distribution contains an item that does not belong there:<\/p>\n\n\n\n

    \n
  • Expected:<\/strong> items named supervisor-<version> (the Supervisor update images).<\/li>\n\n\n\n
  • Found:<\/strong> a vSphere Kubernetes release (VKr) node image for guest clusters \u2013 Ubuntu 22.04, Kubernetes v1.28.15 \u2013 named ob-24773265-ubuntu-2204-\u2026-vkr.3.<\/li>\n<\/ul>\n\n\n\n

    The Supervisor tries to parse every item in the library as a Supervisor template. Because this item does not match the naming format, the library is never marked as processed, the catalog is not “ready”, and every operation that needs the Supervisor content \u2013 including the update \u2013 fails with “supervisor content is being processed”.<\/p>\n\n\n\n

    <\/div>\n\n\n\n

    Why this happens<\/h2>\n\n\n\n

    VKr images and Supervisor images are two different content types and should live in different libraries. A typical cause is that a single (often local or subscribed) library was assigned for both purposes, or that a library with VKr images was assigned to the Supervisor by mistake. The same pattern is described in several Broadcom articles:<\/p>\n\n\n\n

      \n
    • KB 412096<\/strong> \u2013 the Supervisor logs “supervisor content is being processed” \/ “catalog is not ready”, Content Distribution shows “Error processing Content Library \u2026 malformed Supervisor OVF template name”, and the host configuration gets stuck.<\/li>\n\n\n\n
    • KB 416011<\/strong> \u2013 an unknown library was incorrectly associated with the WCP service, so the Supervisor content library was never initialized.<\/li>\n\n\n\n
    • KB 442757 and KB 440378<\/strong> \u2013 a non-VKS item or library in the content library configuration breaks the VKS\/Supervisor service compatibility pre-checks.<\/li>\n<\/ul>\n\n\n\n
      <\/div>\n\n\n\n

      How to confirm it on VCSA<\/h2>\n\n\n\n

      If you want proof before changing anything, check the WCP service log on the vCenter Server Appliance:<\/p>\n\n\n\n

      <\/circle><\/circle><\/circle><\/g><\/svg><\/span>