search

DarkMatter68 / satcb

Satellite Server 6 Content Baseline - automatically manage content views for consistent patching baseline
GNU General Public License v3.0
4 stars 0 forks source link

Publishing a new CCV version not taking LATEST CV's #1

Closed DarkMatter68 closed 4 years ago

DarkMatter68 commented 4 years ago

When publishing a new CCV version the LATEST CV version is not being associated with the new CCV. Instead it is keeping the current CV version.

DarkMatter68 commented 4 years ago

The variable _available_cv_ccv_list was NOT refreshed before publishing the CCV.

Fix was to put the following code into: step-04_publish_ccv.yaml:-

# #---- # 2020-03-11: Andy (Issue #1 - BEGIN) # # BEFORE WE CAN PUBLISH THE NEW CCV WE MUST REFRESH:- # # _available_cv_ccv_list # # # Otherwise it will not contain the latest versions of # the CV's which we have just published. # # This variable was originally setup in:- # # step-02_setup.yaml # # - name: "{{ _task_name_prefix }} - CLEAR CONTENT VIEW LIST" set_fact: _available_cv_ccv_list: []

- block: - name: "{{ _task_name_prefix }} - REFRESH CONTENT VIEW LIST FROM SATELLITE SERVER [{{ satcb_hostname }}]" uri: url: "{{ _satcb_url_katello_api }}/content_views" method: GET user: "{{ satcb_user }}" password: "{{ satcb_password }}" validate_certs: no force_basic_auth: yes no_log: true register: _available_cv_ccv_list

- debug: var: _available_cv_ccv_list when: _DEBUG_ME == true # # #---- # 2020-03-11: Andy (Issue #1 - END) #`