[JIRA] Updated: (SSPCPP-517) Windows SP installer should not always roll back when shibd fails to start

[Rod Widdowson (JIRA)]

     [ https://issues.shibboleth.net/jira/browse/SSPCPP-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rod Widdowson updated SSPCPP-517:
---------------------------------

    Original Estimate: 4 hours

 I have looked a bit at this, work is ongoing.

My initial assumption was that it would suffice to tell the service starting mechanism to not wait for the service to start and off we would go.
Sadly this did not work in my case (in which I had managed to build a shibd.exe but not shibsp.dll).

The next idea was to look at surpressing exactly rollback.  This does more of what you would expect it does not roll back the installation and so you can poke at shibd.exe -t and see whats up.

But it actually leaves the SP not installed (in the msi sense of the word).  The executables are all there, the service is registered, the world is good.   But the installed does not believe that it is installed.  The overweening temptation will be to make it work and move on, leaving a pseudop-install in place.  So I think that stopping "Rollback" in the MSI sense is a really bad idea.

I need to poke at this a bit further (since wait seems to be what we want), but my feeling right now is that we may need to circumvent the automatic starting and use something else)

> Windows SP installer should not always roll back when shibd fails to start
> --------------------------------------------------------------------------
>
>                 Key: SSPCPP-517
>                 URL: https://issues.shibboleth.net/jira/browse/SSPCPP-517
>             Project: Shibboleth SP - C++
>          Issue Type: Improvement
>          Components: Installation / Packaging
>    Affects Versions: 2.5.0
>            Reporter: Elliot Kendall
>            Assignee: Rod Widdowson
>            Priority: Minor
>             Fix For: 2.5.1
>
>   Original Estimate: 4 hours
>          Time Spent: 1 hour
>  Remaining Estimate: 3 hours
>
> The SP Windows installer currently installs the software, tries to start shibd, and then removes the software if shibd does not start. Troubleshooting the reason that shibd did not start generally requires that the SP software be installed, however.
> Either disable the rollback functionality completely, or provide an option (GUI or command line) to let the user disable it.
> See also:
> http://marc.info/?l=shibboleth-users&m=135057653113392
> https://issues.shibboleth.net/jira/browse/SSPCPP-499

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira