westend and kusama nodes cannot be upgraded v1.18.0, show error:"/usr/bin/polkadot": stat own /usr/bin/polkadot: no such file or directory: unknown

[kate102066]

Is there an existing issue?

• I have searched the existing issues

Experiencing problems? Have you tried our Stack Exchange first?

• This is not a support question.

Description of bug

"/usr/bin/polkadot": stat own /usr/bin/polkadot: no such file or directory: unknown

Above is a screenshot of the node log, the error reported above prevents upgrading to the latest version

Steps to reproduce

No response

[alexggh]

First I don't think 1.18.0 is released yet, so how did you end up to this version ?

FYI @EgorPopelyaev

[ggwpez]

We should re-tag that docker image as v1.18.0-rc1 or something

[kate102066]

Ok, I see that v1.18.0 has already been renamed, so is the recommended version still 1.17.2, or is it recommended to upgrade to v1.18.0-rc1 ? @ggwpez @alexggh

[alexggh]

Ok, I see that v1.18.0 has already been renamed, so is the recommended version still 1.17.2, or is it recommended to upgrade to v1.18.0-rc1 ? @ggwpez @alexggh

1.7.2 it is our newest official version.
1.18.0-rc1 it is our first release candidate for v1.18.0, that means the QA is not full finished and it might suffer minor changes/fixes.

It's up to you which one you want to use.

[kate102066]

Ok, I see that v1.18.0 has already been renamed, so is the recommended version still 1.17.2, or is it recommended to upgrade to v1.18.0-rc1 ? @ggwpez @alexggh

1.7.2 it is our newest official version. 1.18.0-rc1 it is our first release candidate for v1.18.0, that means the QA is not full finished and it might suffer minor changes/fixes.

It's up to you which one you want to use.

thanks

[kate102066]

Hey @alexggh @ggwpez , since the last node update to v1.80.0, we can't change our nodes to other versions. As long as they are changed to other versions they will encounter the issue and can't be upgraded.
`====================

Version: 1.17.3-06158dd26ba

0: sp_panic_handler::set::{{closure}}

1: std::panicking::rust_panic_with_hook

2: std::panicking::begin_panic_handler::{{closure}}

3: std::sys::backtrace::__rust_end_short_backtrace

4: rust_begin_unwind

5: core::panicking::panic_fmt

6: sc_client_db::Backend::try_commit_operation

7: <sc_client_db::Backend as sc_client_api::backend::Backend>::commit_operation

8: <&sc_service::client::client::Client<B,E,Block,RA> as sc_consensus::block_import::BlockImport>::import_block::{{closure}}

9: <alloc::sync::Arc as sc_consensus::block_import::BlockImport>::import_block::{{closure}}

10: <cumulus_client_consensus_common::ParachainBlockImport<Block,BI,BE> as sc_consensus::block_import::BlockImport>::import_block::{{closure}}

11: <alloc::boxed::Box<dyn sc_consensus::block_import::BlockImport+Error = sp_consensus::error::Error+core::marker::Send+core::marker::Sync> as sc_consensus::block_import::BlockImport>::import_block::{{closure}}

12: sc_consensus::import_queue::import_single_block_metered::{{closure}}

13: sc_consensus::import_queue::basic_queue::BlockImportWorker::new::{{closure}}

14: <futures_util::future::future::Map<Fut,F> as core::future::future::Future>::poll

15: <tracing_futures::Instrumented as core::future::future::Future>::poll

16: tokio::runtime::task::raw::poll

17: std::sys::backtrace::__rust_begin_short_backtrace

18: core::ops::function::FnOnce::call_once{{vtable.shim}}

19: std::sys::pal::unix::thread::Thread::new::thread_start

20:

21:

Thread 'tokio-runtime-worker' panicked at 'internal error: entered unreachable code: Unsupported block gap. TODO: #5406', /__w/polkadot-sdk/polkadot-sdk/substrate/client/db/src/lib.rs:1714

This is a bug. Please report it

at:`