Skip to content

Commit ff10492

Browse files
Aria known issues (vmware#271)
* added operations known issues
1 parent d074f3a commit ff10492

File tree

1 file changed

+27
-1
lines changed

1 file changed

+27
-1
lines changed

aria/operations/8.x/docs/known-issues.md

Lines changed: 27 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,10 @@
55
- [Apache](#apache)
66
- [Casa](#casa)
77
- [Postgres](#postgres)
8+
- [POSTGRES-PROFILE Controls only apply to primary node](#postgres-profile-postgres-controls-only-apply-to-primary-node)
89
- [UI](#ui)
910
- [Photon](#photon)
11+
- [PHTN-40-000073, PHTN-50-000073 Commands in check and fix do not produce expected results](#phtn-40-000073phtn-50-000073-commands-in-check-and-fix-do-not-produce-expected-results)
1012

1113
# Known Issues
1214

@@ -22,6 +24,8 @@ Each known issue links off to an existing GitHub issue. If you have additional q
2224

2325
Please check the [open](https://github.com/vmware/dod-compliance-and-automation/issues) and [closed](https://github.com/vmware/dod-compliance-and-automation/issues?q=is%3Aissue+is%3Aclosed) issues in the issue tracker for the details of your bug. If you can't find it, or if you're not sure, open a new issue.
2426

27+
# Table of contents
28+
2529
## API
2630

2731
## Application
@@ -32,6 +36,28 @@ Please check the [open](https://github.com/vmware/dod-compliance-and-automation/
3236

3337
## Postgres
3438

39+
### [POSTGRES-PROFILE] Postgres controls only apply to primary node
40+
41+
Related issue: none
42+
43+
In a clustered environment, the Postgres controls only need to be applied to the primary node running the replication service. On Data/Replica nodes, that service does not exist.
44+
3545
## UI
3646

37-
## Photon
47+
## Photon
48+
49+
### [PHTN-40-000073,PHTN-50-000073] Commands in check and fix do not produce expected results
50+
51+
Related issue: None
52+
53+
Running commands to check or fix permissions and file ownership on the '/var/log' directory always returns a value of 777, even after attempting to update the permissions.
54+
55+
**Workaround:**
56+
57+
- The '/var/log' entry is a symbolic link to the '/storage/log/var/log' directory, so the check needs to be performed on the underlying directory rather than on the symlink itself. This can be accomplished by any of the following methods:
58+
- Add a trailing slash ("/") to the directory in any commands
59+
- stat -c "..." /var/log/
60+
- chmod 0755 /var/log/
61+
- Use the underlying folder instead
62+
- stat -c "..." /storage/log/var/log
63+
- chmod 0755 /storage/log/var/log

0 commit comments

Comments
 (0)