# S3 Marketplace app from old FE not visible on new FE

**URL:** <https://forum.opennebula.io/t/s3-marketplace-app-from-old-fe-not-visible-on-new-fe/14456>\
**Category:** Marketplace Appliances\
**Created:** [May 4, 2026, 5:19pm UTC](https://forum.opennebula.io/t/s3-marketplace-app-from-old-fe-not-visible-on-new-fe/14456 "2026-05-04T17:19:46Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![hoosain](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/hoosain/32/8554_2.png) [@hoosain](https://forum.opennebula.io/u/hoosain)\
**Post date:** [May 4, 2026, 5:19pm UTC](https://forum.opennebula.io/t/s3-marketplace-app-from-old-fe-not-visible-on-new-fe/14456/1 "2026-05-04T17:19:46Z")

</div>

Hi OpenNebula community,

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

On the **old FE** , the marketplace is:

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

```

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

```auto
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:

```auto
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.

---

<div class="post-metadata">

**Author:** ![Dmitrii](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/dmitrii/32/8980_2.png) [@Dmitrii](https://forum.opennebula.io/u/Dmitrii)\
**Post date:** [May 7, 2026, 3:50pm UTC](https://forum.opennebula.io/t/s3-marketplace-app-from-old-fe-not-visible-on-new-fe/14456/2 "2026-05-07T15:50:44Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![mkutouski](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/mkutouski/32/7923_2.png) [@mkutouski](https://forum.opennebula.io/u/mkutouski)\
**Post date:** [May 8, 2026, 4:02pm UTC](https://forum.opennebula.io/t/s3-marketplace-app-from-old-fe-not-visible-on-new-fe/14456/3 "2026-05-08T16:02:09Z")

</div>

@hoosain the only way to make the same private marketplace accessible from 2+ OpenNebula clouds is to join them into [Federation](https://docs.opennebula.io/7.2/product/control_plane_configuration/data_center_federation/config/).

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex031/uploads/opennebula/original/2X/1/14d66f1130b9cd292905f575da9b68a9f574dd03.png) [@system](https://forum.opennebula.io/u/system)\
**Post date:** [June 7, 2026, 4:03pm UTC](https://forum.opennebula.io/t/s3-marketplace-app-from-old-fe-not-visible-on-new-fe/14456/4 "2026-06-07T16:03:09Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.