CA Install Script overwrites admin and engage url config keys

Steps to reproduce

Steps to reproduce:
1. On a fresh system, install a capture agent as described at https://opencast.jira.com/wiki/display/mh14/Install+Capture+Agent
2. At prompts, accept default responses except for admin server url. (Therefore, engage url will default to same response as admin url)
3. Once installation is complete, view contents of config.properties

Actual Results:
The following is an excerpt from my install. Note that "org.opencast.serviceregistry.url" appears three times:

  1. The url of the remote service registry. This is used in cases where there is no direct connection to the service

  2. registry database such as capture agens running in protected environments. This is typically true for capture agents

  3. and should be set to the url of a server running the actual implementation of the service registry and the path to

  4. the service registry(admin, worker, etc. See the build profiles in pom.xml for a complete list).
    org.opencastproject.serviceregistry.url=http://10.8.49.5:8080/services

  1. The base URL of the server hosting the administrative tools. If the admin tools are deployed on this server,

  2. this should point to this server's public URL.
    org.opencastproject.serviceregistry.url=http://10.8.49.5:8080

  1. The base URL of the server hosting the engage tools. If the engage tools are deployed on this server, this

  2. should point to this server's public URL.
    org.opencastproject.serviceregistry.url=http://10.8.49.5:8080

Expected Results:
Two instances of "#org.opencastproject.serviceregistry.url" should be "#org.opencastproject.admin.ui.url" and "#org.opencastproject.engage.ui.url", respectively.

Workaround (if any):
Manually replace the admin and engage config keys.

Status

Assignee

Greg Logan

Reporter

Jonathan Lee

Severity

Usability Issue

Tags (folksonomy)

None

Components

Fix versions

Affects versions

1.4.0

Priority

Critical