Thank you all for your assistance
141             - name: write the version to an variables file we can 
include in other plays
142       copy:
143         dest: "vars/{{ appname }}-version.yml"
144         content: "oldversion: '{{ oldversion }}'"
145       delegate_to: localhost
146       when:
147         - existingapp.stat.exists == True


With {{ oldversion }} in single quotes. Other things I tried including (on 
line 144) {{ oldversion | quote }} and {{ oldversion | string }} where in 
the task where Im rendering the command for the backup. e.g. 

/usr/lib/postgresql-{{ postgresqlversion }}/bin/pg_dump -h 
/run/postgresql/{{ postgresqlversion }} -C --clean {{ dbname  }}| 
/usr/bin/pigz > {{ dbbackuplocation }}/{{ oldversion | string }}_{{ dbname 
}}_{{ dbbackups.matched }}.sql.gz




On Friday, 13 December 2019 13:40:55 UTC, Dylan Humphreys wrote:
>
> Im getting that bug happen to me, but Im on 2.9.2
>
>  % dpkg -l ansible
>
> Desired=Unknown/Install/Remove/Purge/Hold
>
> | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-
> pend
>
> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
>
> ||/ Name                                                          Version 
>                             Architecture                        
> Description
>
>
> +++-=============================================================-===================================-===================================-================================================================================================================================
>
> ii  ansible                                                       2.9.2-
> 1ppa~xenial                   all                                 Ansible 
> IT Automation
>
>
>
> The code in question:
> msg: "/usr/lib/postgresql-{{ postgresqlversion }}/bin/pg_dump -h 
> /run/postgresql/{{ postgresqlversion }} -C --clean {{ dbname  }}| 
> /usr/bin/pigz > {{ dbbackuplocation }}/{{ oldversion }}_{{ dbname }}_{{ 
> dbbackups.matched }}.sql.gz"
>
> In the above, oldscmversion is:
>
>  % cat vars/demo-scmversion.yml
>
> oldversion: 19.10
>
> However the resulting filename for the above once rendered is "19.1" 
> Ill confess to not know how to find out what version of ansible that bug 
> was actually addressed, but given it was back in 2015, I suspect the fix 
> referred to is in the version I am using. Can anyone help / suggest a work 
> around?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/89ba5b76-89b9-4eff-9a36-27f22dc0a4dc%40googlegroups.com.

Reply via email to