Fix bug in package-listing start script 07/15207/1
authorAndrew Grimberg <agrimberg@linuxfoundation.org>
Thu, 4 Apr 2019 22:39:32 +0000 (15:39 -0700)
committerAndrew Grimberg <agrimberg@linuxfoundation.org>
Thu, 4 Apr 2019 22:39:32 +0000 (15:39 -0700)
commite7d59ac2d68762d6cb6051ef9f828aae4547d1ed
tree2c2559c77d72588945b7dfc8dc9c31448cc428e2
parent84ae8c5aae88cdf9bf4903900da7b6f5c6398582
Fix bug in package-listing start script

Change af89ef784234e7b89984d5b2995fc6d29b6d8c34 introduced a bug where
we don't make sure that the package-listing.sh script is executable
before calling it during system startup. This means that we are no
longer currently producing the needed listing start file for instances
to be able to diff against to give us a view of package changes.

Change-Id: Iea2f0b07cdf10f7819072bcb00596bdeda4665df
Signed-off-by: Andrew Grimberg <agrimberg@linuxfoundation.org>
jenkins-init-scripts/package-listing.sh