Bug 2143682 - ReaR backup task must be run as async
Summary: ReaR backup task must be run as async
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: tripleo-ansible
Version: 17.1 (Wallaby)
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
: ---
Assignee: Juan Larriba
QA Contact: Joe H. Rahme
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-17 14:10 UTC by Juan Larriba
Modified: 2023-08-07 09:34 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-06-07 11:49:04 UTC
Target Upstream Version:
Embargoed:
fdiazbra: needinfo-


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-20265 0 None None None 2022-11-17 14:12:47 UTC

Description Juan Larriba 2022-11-17 14:10:54 UTC
Currently, the ReaR task that runs the backup using ansible is:


- name: Create the node backup
  command: rear {{ (tripleo_backup_and_restore_rear_simulate | bool) | ternary('-s ', '') }}-d -v mkbackup
  register: tripleo_backup_and_restore_rear_output
  when: tripleo_backup_and_restore_rear_output is undefined
  tags:
    - bar_create_recover_image

This task is very long running (over 40 minutes) so if the controllers have some kind of session timeout (like the one specified by the env variable TMOUT), this will kill the task and end the backup.

It would be necessary to add an async configuration to this task so it runs as async while, with a poll, the playbook execution waits for the finalization of the task:

async: 3600
poll: 60

Comment 1 Carlos Camacho 2023-06-07 11:49:04 UTC
Rear is marked to be deprecated in 17.1 and we never hit any regression in any customer or pipeline with this timeout


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