kolla

/etc/hostname has wrong selinux context

Bug #1568047 reported by Steven Dake
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Fix Released
Low
Paul Belanger
kolla newton-1 "n1"
Mitaka
Fix Released
Low
Paul Belanger
kolla mitaka-rc4 "mitaka-rc4"
Steven Dake (sdake)
Changed in kolla:
status: New → Confirmed
importance: Undecided → Low
milestone: none → newton-1
assignee: nobody → Paul Belanger (pabelanger)
OpenStack Infra (hudson-openstack)
Changed in kolla:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla (master)

Reviewed: https://review.openstack.org/303414
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=84a0f2dd5bb537bcae92c172fcf1bc42d266ec5c
Submitter: Jenkins
Branch: master

commit 84a0f2dd5bb537bcae92c172fcf1bc42d266ec5c
Author: Paul Belanger <email address hidden>
Date: Fri Apr 8 09:13:52 2016 -0400

    Make sure /etc/hostname is valid for SELinux

    In the gate, it is possible for /etc/hostname to not have a valid
    SELinux security conext. So, reset them to default before we update
    the hostname to avoid:

      TASK: [Assign hostname]
      failed: [node1] => {"failed": true}
      msg: Command failed rc=1, out=, err=Could not set property: Access
      denied

    Closes-Bug: #1568047
    Change-Id: Ie30c8437b310d1ea5bc75307375c255131dfe934
    Needed-By: I2ff5fbb315832b8cf07c93d0dd0cdaacd958631e

Changed in kolla:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla (stable/mitaka)

Reviewed: https://review.openstack.org/304948
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=cbe3a15a8e53f600d519a17d7eabab1f7d96e2ab
Submitter: Jenkins
Branch: stable/mitaka

commit cbe3a15a8e53f600d519a17d7eabab1f7d96e2ab
Author: Paul Belanger <email address hidden>
Date: Fri Apr 8 09:13:52 2016 -0400

    Make sure /etc/hostname is valid for SELinux

    In the gate, it is possible for /etc/hostname to not have a valid
    SELinux security conext. So, reset them to default before we update
    the hostname to avoid:

      TASK: [Assign hostname]
      failed: [node1] => {"failed": true}
      msg: Command failed rc=1, out=, err=Could not set property: Access
      denied

    Closes-Bug: #1568047
    Change-Id: Ie30c8437b310d1ea5bc75307375c255131dfe934
    Needed-By: I2ff5fbb315832b8cf07c93d0dd0cdaacd958631e
    (cherry picked from commit 84a0f2dd5bb537bcae92c172fcf1bc42d266ec5c)

Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote : Fix included in openstack/kolla 2.0.0.0rc4

This issue was fixed in the openstack/kolla 2.0.0.0rc4 release candidate.

Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/kolla 2.0.0

This issue was fixed in the openstack/kolla 2.0.0 release.

Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/kolla 1.1.0

This issue was fixed in the openstack/kolla 1.1.0 release.

Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/kolla 3.0.0.0b1

This issue was fixed in the openstack/kolla 3.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.