[
https://issues.apache.org/jira/browse/AIRAVATA-3609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17572611#comment-17572611
]
Marcus Christie commented on AIRAVATA-3609:
-------------------------------------------
Checking for `failed` or `success` changed in Ansible 2.9 (deprecated in 2.5).
https://docs.ansible.com/ansible/latest/porting_guides/porting_guide_2.5.html#jinja-tests-used-as-filters
I've gone through and updated places where we were doing the old style to the
new style. (I only updated the Ansible scripts we actually use, there are some
older ones we should probably remove since we aren't using them any longer.)
> Update Ansible scripts for Rocky Linux and Python 3
> ---------------------------------------------------
>
> Key: AIRAVATA-3609
> URL: https://issues.apache.org/jira/browse/AIRAVATA-3609
> Project: Airavata
> Issue Type: Task
> Components: Django Portal
> Reporter: Marcus Christie
> Assignee: Marcus Christie
> Priority: Major
>
> h3. TODO
> - (/) Fix delegation of database setup tasks (see
> https://github.com/ansible/ansible/issues/37995)
> - (/) Either install django apps as editable or figure out how to get built
> JS into the package. MANIFEST includes don't seem to apply to post install
> generated files.
> - [ ] configure alternate gateway data store resource ids (moving portal to a
> new data storage resource means resource ids won't match, but we can map more
> than one to the same directory in settings_local.py)
> - [ ] nodejs/yarn install
> - [ ] with the upgraded Ansible, can add a check to see if Docker is running
> - (/) switch from yum-cron to dnf-automatic on Rocky Linux
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
