Reviewed: https://review.opendev.org/c/starlingx/ansible-playbooks/+/852020 Committed: https://opendev.org/starlingx/ansible-playbooks/commit/4c8117534fdd3a84934b3815f0b76f74d99a68aa Submitter: "Zuul (22348)" Branch: master
commit 4c8117534fdd3a84934b3815f0b76f74d99a68aa Author: Thiago Brito <email address hidden> Date: Wed Aug 3 10:01:47 2022 -0300
Fixing unquoted backslashes for grep -E
After the merge of [1], the restore playbook fails with a message saying "We could be wrong, but this one looks like it might be an issue with missing quotes" at either L243 or L265. This is due to backslash not properly scaped for yaml syntax.
[1]https://review.opendev.org/c/starlingx/ansible-playbooks/+/848770
TEST PLAN PASS run restore playbook
Closes-Bug: #1983475 Signed-off-by: Thiago Brito <email address hidden> Change-Id: Idcb5f5939a2a706afe1da1075397652e55dd37d0
Reviewed: https:/ /review. opendev. org/c/starlingx /ansible- playbooks/ +/852020 /opendev. org/starlingx/ ansible- playbooks/ commit/ 4c8117534fdd3a8 4934b3815f0b76f 74d99a68aa
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 4c8117534fdd3a8 4934b3815f0b76f 74d99a68aa
Author: Thiago Brito <email address hidden>
Date: Wed Aug 3 10:01:47 2022 -0300
Fixing unquoted backslashes for grep -E
After the merge of [1], the restore playbook fails with a message
saying "We could be wrong, but this one looks like it might be an issue
with missing quotes" at either L243 or L265. This is due to backslash
not properly scaped for yaml syntax.
[1]https:/ /review. opendev. org/c/starlingx /ansible- playbooks/ +/848770
TEST PLAN
PASS run restore playbook
Closes-Bug: #1983475 6afe1da10753976 52e55dd37d0
Signed-off-by: Thiago Brito <email address hidden>
Change-Id: Idcb5f5939a2a70