USER RIGHTS, HUNT GROUPS DELETED FROM CONFIGURATION AFTER MERGE CHANGES 2

[JRTrevino]

ISSUE:
User rights or hunt groups deleted from configuration after merge changes are saved. This is a known Avaya software bug on 9.1, 10.1, and 11.0+ software releases.

*Issue doesn't affect every single client. This appears to occur in Server Edition with multi-site, or IP500v2's in an SCN.

SOLUTION:
You must open an Avaya SR, and provide configuration files, monitor traces etc, and they will provide you with Critical Patch 11.0.4.1.35. The fix will be available with 10.1.0.7.0 and 11.0.4.2 versions when released. The patch will be GA released in the month of November 2019. no specific date was shared. See the attached article from Avaya support.

https://support.avaya.com/ext/index?page=content&a...

IP Office: Server Edition losing User Rights at Solution level
Rate Content Rate this Page
Doc ID: SOLN342732
Version: 6.0
Status: Published
Published date: 20 Aug 2019
Updated: 05 Nov 2019
Author:
Victor Brattsev
Details: A number of User Rights disappear from the SE Solution on a almost daily basis when Manager opened, we can rectify and save but next time Manager opened they can disappear again11.0 FP4The issue was seen twice when the system was being built in our workshop, seems to have gotten worst since equipment moved to site and since upgrading to 11.4.

Problem Clarification: All user rights are disappearing from the system triggered by a config merge (adding users)
This can be seen in the ipoffice_logs_yyyy-mm-dd-hh-mm.tar.gz file - after new user Alice is added, all the user rights are deleting from the configuration

<110> 2019 Jul 3 17:10:52 192.168.42.1 ipoffice: +01:00 2019 000 1 .ipoffice | 0 EXA|AdminChange|Administrator|4...|Alice...||NEW||
<110> 2019 Jul 3 17:10:52 192.168.42.1 ipoffice: +01:00 2019 000 1 .ipoffice | 0 EXA|AdminChange|Administrator|49...|UsRights_1...|||DELETED|
<110> 2019 Jul 3 17:10:52 192.168.42.1 ipoffice: +01:00 2019 000 1 .ipoffice | 0 EXA|AdminChange|Administrator|49...|UsRights_2...|||DELETED|
<110> 2019 Jul 3 17:10:52 192.168.42.1 ipoffice: +01:00 2019 000 1 .ipoffice | 0 EXA|AdminChange|Administrator|49...|UsRights_3...|||DELETED|
<110> 2019 Jul 3 17:10:52 192.168.42.1 ipoffice: +01:00 2019 000 1 .ipoffice | 0 EXA|AdminChange|Administrator|49...|UsRights_4...|||DELETED|
<110> 2019 Jul 3 17:10:52 192.168.42.1 ipoffice: +01:00 2019 000 1 .ipoffice | 0 EXA|AdminChange|Administrator|49...|UsRights_5...|||DELETED|
<110> 2019 Jul 3 17:10:52 192.168.42.1 ipoffice: +01:00 2019 000 1 .ipoffice | 0 EXA|AdminChange|Administrator|49...|UsRights_6...|||DELETED|
<110> 2019 Jul 3 17:10:52 192.168.42.1 ipoffice: +01:00 2019 000 1 .ipoffice | 0 EXA|AdminChange|Administrator|49...|UsRights_7...|||DELETED|
<110> 2019 Jul 3 17:10:52 192.168.42.1 ipoffice: +01:00 2019 000 1 .ipoffice | 0 EXA|AdminChange|Administrator|49...|UsRights_8...|||DELETED|
...
<110> 2019 Jul 3 17:10:52 192.168.42.1 ipoffice: +01:00 2019 000 1 .ipoffice | 0 EXA|AdminChange|Administrator|49...|UsRights_n...|||DELETED|

After the user "Alice" was added and config saved, when reopened, there was a "Consolidation Report" dialog appearing and the customer clicked "Reconsolidate".
Cause: Product Defect IPOFFICE-153111
Solution:
Critical Patch 11.0.4.0.57 Build 3 was released to address this issue.
Fix will be available with 10.1.0.7.0 and 11.0.4.2 versions when released.

 

[NYSTECH]

I just don't understand how Avaya can release software with known bugs and have no quality control. If they know there has been issue since 9.1 why not fix it?

 

[janni78]

The PDF is not valid, can you link the solution notes on Avaya Support site instead?

"Trying is the first step to failure..." - Homer

 

[rgunther]

