Background

After upgrade to v. 0.5 I am unable to start LND node.
Error message: unable to open channeldb: unable to update edge policies: unable to fetch node: 028925a789df879d8cde4149f099efd76f4bcab87a30c2e6f48e34a984300343f6, unable to find node
ln

Your environment

lnd --version
lnd version 0.5.0-beta commit=3b2c807288b1b7f40d609533c1e96a510ac5fa6d

uname -a
Linux schhh-lightning 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

btcd --version
btcd version 0.12.0-beta

-- Mainet
-- No channels with the node that can't be fetched.
-- The node in issue is not even in peer list.
-- During my investigation I figured out that if I remove the channeldb from data folder, I am enable to start the node, but all channels and channel balances are lost.
-- I revert back to version 0.4.2-beta and I am running a health node:
---- 18 open channels
------ 15 active=true,
------ 3 active = false

Steps to reproduce

1, stop lnd daemon
-- lnd stop
2. Update the lnd version
-- cd $GOPATH/src/github.com/lightningnetwork/lnd
-- git pull
-- make && make install

3. start lnd deamon:
   -- lnd

Expected behaviour

lnd daemon v. 0.5 starts and waits for wallet password

Actual behaviour

Log nohup.out:

2018-09-17 19:46:30.180 [INF] LTND: Active chain: Bitcoin (network=mainnet)
2018-09-17 19:46:30.181 [INF] CHDB: Checking for schema update: latest_version=6, db_version=3
2018-09-17 19:46:30.181 [INF] CHDB: Performing database schema migration
2018-09-17 19:46:30.181 [INF] CHDB: Applying migration #4
2018-09-17 19:46:30.206 [INF] CHDB: Unable to apply migration #4
2018-09-17 19:46:30.209 [ERR] LTND: unable to open channeldb: unable to update edge policies: unable to fetch node: 028925a789df879d8cde4149f099efd76f4bcab87a30c2e6f48e34a984300343f6, unable to find node
2018-09-17 19:46:30.209 [INF] LTND: Shutdown complete
unable to update edge policies: unable to fetch node: 028925a789df879d8cde4149f099efd76f4bcab87a30c2e6f48e34a984300343f6, unable to find node