Project

General

Profile

Bug #6291

Zypper hangs on dialogs / issues due to open tty

Added by Florian Heigl almost 4 years ago. Updated 10 months ago.

Status:
Released
Priority:
N/A
Category:
Generic methods - Package Management
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Priority:
58

Description

There's a few places where we're calling zypper.
Zypper notices that there's an open tty and runs in interactive mode.
The result is when you have unavailable repositories or key issues (i.e. nightly rudder repos) or anything else that could use manual input, zypper will stop with the relevant dialog.

i.e. in cfengine stdlib:
$ grep -R "zypper pat" *
initial-promises/node-server/common/1.0/cfengine_stdlib.cf: package_patch_list_command => "/usr/bin/zypper patches";
initial-promises/node-server/common/1.0/cfengine_stdlib.cf: package_patch_list_command => "/usr/bin/zypper patches"

same goes with most of the other techniques.

There is a --non-interactive flag, which (great) comes with safe defaults; this could be easily used, otherwise one could also try closing the tty.

Associated revisions

Revision 74511564 (diff)
Added by Alexis MOUSSET 12 months ago

Fixes #6291: Zypper hangs on dialogs / issues due to open tty

History

#1 Updated by Nicolas CHARLES almost 4 years ago

  • Status changed from New to Discussion
  • Assignee set to Florian Heigl

Florian,

The Technique rpmPackageInstallation alreay uses --non-interactive parameter, as well as ncf
In the initial promises, we are using the package_method generic, that also uses --non-interactive

Do you have specific example where we use zypper in non-interactive mode ?

Just as a remark, we don't use most of the bundles in the cfengine standart librairy; they are there, but we just don't need them

#2 Updated by Nicolas CHARLES almost 4 years ago

Oh, if the non-interactive mode is used, and the repository is not signed, zypper complains about not having tty
Could it be this issue that you are encoutering ?

#3 Updated by Benoît PECCATTE over 2 years ago

  • Target version set to 2.11.21

#4 Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 2.11.21 to 2.11.22

#5 Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 2.11.22 to 2.11.23

#6 Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 2.11.23 to 2.11.24

#7 Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 2.11.24 to 308

#8 Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 308 to 3.1.14

#9 Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 3.1.14 to 3.1.15

#10 Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 3.1.15 to 3.1.16

#11 Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 3.1.16 to 3.1.17

#12 Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 3.1.17 to 3.1.18

#13 Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 3.1.18 to 3.1.19

#14 Updated by Jonathan CLARKE over 1 year ago

  • Severity set to Major - prevents use of part of Rudder | no simple workaround
  • User visibility set to Getting started - demo | first install | level 1 Techniques

#15 Updated by Benoît PECCATTE over 1 year ago

  • Priority set to 45

#16 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.19 to 3.1.20

#17 Updated by Jonathan CLARKE over 1 year ago

  • Status changed from Discussion to New
  • Assignee deleted (Florian Heigl)

#18 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.20 to 3.1.21

#19 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.21 to 3.1.22

#20 Updated by Benoît PECCATTE over 1 year ago

  • Priority changed from 45 to 58

#21 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.22 to 3.1.23

#22 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.23 to 3.1.24

#23 Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 3.1.24 to 3.1.25

#24 Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 3.1.25 to 387

#25 Updated by Alexis MOUSSET 12 months ago

  • Project changed from Rudder to ncf
  • Category changed from System integration to Generic methods - Package Management
  • Assignee set to Alexis MOUSSET
  • Target version changed from 387 to 4.1.10

It seems we are not calling zypper with non-interactive everywhere.

#26 Updated by Alexis MOUSSET 12 months ago

  • Status changed from New to In progress

#27 Updated by Alexis MOUSSET 12 months ago

  • In package_install/remove/check we use the ncf_generic* bundles which are fixed by this PR
  • In the technique and package_present/absent we use the zypper package module wich already has the non-interactive option
  • In the deprecated technique we already have non-interactive option

#28 Updated by Alexis MOUSSET 12 months ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Alexis MOUSSET to Benoît PECCATTE
  • Pull Request set to https://github.com/Normation/ncf/pull/671

#29 Updated by Alexis MOUSSET 12 months ago

  • Status changed from Pending technical review to Pending release

#30 Updated by Vincent MEMBRÉ 10 months ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.1.10 and 4.2.4 which were released today.

Also available in: Atom PDF