search

oveits / ProvisioningEngine

Ruby on Rails based ProvisioningEngine Frontend for provisioning of legacy systems via Apache Camel Backend (SOAP/XML+SPML+File import)
3 stars 6 forks source link

Site with duplicate name is synchronized with wrong variables read from other site (seen in simulation mode) #63

Open oveits opened 7 years ago

oveits commented 7 years ago

Seen on Heroku in foreground simulation mode:

I have provisioned Site1 on a new customer (named Cust_2016_11_06) with random data like office code etc.

Then I get a status "provisioning successful (synchronized all parameters)" immediately. When checking the data, I can see, that Site1 has been synchronized with wrong date from Site1 of another customer (named OllisCust4).

The provisioning task is (found on https://provisioningengine.herokuapp.com/provisionings/78) shows following action

action=Add Site, customerName=Cust_2016_11_06, SiteName=Site1, SC=, GatewayIP=, CC=49, AC=473, LOC=9348, XLen=5, EndpointDefaultHomeDnXtension=10000, please_do_not_change_the_next_line = true, OSVIP = 1.1.1.1

and status

stopped with ERROR[100]="Site Name "ExampleSite" exists already in the data base (Numbering Plan = NP_Site1_00010)!" at 2016-11-06 11:59:14 +0000
oveits commented 7 years ago

Questions:

  1. why do we see Site Name "ExampleSite" in simulation mode?
  2. why does the provisioning task error not lead to an errored status of the corresponding object?
  3. why is the back synchronization choosing a wrong source site?