A centralmanagement bundle register the pscheduler service to global LS

After a plain yum install perfsonar-centralmanagement the ls-registration-daemon is registering a pscheduler service to the global LS, although none is running.

2019/09/13 19:34:34 (3532) DEBUG> TCP_Service.pm:79 perfSONAR_PS::LSRegistrationDaemon::Services::TCP_Service::is_up - Connecting to pScheduler server: 192.168.1.186:443
2019/09/13 19:34:34 (3532) DEBUG> Base.pm:339 perfSONAR_PS::LSRegistrationDaemon::Base::bulk_refresh - Service is up
2019/09/13 19:34:34 (3532) DEBUG> Base.pm:341 perfSONAR_PS::LSRegistrationDaemon::Base::bulk_refresh - Current reg statusREGISTERED
2019/09/13 19:34:34 (3532) DEBUG> Base.pm:723 perfSONAR_PS::LSRegistrationDaemon::Base::build_checksum - Checksum prior to md5 is service::https://192.168.1.186/pschedulerpschedulerpSchedulerpscheduler-1.0lookup/host/7cb9cde8-7836-4af6-a381-2cd2e0266a3fdelvaux.net,mam.delvaux.net03688938-D65C-11E9-96F2-BB2516FB79C2
2019/09/13 19:34:34 (3532) DEBUG> Base.pm:728 perfSONAR_PS::LSRegistrationDaemon::Base::build_checksum - Checksum is VinIcJNQb4/+5jqo4hnUjQ
2019/09/13 19:34:34 (3532) DEBUG> Base.pm:610 perfSONAR_PS::LSRegistrationDaemon::Base::find_key - Found key lookup/service/99dff64a-508f-42d2-b9ab-7e1ba72785d4 with VinIcJNQb4/+5jqo4hnUjQ for pScheduler that expires 1568407103
2019/09/13 19:34:34 (3532) INFO> Base.pm:358 perfSONAR_PS::LSRegistrationDaemon::Base::bulk_refresh - Record is up, adding registration to refresh list(key=lookup/service/99dff64a-508f-42d2-b9ab-7e1ba72785d4, description=pScheduler)

Content in global LS:

[
{
"expires": "2019-09-13T21:34:37.015Z",
"psservice-eventtypes": [],
"service-type": [
"ma"
],
"service-version": [
"esmond-2.0"
],
"type": [
"service"
],
"uri": "lookup/service/a4afd8fa-e21b-452f-91fc-d7fc25aa622d",
"service-host": [
"lookup/host/7cb9cde8-7836-4af6-a381-2cd2e0266a3f"
],
"service-name": [
"Measurement Archive"
],
"client-uuid": [
"03688938-D65C-11E9-96F2-BB2516FB79C2"
],
"group-domains": [
"mam.delvaux.net",
"delvaux.net"
],
"state": "renewed",
"service-administrators": [
""
],
"service-locator": [
"http://192.168.1.186/esmond/perfsonar/archive",
"https://192.168.1.186/esmond/perfsonar/archive"
],
"ttl": []
},
{
"expires": "2019-09-13T21:34:37.017Z",
"service-type": [
"pscheduler"
],
"service-version": [
"pscheduler-1.0"
],
"type": [
"service"
],
"uri": "lookup/service/99dff64a-508f-42d2-b9ab-7e1ba72785d4",
"service-host": [
"lookup/host/7cb9cde8-7836-4af6-a381-2cd2e0266a3f"
],
"service-name": [
"pScheduler"
],
"client-uuid": [
"03688938-D65C-11E9-96F2-BB2516FB79C2"
],
"group-domains": [
"mam.delvaux.net",
"delvaux.net"
],
"state": "renewed",
"service-administrators": [
""
],
"service-locator": [
"https://192.168.1.186/pscheduler"
],
"ttl": []
}
]

I guess the ls-reg-daemon is only checking if it can establish a connexion on port 443.

perfsonar / ls-registration-daemon

A centralmanagement bundle register the pscheduler service to global LS #61