Unable to apply migration #6

[lnd-d]

Background

When upgrading from version 0.4.2-beta to 0.5-beta the node cannot be started anymore.

Your environment

• lnd version 0.5.0-beta
• Debian
• bitcoind 0.16.2

Steps to reproduce

lncli stop
cd $GOPATH/src/github.com/lightningnetwork/lnd
git pull
make && make install
lnd

Expected behaviour

lnd should start

Actual behaviour

 [INF] LTND: Version 0.5.0-beta commit=
 [INF] LTND: Active chain: Bitcoin (network=mainnet)
 [INF] CHDB: Checking for schema update: latest_version=6, db_version=0
 [INF] CHDB: Performing database schema migration
 [INF] CHDB: Applying migration #1
 [INF] CHDB: Populating new node update index bucket
 [INF] CHDB: Populating new edge update index bucket
 [INF] CHDB: Migration to node and edge update indexes complete!
 [INF] CHDB: Applying migration #2
 [INF] CHDB: Migrating invoice database to new time series format
 [INF] CHDB: Migration to invoice time series index complete!
 [INF] CHDB: Applying migration #3
 [INF] CHDB: Applying migration #4
 [INF] CHDB: Migration of edge policies complete!
 [INF] CHDB: Applying migration #5
 [INF] CHDB: Migrating database to support payment statuses
 [INF] CHDB: Marking all known circuits with status InFlight
 [INF] CHDB: Marking all existing payments with status Completed
 [INF] CHDB: Applying migration #6
 [INF] CHDB: Migrating database to properly prune edge update index
 [INF] CHDB: Unable to apply migration #6
 [ERR] LTND: unable to open channeldb: unable to remove existing edge update index: delete bucket: incompatible value
 [INF] LTND: Shutdown complete
unable to remove existing edge update index: delete bucket: incompatible value

Hi, I'm getting the same issue. Attaching my log file.
lnd.log

[lnd-d]

I have a dirty workaround:
edit $GOPATH/src/github.com/lightningnetwork/lnd/channeldb/migrations.go

Remove parts of function migratePruneEdgeUpdateIndex migration #6 like below then it should start.
I remove lines 480 to 556.

func migratePruneEdgeUpdateIndex(tx *bolt.Tx) error {
	// To begin the migration, we'll retrieve the update index bucket. If it
	// does not exist, we have nothing left to do so we can simply exit.
	edges := tx.Bucket(edgeBucket)
	if edges == nil {
		return nil
	}
	edgeUpdateIndex := edges.Bucket(edgeUpdateIndexBucket)
	if edgeUpdateIndex == nil {
		return nil
	}

	log.Info("Migration to properly prune edge update index complete!")

	return nil
}

Don't know it that broke something but it works. Anyways use at own risk.

[Roasbeef]

I just made a new node, started it at 0.4.2, then updated to 0.5 and the migration went through no problem on my end.

[Roasbeef]

Which commit did both of y'all start from?

I started from 0.4.0

[lnd-d]

Me too

[cfromknecht]

@lnd-d that change will definitely break some things if anyone runs it 😬