Bug 2143682

Summary: ReaR backup task must be run as async
Product: Red Hat OpenStack Reporter: Juan Larriba <jlarriba>
Component: tripleo-ansibleAssignee: Juan Larriba <jlarriba>
Status: CLOSED NOTABUG QA Contact: Joe H. Rahme <jhakimra>
Severity: medium Docs Contact:
Priority: low    
Version: 17.1 (Wallaby)CC: ccamacho, dpini, fdiazbra, jpretori, mciecier
Target Milestone: ---Keywords: Triaged
Target Release: ---Flags: fdiazbra: needinfo-
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-06-07 11:49:04 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:

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