- **status**: assigned --> invalid
- **assigned_to**: Canh Truong --> nobody
- **Blocker**: --> False
- **Comment**:
The user has to make sure that the group name and group id are created the same
in both node
---
** [tickets:#1730] LOG: group ownership of log file is not correct after
- **Milestone**: 4.6.2 --> 4.7.2
---
** [tickets:#1730] LOG: group ownership of log file is not correct after
failover**
**Status:** assigned
**Milestone:** 4.7.2
**Created:** Wed Apr 06, 2016 09:16 AM UTC by Quyen Dao
**Last Updated:** Thu Apr 21, 2016 04:44 AM UTC
**Owner:** Canh Truong
The reason of this issue is the group id and group name between ACTIVE node and
STANDBY node is not compatible. In above step (step 1, 2), test_data_group_1
have group id 1001 in ACTIVE SC. but in STANBY SC, group id of name
"test_data_group_1" is 1002, while 1001 is id of "test_data_group_2".
In current design, the group change at "new active" node just takes effective
when getting an write action, otherwise the log file permission still remains.
As above case, the group was not changed to file
"saLogNotification_20160323_135207.log" because no write action to that file
took place.
---
** [tickets:#1730] LOG: group ownership of log file is not correct after
failover**
**Status:** unassigned
**Milestone:** 4.6.2
**Created:** Wed Apr 06, 2016 09:16 AM UTC by Quyen Dao
**Last Updated:** Wed Apr 06, 2016 09:16 AM UTC
**Owner:** nobody
*Steps to reproduce*
1. Create
