[KNOX-2693] When topology is updated twice consecutively with 275ms delay then redeployed topology doesnt have 2nd updates

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.3.0
• Fix Version/s: 2.0.0
• Assignee: Sandor Molnar
• Reporter: J.Andreina
• Created: 29/Nov/21 11:46
• Updated: 17/Jan/22 07:38
• Resolved: 17/Jan/22 07:38

Description

ENV:

Have a custom topology_1.xml with below provider 

      <provider>
         <role>authorization</role>
         <name>CompositeAuthz</name>
         <enabled>true</enabled>
         <param>
            <name>AclsAuthz.atlas-api.acl</name>
            <value>user1;group1;10.10.10.10</value>
         </param> 
      </provider>

Steps:
1. Replace acl "user1" value to "guest" using sed
sed -i -e 's#user1#guest#g' topology_1.xml

2. Within 250 ms issue another sed command to replace acl "group1" value to "analyst"
sed -i -e 's#group1#analyst#g' topology_1.xml

Issue:

After 5 mins redeployed topology_1.xml still have "group1" as acl value instead of having analyst.

Issue Links

• links to: GitHub Pull Request #531