Bug 1399146
Summary: | Installation fails with more restrictive, system-wide umask setting. | |||
---|---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Rafal Szmigiel <rszmigie> | |
Component: | openstack-puppet-modules | Assignee: | Emilien Macchi <emacchi> | |
Status: | CLOSED ERRATA | QA Contact: | Gurenko Alex <agurenko> | |
Severity: | medium | Docs Contact: | ||
Priority: | medium | |||
Version: | 9.0 (Mitaka) | CC: | aschultz, jguiditt, ohochman, rszmigie, srevivo, ssmolyak | |
Target Milestone: | --- | Keywords: | Triaged, ZStream | |
Target Release: | 9.0 (Mitaka) | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | openstack-puppet-modules-8.1.13-1.el7ost | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1428119 1431664 (view as bug list) | Environment: | ||
Last Closed: | 2017-06-19 14:49:02 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: |
Description
Rafal Szmigiel
2016-11-28 12:17:46 UTC
Fixed in OSP11, do we want to fix it in OSP10 and 9? Hi, If that wouldn't be a big problem then yes please. I know at least one customer who was affected by this using OSP10. Thanks in advance, Rafal [stack@undercloud-0 ~]$ cat /etc/yum.repos.d/latest-installed 9 -p 2017-03-17.1 [stack@undercloud-0 ~]$ rpm -q openstack-puppet-modules openstack-puppet-modules-8.1.13-1.el7ost.noarch [stack@undercloud-0 ~]$ ll /var/www/cgi-bin/keystone/ total 8 -rw-r--r--. 1 keystone keystone 1162 Mar 28 07:37 keystone-admin -rw-r--r--. 1 keystone keystone 1167 Mar 28 07:37 keystone-public [stack@undercloud-0 ~]$ ll /var/www/cgi-bin/ total 0 drwxr-xr-x. 2 aodh aodh 17 Mar 28 07:37 aodh drwxr-xr-x. 2 keystone keystone 51 Mar 28 07:37 keystone 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. https://access.redhat.com/errata/RHBA-2017:1501 |