Skip to content

Tarantool installation stuck when previous version of config is discovered #73

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
ligurio opened this issue Oct 28, 2020 · 2 comments · Fixed by #88
Closed

Tarantool installation stuck when previous version of config is discovered #73

ligurio opened this issue Oct 28, 2020 · 2 comments · Fixed by #88
Labels
bug Something isn't working

Comments

@ligurio
Copy link
Member

ligurio commented Oct 28, 2020

sometimes when apt installs tarantool package it stuck with message:

ubuntu@n1:~$ sudo apt install tarantool               
Reading package lists... Done
Building dependency tree
Reading state information... Done
tarantool is already the newest version (2.6.1.0.gcfe0d1a55-1).
0 upgraded, 0 newly installed, 0 to remove and 63 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up tarantool-common (2.6.1.0.gcfe0d1a55-1) ...
               
Configuration file '/etc/default/tarantool'                                                                                                      
 ==> File on system created by you or by a script.
 ==> File also in package provided by package maintainer.
   What would you like to do about it ?  Your options are:
    Y or I  : install the package maintainer's version         
    N or O  : keep your currently-installed version            
      D     : show the differences between the versions
      Z     : start a shell to examine the situation
 The default action is to keep your current version.
*** tarantool (Y/I/N/O/D/Z) [default=N] ?
                                                                                                                                                 
Configuration file '/etc/logrotate.d/tarantool'
 ==> File on system created by you or by a script.
 ==> File also in package provided by package maintainer.
   What would you like to do about it ?  Your options are:
    Y or I  : install the package maintainer's version         
    N or O  : keep your currently-installed version    
      D     : show the differences between the versions
      Z     : start a shell to examine the situation                   
 The default action is to keep your current version.
*** tarantool (Y/I/N/O/D/Z) [default=N] ?     

How-To Reproduce

  • install 2.6.1.0.gcfe0d1a55-1
  • run script VER=2.6 curl -L https://tarantool.io/cshMMp/release/2.4/installer.sh | bash was run.

Possible solution:

-o Dpkg::Options::=--force-confdef -o Dpkg::Options::=--force-confnew (from https://unix.stackexchange.com/questions/22820/how-to-make-apt-get-accept-new-config-files-in-an-unattended-install-of-debian-f)

@ligurio ligurio changed the title Override tarantool config if it exists Tarantool installation stuck when previous version of config is discovered Oct 28, 2020
@Totktonada
Copy link
Member

Maybe export DEBIAN_FRONTEND=noninteractive will help.

@ligurio ligurio added the bug Something isn't working label Apr 5, 2021
@ligurio
Copy link
Member Author

ligurio commented May 25, 2021

Thanks, Alexander!

Jepsen sets DEBIAN_FRONTEND=noninteractive by default in function that installs packages on Debian (our source code uses these helpers). jepsen.tarantool installs Tarantool itself using in two ways: self building and using tarantool.io/installer.sh. Although I didn't see problem described in issue for a long time I think it is worth to set DEBIAN_FRONTEND for installer.sh too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants