Bugzilla – Bug 821
Deployment to non-default server takes 2x the time
Last modified: 2011-06-03 09:33:22 UTC
DETAILED DESCRIPTION: Deploy a configuration to a server that is not the default server listed in the Identity Vaut. The deploy makes all non-server specific modification on the default server, but the server specific data must wait for the objects to synchronize from the default server to that target server. BUILD NUMBER: Oses/CONFIG: STEPS TO REPRO: RESULTS: EXPECTED: WORKAROUNDS: Set the default server in the Identity vault to the DirXML server you are trying to deploy the DirXML configuration to. CUSTOMER IMPACT: NTS entered defects should also include: Additional debug info like screenshots, screencams, log files, trace files, packet traces, memory coredump location. Accurate customer information so that proper prioritizing of the defect is possible (mainly for NTS defects)
Marking resolve later.
Reopening bugs for determination of fixing bug or adding enhancements for Milestone 1.1. Bill
Will not get to for 1.1, marking resolve later.
Reopening resolved/later bugs and changing to assigned/future. Resolved/later is being removed from bugzilla.
marking assigned.
Marking fixed. There has been a lot of work in 3.0 M2 for deploying to non-default servers. This bug was originally opened in 2005.
I believe this was fixed with bug 337280.