Publish LiveSite Content workflow stalled at "Resolve Production Deployment error" task (16.4/Linux)

BigBruv

Hello,
I’ve just made a new TeamSite16.4 installation which I thought was sound, but am failing at the last hurdle – trying to run the Publish LiveSite Content (to Prod) workflow. When run from CCPro it stalls on "Resolve Production Deployment error" task, and nothing is deployed.

I do get OpenDeploy lscs logs produced, but not seeing anything very indicative to me (see later).

I have already made appropriate changes for host, webservice port (9273) and deployment target directory variously in odbase.xml, cssdk.cfg, DataSourceConfig.xml, opendeploy.properties & LCSSAuth/../deployment-source.properties, and I've 775’ed the target dir.

But I think I must be missing some other configuration I need to make. Does anyone have any ideas???

Cheers
BB

Messages written in logs (x3) at the time of failure are:

1. In src.teamsite-areadiff4960899e2277ccc05568b13371917bba.MYDEFINITIONNAME.localhost.to.LSCSRuntime.log
   LIB: 2018-08-28 16:15:01 COMMITTING Transactional Deployment
   LIB: 2018-08-28 16:15:02 Receiver-ERROR: ERROR: commit-failed.
   LIB: 2018-08-28 16:15:02 ERROR: Failed to deploy local_directory[.] of area[/opt/teamsite/iw-home/LiveSiteCSAuth/authoring/tmp/4960899e2277ccc05568b13371917bba/payload] for filelist[/opt/teamsite/iw-home/LiveSiteCSAuth/authoring/tmp/4960899e2277ccc05568b13371917bba/filelist/lscs.filelist]
   LIB: 2018-08-28 16:15:02 ERROR: Failed 1 of 1 filelists

2. In rcv.teamsite-areadiff4960899e2277ccc05568b13371917bba.MYDEFINITIONNAME.localhost.to.LSCSRuntime.log
   LIB: 2018-08-28 16:15:02 ERROR: commit-failed.
   LIB: 2018-08-28 16:15:02 ERROR: Failed deploying filelist[0]
   LIB: 2018-08-28 16:15:02 ERROR: Failed 1 of 1 filelists

3. [Runtime]/LiveSiteCSRT/log/lscs.log
   08-28-18 @ 16:15:01 [INFO ] UtilCommandRequestHandler - No pending context found for project : //localhost/default/main/component-guide
   08-28-18 @ 16:15:01 [INFO ] ImportRequestHandler - Starting import.
   08-28-18 @ 16:15:02 [INFO ] SolrSearchDaoRuntimeImpl - Deleting Solr collection 859365312...
   08-28-18 @ 16:15:02 [INFO ] SolrServiceImpl - Deleting solr collection :859365312
   08-28-18 @ 16:15:02 [ERROR] SolrServiceImpl - Failed to delete solr collection: 859365312
   ....
   08-28-18 @ 16:15:02 [INFO ] UtilCommandRequestHandler - Beginning rollback of context: 4960899e2277ccc05568b13371917bba
   08-28-18 @ 16:15:02 [INFO ] AssetDaoHibernateImpl - handleContextRollback
   08-28-18 @ 16:15:02 [INFO ] SolrSearchDaoRuntimeImpl - Rollback index from Solr collection null...
   08-28-18 @ 16:15:02 [WARN ] SolrSearchDaoRuntimeImpl - updateAssets(): collectionName is null.
   08-28-18 @ 16:15:02 [INFO ] SolrSearchDaoRuntimeImpl - Done rollback index from Solr collection null
   08-28-18 @ 16:15:02 [INFO ] UtilCommandRequestHandler - Rollback completed.

tsp3

@BigBruv seems like your problem might be with deployment on LSDS side. Are you sure that the path for lsds is correct?

nipper

To me it looks like the issue is LSCS deployment.

I tend to use startdeploy.sh to test out the deployments before I work with the PLC.

The import failed and then it tried to roll back.

There is an undocumented step in the configuration of LSCS, you have to create the collection in SOLR to use it:

curl http://localhost:1876/lscs/v1/admin/upload-configset

This should return a JSON response with success/failure (if failure there should be an error message).

Note: LiveSite Runtime install guide needs to be updated to run above command to upload lscs configset as a manual post install task. This has been filed as WCM-12095 - 'Upload lscs configsets as post install task for LSCSRuntime install'

To verify that the configset has been uploaded to zookeeper navigate to one of the solr instances in the solr cloud and navigate to cloud tab and tree view. Here expand the configs folder and you should see the uploaded configset
curl http://runtime-ip:8983/solr/#/~cloud?view=tree

BigBruv

Hi
@tsp3 ,
I have set the lsds path as follows:
odbase.xml: < path name="/usr/Interwoven/LiveSiteDisplayServices/runtime/web"/>
opendeploy.properties: opendeploy.runtimeHome=/usr/Interwoven/LiveSiteDisplayServices/runtime/web

@Andy Knipp ,
http://[ip]:1876/lscs/v1/admin/upload-configset gives me "Success".

Working through this.
Cheers
BB

BigBruv

An update, this is solved now. @tsp3 was right. I had made changes for the target path, port and host in all the config files listed in the OP, BUT I had neglected to run build.sh to incorporate the important lsds path change in opendeploy.properties. And now the Publish Livesite Content workflow works for both eStudio & CCPro. Thank you both for your help.
Rgds
BB