mycelium/www_migrate_mycelium

Fork 0

Unable to deploy on v3 nodes after registration on Migration Hub #68

New issue

Open

opened 2026-03-26 09:10:00 +00:00 by Sherwint · 3 comments

Sherwint commented

2026-03-26 09:10:00 +00:00

Member

NodeID_7076
Error shown in the screenshot below:

Scott advised: the node has been opted-out from v3 and it's no longer possible to deploy via the usual v3 deployment flow.

- NodeID_7076 - Error shown in the screenshot below: ![image](/attachments/8426fd5a-a537-4481-8a72-855f31ca238b) - Scott advised: the node has been opted-out from v3 and it's no longer possible to deploy via the usual v3 deployment flow.

image.png

60 KiB

sabrinasadik commented

2026-03-26 09:12:43 +00:00

Member

Shouldnt opt out of v3 if mycelium project migration hub is only registration for now (according to what we said here).

Shouldnt opt out of v3 if mycelium project migration hub is only registration for now (according to what we said [here](https://forum.threefold.io/t/understanding-the-migration-hub-how-to-move-your-nodes-to-project-mycelium/4715)).

sameh-farouk commented

2026-03-26 09:58:07 +00:00

Member

I was checking this, and based on the code I've already read on the codebase of the portal, The "Register on Mycelium" flow calls opt_out_of_v3_billing on TFChain before registering on the marketplace. Once a node is opted out of V3, it can no longer accept V3 deployments, and workloads can't be deployed to it through the normal TFGrid flow.
The error on the screenshot (module 26 index 54, coming from outdated client) refer to the smart contract pallet's OnlyTwinAdminCanDeployOnThisNode error (Mycelium flow).

So, the node becomes effectively unusable temporally until Mycelium's deployment system (the marketplace) is live.
This is a product/business decision, not a code bug .. the code does exactly what it was designed to do.

I was checking this, and based on the code I've already read on the codebase of the portal, The "Register on Mycelium" flow calls `opt_out_of_v3_billing` on TFChain before registering on the marketplace. Once a node is opted out of V3, it can no longer accept V3 deployments, and workloads can't be deployed to it through the normal TFGrid flow. The error on the screenshot (module 26 index 54, coming from outdated client) refer to the smart contract pallet's `OnlyTwinAdminCanDeployOnThisNode` error (Mycelium flow). So, the node becomes effectively unusable temporally until Mycelium's deployment system (the marketplace) is live. This is a product/business decision, not a code bug .. the code does exactly what it was designed to do.

sameh-farouk commented

2026-04-06 13:15:36 +00:00

Member

Also note, the user has two main independent actions:

Register on Mycelium Ledger in Identity/Pre-Register page -> Creates Hero Ledger account + email verification. It never touches nodes or V3 opt-out.
Move node to Mycelium in My Nodes page -> Opt-out V3 billing on TFChain + register on marketplace (creating a sellable listing for the node's resources on the Mycelium marketplace via a NEAR smart contract call)

The user in the issue likely clicked "Move to Mycelium" on their node, which opted it out of V3 and and registered it on the marketplace. The node becomes available for Mycelium workloads and can't accept V3 deployments after that.

Also note, the user has two main independent actions: 1. Register on Mycelium Ledger in Identity/Pre-Register page -> Creates Hero Ledger account + email verification. It never touches nodes or V3 opt-out. 2. Move node to Mycelium in My Nodes page -> Opt-out V3 billing on TFChain + register on marketplace (creating a sellable listing for the node's resources on the Mycelium marketplace via a NEAR smart contract call) The user in the issue likely clicked "Move to Mycelium" on their node, which opted it out of V3 and and registered it on the marketplace. The node becomes available for Mycelium workloads and can't accept V3 deployments after that.

No labels

No milestone

No project

No assignees

3 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

mycelium/www_migrate_mycelium#68

No description provided.

Rows
Columns