Project

General

Profile

Actions

Bug #6291

closed

Zypper hangs on dialogs / issues due to open tty

Added by Florian Heigl about 9 years ago. Updated almost 2 years ago.

Status:
Released
Priority:
N/A
Category:
Generic methods
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

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.

Actions

Also available in: Atom PDF