Bug 978556 - chmod error on "ocal secret token"
Summary: chmod error on "ocal secret token"
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: foreman
Version: 3.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: async
: 3.0
Assignee: Jordan OMara
QA Contact: Ami Jeain
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-26 19:25 UTC by Jordan OMara
Modified: 2015-06-04 21:52 UTC (History)
8 users (show)

Fixed In Version: ruby193-foreman-1.1.10009-4.el6ost
Doc Type: Bug Fix
Doc Text:
The Foreman package specification previously attempted to modify the permissions of a non-existent file, "ocal_secret_token.rb". This resulted in an error message being displayed but no further negative consequences for the installation. The Foreman package specification has been updated to modify the permissions of the correct file, "local_secret_token.rb".
Clone Of:
Environment:
Last Closed: 2013-07-10 15:42:03 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:1020 0 normal SHIPPED_LIVE Red Hat OpenStack 3.0 bug fix advisory 2013-07-10 19:40:46 UTC

Description Jordan OMara 2013-06-26 19:25:24 UTC 
Foreman spec sets permissions on a non-existant file (typo) "ocal_secret_token.rb". This is erroneous, but does not cause issues for the installation

The correct file is named "local_secret_token.rb"
Comment 2 Ami Jeain 2013-07-07 11:43:25 UTC 
how do I verify this chmod error?
Any foreman documentation that I can look at?
Comment 3 Jordan OMara 2013-07-08 20:56:09 UTC 
Verified "ocal_secret_token" issue not present on install of pkg ruby193-foreman-1.1.10009-4.el6ost
Comment 5 errata-xmlrpc 2013-07-10 15:42:03 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1020.html
Note You need to log in before you can comment on or make changes to this bug.