magnum config-internal missing +x

Bug #1473522 reported by Harm Weites
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Fix Released
High
Harm Weites

Bug Description

Without +x on the Magnum config-internal.sh scripts, the containers will not run.

Harm Weites (harmw)
Changed in kolla:
assignee: nobody → Harm Weites (harmw)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kolla (master)

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

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

Reviewed: https://review.openstack.org/200645
Committed: https://git.openstack.org/cgit/stackforge/kolla/commit/?id=ea14f2286680ee4e0b7abe58e8d86a0023a2eee9
Submitter: Jenkins
Branch: master

commit ea14f2286680ee4e0b7abe58e8d86a0023a2eee9
Author: Harm Weites <email address hidden>
Date: Fri Jul 10 20:02:20 2015 +0200

    Add +x to Magnum's config-internal.sh scripts

    Change-Id: Ie58fa5474d63d4cabfd1cdcda7781da364fae5cc
    Closes-bug: #1473522

Changed in kolla:
status: In Progress → Fix Committed
Steven Dake (sdake)
Changed in kolla:
milestone: none → liberty-rc1
importance: Undecided → High
Sam Yaple (s8m)
Changed in kolla:
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.