-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Closed
ipfs/fs-repo-migrations
#104Labels
kind/bugA bug in existing code (including security flaws)A bug in existing code (including security flaws)need/triageNeeds initial labeling and prioritizationNeeds initial labeling and prioritization
Description
I tried to use the v9 to v10 migration on two nodes, in both cases there was already a QUIC listening definition in the swarm-listening array.
The migration added an identical secondary listening entry for QUIC (twice, one for IPv4 one for IPv6).
On the first node, this ended up with just a weird config, since the port is random:
"Swarm": [
"/ip4/0.0.0.0/tcp/0",
"/ip6/::/tcp/0",
"/ip4/0.0.0.0/udp/0/quic",
"/ip6/::/udp/0/quic",
"/ip4/0.0.0.0/udp/0/quic",
"/ip6/::/udp/0/quic"
]
On the secondary node this is ending up with this duplicate entries:
"Swarm": [
"/ip4/0.0.0.0/tcp/443",
"/ip6/::/tcp/443",
"/ip4/0.0.0.0/udp/443/quic",
"/ip6/::/udp/443/quic",
"/ip4/0.0.0.0/udp/443/quic",
"/ip6/::/udp/443/quic"
]
Proposed solution
If there's any quic definition in the listing ports, just skip this migration step.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
kind/bugA bug in existing code (including security flaws)A bug in existing code (including security flaws)need/triageNeeds initial labeling and prioritizationNeeds initial labeling and prioritization