os-apply-config doesn't preserve permissions and ownership

Bug #1246266 reported by Tomas Sedovic
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
os-apply-config
Fix Released
High
Tomas Sedovic

Bug Description

It's sometimes necessary for a config file to have specific owner or permissions (e.g. Horizon's .secret_key_store has to be 600 and owned by horizon).

If the file already exists (e.g. because it was created in install.d), os-apply-config should preserve its permission and ownership. Righ now always sets it to 644 and root.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to os-apply-config (master)

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

Changed in os-apply-config:
assignee: nobody → Tomas Sedovic (tsedovic)
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to os-apply-config (master)

Reviewed: https://review.openstack.org/54708
Committed: http://github.com/openstack/os-apply-config/commit/086b6b155125c1da9a802a73b596b7fc13ba49c2
Submitter: Jenkins
Branch: master

commit 086b6b155125c1da9a802a73b596b7fc13ba49c2
Author: Tomas Sedovic <email address hidden>
Date: Thu Oct 31 11:26:10 2013 +0100

    Respect the preset permissions of config files

    It's sometimes desirable to specify the permissions or ownership of the
    generated config file instead of setting the default 644 root:root.

    If the file is already present, os-apply-config will just update the
    contents and leave everything else alone.

    Closes-Bug: #1246266
    Change-Id: Idd41ec276dd04f517760c1dbd97c75e376840b41

Changed in os-apply-config:
status: In Progress → Fix Committed
Changed in os-apply-config:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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