Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
oveits opened this issue Nov 6, 2016 · 1 comment

Comments

@oveits
Copy link
Owner

oveits commented Nov 6, 2016

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
Copy link
Owner Author

oveits commented Nov 6, 2016

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant