Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 2.0.2
-
Fix Version/s: 2.0.2
-
Component/s: None
-
Labels:None
-
Environment:
QA Server
Builds:
SAPI - OMS-2.0.2-Prod - Build 23
UI 2.0.2 - Build 34
Core - Trunk Build 772
BidMgr/Listener - Trunk Build 797
-
Sprint:Sprint 3 - 2.0.2
Description
Steps:
1. Log into Reseller UI, create a valid merchant and order associated to it.
2. Deploy the order and ensure that deployment was successful (state of order is now deployed).
3. Now, using change-order-state.groovy script, change the status of order to paused (CANCELLED).
groovy change-order-state.groovy -ah http://aq-qa-tomcat1:8080/sapi/rest/ -uuid 1b237d63-ac6b-491a-8589-29f7d65f2cec -s CANCELLED -ru reseller1@thesearchagency.com
4. After successful execution of groovy script, ensure that the status of order in UI is "Paused".
5. Observe the /tsa-admax-jmslistener.log and check for seupdate to run once the processing has finished.
Expected:
Once the processing of campaigns is finished (ie. obtained SUCCEEDED for the campaigns), seupdate must be automatically run.
Actual:
After successful processing of the campaigns, seupdate is not run. Also, observed the following in log file.
2013-02-22 07:18:47.186 (3) [pool-3-thread-4]: 8ee2247d-cacc-4283-8853-ae7ce635409e has 0 campaigns for a SE Update accounts sync.
2013-02-22 07:18:47.186 (3) [pool-3-thread-4]: 8ee2247d-cacc-4283-8853-ae7ce635409e has 0 campaigns for a SE Update groups-listings sync.
Please find the log attached.
