Bug 1439619
| Summary: | Audit configuration issues | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Marko Myllynen <myllynen> |
| Component: | Installer | Assignee: | Giuseppe Scrivano <gscrivan> |
| Status: | CLOSED ERRATA | QA Contact: | Gaoyun Pei <gpei> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.4.1 | CC: | aos-bugs, gpei, jialiu, jokerman, knakayam, mmccomas, tlarsson |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: |
undefined
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-08-10 05:20: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
Marko Myllynen
2017-04-06 10:27:28 UTC
Had this issue as well in 3.3/3.4, I had to change to Enabled to get it working. However a coworker used "basicAuditEnabled" and that worked fine for him. Verify this bug with openshift-ansible-3.6.68-1.git.0.9cbe2b7.el7.noarch.rpm
[root@gpei-test-ansible installer-master]# grep "openshift_master_audit_config" /usr/share/doc/openshift-ansible-docs-3.6.68/docs/example-inventories/*
/usr/share/doc/openshift-ansible-docs-3.6.68/docs/example-inventories/hosts.origin.example:#openshift_master_audit_config={"enabled": true}
/usr/share/doc/openshift-ansible-docs-3.6.68/docs/example-inventories/hosts.ose.example:#openshift_master_audit_config={"enabled": true}
When set openshift_master_audit_config={"enabled": true} in ansible inventory file for ha master env installation, all masters would have the following options configured in /etc/origin/master/master-config.yaml
auditConfig:
enabled: true
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/RHEA-2017:1716 |