FIX:
[highlight #FCE94F]You must open an Avaya SR, and provide configuration files, monitor traces etc, and they will provide you with the Release 11.0.4.1 patch. The patch will be GA released in the month of November 2019[/highlight]

I show that Avaya IP Office 11.0 Feature Pack 4 Service Pack 1 General Availability was release on Aug 1, 2019. Can anyone verify the bug has been fixed in this release - or is it another patch for this release?

 

[JRTrevino]

@NYSTECH Right? The thing is that this issue doesn't affect every single client. It appears to me to be affecting lucky clients on Server Edition with multi-site, or IP500v2's in an SCN.

@rgunther Sorry. I will edit that. To be clear, the 11.0.4.1 GA release in August HAS the bug. Critical Patch 11.0.4.0.57 Build 3 was released to address this issue. Fix will be available with 10.1.0.7.0 and 11.0.4.2 versions when released.


@janni78 Sure. I'll do that. Here ya go:

https://support.avaya.com/ext/index?page=content&id=SOLN342732

IP Office: Server Edition losing User Rights at Solution level
Rate Content Rate this Page
Doc ID: SOLN342732
Version: 6.0
Status: Published
Published date: 20 Aug 2019
Updated: 05 Nov 2019
Author:
Victor Brattsev
Details: A number of User Rights disappear from the SE Solution on a almost daily basis when Manager opened, we can rectify and save but next time Manager opened they can disappear again11.0 FP4The issue was seen twice when the system was being built in our workshop, seems to have gotten worst since equipment moved to site and since upgrading to 11.4.

Problem Clarification: All user rights are disappearing from the system triggered by a config merge (adding users)
This can be seen in the ipoffice_logs_yyyy-mm-dd-hh-mm.tar.gz file - after new user Alice is added, all the user rights are deleting from the configuration

<110> 2019 Jul 3 17:10:52 192.168.42.1 ipoffice: +01:00 2019 000 1 .ipoffice | 0 EXA|AdminChange|Administrator|4...|Alice...||NEW||
<110> 2019 Jul 3 17:10:52 192.168.42.1 ipoffice: +01:00 2019 000 1 .ipoffice | 0 EXA|AdminChange|Administrator|49...|UsRights_1...|||DELETED|
<110> 2019 Jul 3 17:10:52 192.168.42.1 ipoffice: +01:00 2019 000 1 .ipoffice | 0 EXA|AdminChange|Administrator|49...|UsRights_2...|||DELETED|
<110> 2019 Jul 3 17:10:52 192.168.42.1 ipoffice: +01:00 2019 000 1 .ipoffice | 0 EXA|AdminChange|Administrator|49...|UsRights_3...|||DELETED|
<110> 2019 Jul 3 17:10:52 192.168.42.1 ipoffice: +01:00 2019 000 1 .ipoffice | 0 EXA|AdminChange|Administrator|49...|UsRights_4...|||DELETED|
<110> 2019 Jul 3 17:10:52 192.168.42.1 ipoffice: +01:00 2019 000 1 .ipoffice | 0 EXA|AdminChange|Administrator|49...|UsRights_5...|||DELETED|
<110> 2019 Jul 3 17:10:52 192.168.42.1 ipoffice: +01:00 2019 000 1 .ipoffice | 0 EXA|AdminChange|Administrator|49...|UsRights_6...|||DELETED|
<110> 2019 Jul 3 17:10:52 192.168.42.1 ipoffice: +01:00 2019 000 1 .ipoffice | 0 EXA|AdminChange|Administrator|49...|UsRights_7...|||DELETED|
<110> 2019 Jul 3 17:10:52 192.168.42.1 ipoffice: +01:00 2019 000 1 .ipoffice | 0 EXA|AdminChange|Administrator|49...|UsRights_8...|||DELETED|
...
<110> 2019 Jul 3 17:10:52 192.168.42.1 ipoffice: +01:00 2019 000 1 .ipoffice | 0 EXA|AdminChange|Administrator|49...|UsRights_n...|||DELETED|

After the user "Alice" was added and config saved, when reopened, there was a "Consolidation Report" dialog appearing and the customer clicked "Reconsolidate".
Cause: Product Defect IPOFFICE-153111
Solution:
Critical Patch 11.0.4.0.57 Build 3 was released to address this issue.
Fix will be available with 10.1.0.7.0 and 11.0.4.2 versions when released.

 

[rgunther]

Thank you JRTrevino -

I am glad to hear this has been addressed as a bug, as I have been experiencing this issue for months now on our 7 site SCN (IP500V2 R10.1.5) and have not had confirmation of a bug until now. Been searching for an answer as almost everytime I make a merge change, my user rights groups are removed from the system.​

I was just about to upgrade to R11, but I think i will wait until the patch is released now. Thank you for the help!