RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1726992 - Cannot restore using Bacula method due to "bconsole" not showing its prompt
Summary: Cannot restore using Bacula method due to "bconsole" not showing its prompt
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: rear
Version: 8.0
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: 8.2
Assignee: Pavel Cahyna
QA Contact: David Jež
URL:
Whiteboard:
: 1729492 (view as bug list)
Depends On: 1726982
Blocks: 1746915
TreeView+ depends on / blocked
 
Reported: 2019-07-04 08:38 UTC by Renaud Métrich
Modified: 2023-05-14 08:24 UTC (History)
2 users (show)

Fixed In Version: rear-2.4-11.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-28 15:47:07 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github rear rear pull 2173 0 'None' closed bacula: Fixed 'bconsole' prompt not displaying at all when doing a recover 2020-04-23 15:10:34 UTC
Red Hat Issue Tracker RHELPLAN-26739 0 None None None 2023-05-14 08:24:38 UTC
Red Hat Product Errata RHBA-2020:1648 0 None None None 2020-04-28 15:47:26 UTC

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


Note You need to log in before you can comment on or make changes to this bug.