OpenStack-Ansible

ClamAV update fails if install forces update

Bug #1730998 reported by Jason
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Fix Released
Low
Russell Tweed

Bug Description

In the task file tasks/rhel7stig/misc.yml the ClamAV install kicks off an automatic update of the ClamAV database on ubuntu 16.04.3 (possibly others, did not test). This causes the following task which attempts to perform this update to fail out as the process errors because its already running. I implemented a fix for this in a fork of the repo that can be seen here:

https://github.com/AnonosDev/ansible-hardening/commit/52796452a6c33d4d06303d3b6f233fd57d36df49#diff-93727f5c9f39c55bfad4d13e3af1378b

Jean-Philippe Evrard (jean-philippe-evrard)
Changed in openstack-ansible:
status: New → Confirmed
importance: Undecided → Low
tags: added: low
tags: added: low-hanging-fruit
removed: low
Russell Tweed (russell-tweed)
Changed in openstack-ansible:
assignee: nobody → Russell Tweed (russell-tweed)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to ansible-hardening (master)

Fix proposed to branch: master
Review: https://review.openstack.org/550268

Changed in openstack-ansible:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to ansible-hardening (master)

Reviewed: https://review.openstack.org/550268
Committed: https://git.openstack.org/cgit/openstack/ansible-hardening/commit/?id=f1a52aad91ec94e56d5207c84c61219593d10ad2
Submitter: Zuul
Branch: master

commit f1a52aad91ec94e56d5207c84c61219593d10ad2
Author: Russell Tweed <email address hidden>
Date: Tue Mar 6 21:55:27 2018 +0000

    Add check to ClamAV task to prevent simeltaneous content updates

    Check to see if a freshclam process is already running before kicking off another; attempting a second update will fail if one is already in progress.

    Change-Id: Id5ab344c2408ba64c58612bab33c2ee98aeb97d5
    Closes-Bug: 1730998

Changed in openstack-ansible:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/ansible-hardening 18.0.0.0b1

This issue was fixed in the openstack/ansible-hardening 18.0.0.0b1 development milestone.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.