S3 Marketplace app from old FE not visible on new FE

Integration Support Marketplace Appliances
1

Hi OpenNebula community,

I have two OpenNebula front-ends using the same private S3-backed marketplace bucket.

On the old FE, the marketplace is:

Marketplace ID: 101
Name: 5G Marketplace
MARKET_MAD: s3

I exported an image from the old FE, which created:

MarketplaceApp ID: 160
Name: blue-arcus-2025-old-fe
Type: IMAGE
State: rdy
Source: s3://onexnaas/marketapp-160
Format: qcow2
Size: 600G
Origin ID: 150
Marketplace ID: 101

On the new FE, the same S3 marketplace is configured and enabled, but with a different marketplace ID:

Marketplace ID: 100
Name: 5G Marketplace
MARKET_MAD: s3

The issue is that MarketplaceApp 160 does not appear on the new FE, even though both front-ends point to the same S3 bucket.

My questions:

  1. Is this expected behavior for S3-backed marketplaces?

  2. Are MarketplaceApp records stored only in the local OpenNebula database?

  3. Is there a supported way to make the new FE register or discover the existing S3 object s3://onexnaas/marketapp-160 without re-uploading it?

  4. Can a MarketplaceApp record be safely created on the new FE pointing to the existing S3 object?

Thanks.

2

Hello,

OpenNebula reads Marketplace App metadata from its local DB, not directly from the Marketplace backend/storage itself.

So for example:

  1. You have one Marketplace
  2. You have two separate OpenNebula deployments

In ONE1 , you upload an nginx Marketplace App — it becomes visible because metadata is stored in the local DB of that deployment.

In ONE2 , the app is not visible, because this deployment does not have the corresponding DB record for that Marketplace App, even if both deployments point to the same Marketplace backend/storage.

Best regards.

3

@hoosain the only way to make the same private marketplace accessible from 2+ OpenNebula clouds is to join them into Federation.