Bug 1879850
| Summary: | Setting fact failed in the satellite clone with template error | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Devendra Singh <desingh> |
| Component: | Satellite Clone | Assignee: | Chris Roberts <chrobert> |
| Status: | CLOSED ERRATA | QA Contact: | Vladimír Sedmík <vsedmik> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.7.0 | CC: | chrobert, egolov, jomitsch, mmccune |
| Target Milestone: | 6.8.0 | Keywords: | Regression, Triaged, UpgradeBlocker |
| Target Release: | Unused | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | satellite-clone-1.6.1 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-10-27 12:38:46 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: | |||
Devendra, What ansible version was used? I suspect that ansible updated in the rhel-7-server-extras-rpms repo and that version no longer supports the syntax we use. (In reply to John Mitsch from comment #5) > Devendra, > > What ansible version was used? I suspect that ansible updated in the > rhel-7-server-extras-rpms repo and that version no longer supports the > syntax we use. We used 2.9.13 ansible version. (.env) #$ ansible --version ansible 2.9.13 config file = /etc/ansible/ansible.cfg configured module search path = [u'/home/jenkins/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules'] ansible python module location = /usr/lib/python2.7/site-packages/ansible executable location = /usr/bin/ansible python version = 2.7.15 (default, May 9 2018, 11:32:33) [GCC 7.3.1 20180130 (Red Hat 7.3.1-2)] What version of ansible are we shipping with satellite-clone? I am seeing only 2.4 available for these repos: [root@sat-clone-test1 ~]# yum provides ansible ... ansible-2.4.0.0-1.el7ae.noarch : SSH-based configuration management, deployment, and task execution system Repo : rhel-7-server-satellite-maintenance-6-rpms ansible-2.4.2.0-2.el7.noarch : SSH-based configuration management, deployment, and task execution system Repo : rhel-7-server-satellite-maintenance-6-beta-rpms ansible-2.4.2.0-2.el7.noarch : SSH-based configuration management, deployment, and task execution system Repo : rhel-7-server-satellite-maintenance-6-rpms ansible-2.4.2.0-2.el7.noarch : SSH-based configuration management, deployment, and task execution system Repo : @rhel-7-server-extras-rpms After a discussion off-thread, we are using ansible 2.8 for Satellite 6.7. The current sat-clone syntax should be supported for this. The satellite to ansible version mapping is 6.6 = 2.6, 6.7 = 2.8, 6.8 = 2.9 It looks like we will run into this issue for 6.8, so we could keep this BZ and align it with 6.8 (but also could just fall under a "support 6.8 for sat-clone" BZ) No changes should be necessary for 6.7, can QE update the automation to use ansible 2.8 for satellite 6.7 clones and ensure everything else functions as expected? Though this isn't needed for 6.7, it has been fixed in https://github.com/RedHatSatellite/satellite-clone/archive/1.6.1.tar.gz QE verified their automation with the latest upstream fix (https://github.com/RedHatSatellite/satellite-clone/pull/374) and it work fine Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Satellite 6.8 Satellite Maintenance Release), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4365 |
Description of problem: Setting fact failed in the satellite clone with template error Version-Release number of selected component (if applicable): 6.7 How reproducible: always Steps to Reproduce: 1. Use upstream satellite-clone master branch. 2. Update all the required configuration file to trigger the satellite-clone-playbook.yml job for restore. 3. while setting the fact of satellite-version it gets failed. : FAILED! => {"msg": "The conditional check 'backup_metadata | success' failed. The error was: template error while templating string: no filter named 'success'. String: {% if backup_metadata | success %} True {% else %} False {% endif %}\n\nThe error appears to be in 'satellite-clone/roles/satellite-clone/tasks/backup_satellite_version_check.yml': line 30, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: setting fact - satellite_version\n ^ here\n"} msg: The conditional check 'backup_metadata | success' failed. The error was: template error while templating string: no filter named 'success'. String: {% if backup_metadata | success %} True {% else %} False {% endif %} The error appears to be in 'satellite-clone/roles/satellite-clone/tasks/backup_satellite_version_check.yml': line 30, column 3, but may be elsewhere in the file depending on the exact syntax problem. The offending line appears to be: - name: setting fact - satellite_version ^ here Actual results: Setting fact failed in the satellite clone with template error Expected results: Setting fact should be completed successfully. Additional info: