Bug 1726992

Summary:	Cannot restore using Bacula method due to "bconsole" not showing its prompt
Product:	Red Hat Enterprise Linux 8	Reporter:	Renaud Métrich <rmetrich>
Component:	rear	Assignee:	Pavel Cahyna <pcahyna>
Status:	CLOSED ERRATA	QA Contact:	David Jež <djez>
Severity:	low	Docs Contact:
Priority:	low
Version:	8.0	CC:	djez, pcahyna
Target Milestone:	rc	Flags:	pm-rhel: mirror+
Target Release:	8.2
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	rear-2.4-11.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-04-28 15:47:07 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1726982
Bug Blocks:	1746915

Description Renaud Métrich 2019-07-04 08:38:10 UTC

This bug was initially created as a copy of Bug #1726982

I am copying this bug because: it applies on ReaR shipped by RHEL8



Description of problem:

Cannot restore using Bacula method due to "bconsole" not showing its prompt: its prompt is sent to ReaR's log instead of stdout (which is FD 7 in ReaR).

Version-Release number of selected component (if applicable):

rear-* including Upstream


How reproducible:

Always


Steps to Reproduce:
1. Setup backup method to Bacula
2. Setup a bacula server
3. Backup the system

  # rear mkbackup

4. Restore the system

  # rear recover


Actual results:

[...]
Do not exit 'bconsole' until all files are restored

WARNING: The new root is mounted under '$TARGET_FS_ROOT'.

Press ENTER to start bconsole"

--> Nothing shows up


Expected results:

Do not exit 'bconsole' until all files are restored

WARNING: The new root is mounted under '$TARGET_FS_ROOT'.

Press ENTER to start bconsole"

Connecting to Director XXX:9101
1000 OK: bacula-dir Version: 5.2.13 (19 February 2013)
Enter a period to cancel a command.
*


Additional info:

GitHub PR: https://github.com/rear/rear/pull/2173

Comment 1 Pavel Cahyna 2019-07-31 09:24:06 UTC

*** Bug 1729492 has been marked as a duplicate of this bug. ***

Comment 5 errata-xmlrpc 2020-04-28 15:47:07 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:1648