Valid service could not be detected at {URI=https://192.168.122.89:443/redfish/v1, type=RMM

[deeptidrut]

Hi,
We have the following redfish APIs exposed in BMC.

curl -b cjar -k https://${bmc}/redfish/v1
{
"@odata.context": "/redfish/v1/$metadata#ServiceRoot.ServiceRoot",
"@odata.id": "/redfish/v1",
"@odata.type": "#ServiceRoot.v1_1_1.ServiceRoot",
"AccountService": {
"@odata.id": "/redfish/v1/AccountService"
},
"Chassis": {
"@odata.id": "/redfish/v1/Chassis"
},
"Id": "RootService",
"JsonSchemas": {
"@odata.id": "/redfish/v1/JsonSchemas"
},
"Links": {
"Sessions": {
"@odata.id": "/redfish/v1/SessionService/Sessions"
}
},
"Managers": {
"@odata.id": "/redfish/v1/Managers"
},
"Name": "Root Service",
"RedfishVersion": "1.6.1",
"Registries": {
"@odata.id": "/redfish/v1/Registries"
},
"SessionService": {
"@odata.id": "/redfish/v1/SessionService"
},
"Systems": {
"@odata.id": "/redfish/v1/Systems"
},
"UUID": "93328078-563b-494c-9bf4-f714c52a5039",
"UpdateService": {
"@odata.id": "/redfish/v1/UpdateService"
}

We are trying to get this BMC detected in Pod-Manager
using configuration in

instance-1:/etc/pod-manager$ cat /tmp/services.list
https://192.168.122.89:443/redfish/v1/ psme
instance-1:/etc/pod-manager$

However when we try to get Manager info using Pod-Manager API, we are getting the below error:
2019-04-04 10:30:59,808 [EE-ManagedScheduledExecutorService-default-Thread-2] ERROR c.i.p.s.d.d.ServiceEndpointsProcessor - Valid service could not be detected at {URI=https://192.168.122.89:443/redfish/v1, type=PSME, updateDate=null}, retry no 1.

Can you please help resolve this?

Many Thanks,
Deepti

[deeptidrut]

This is not yet resolved.. Can someone please help?

[deeptidrut]

Further debugged and found thsi error:

select endpoint0_.id as id2_31_, endpoint0_1_.event_source_context as event_so3_31_, endpoint0_1_.version as version4_31_, endpoint0_1_.description as descript5_31_, endpoint0_1_.global_id as global_i6_31_, endpoint0_1_.is_complementary as is_compl7_31_, endpoint0_1_.name as name8_31_, endpoint0_1_.status as status9_31_, endpoint0_.endpoint_authentication_password as endpoint1_38_, endpoint0_.endpoint_authentication_username as endpoint2_38_, endpoint0_.composed_node_id as compose11_38_, endpoint0_.computer_system_id as compute12_38_, endpoint0_.entity_id as entity_i3_38_, endpoint0_.fabric_id as fabric_13_38_, endpoint0_.host_reservation_memory_bytes as host_res4_38_, endpoint0_.endpoint_metadata_id as endpoin14_38_, endpoint0_.device_id as device_i5_38_, endpoint0_.subsystem_id as subsyste6_38_, endpoint0_.subsystem_vendor_id as subsyste7_38_, endpoint0_.vendor_id as vendor_i8_38_, endpoint0_.processor_id as process15_38_, endpoint0_.endpoint_protocol as endpoint9_38_, endpoint0_.storage_service_id as storage16_38_, endpoint0_.zone_id as zone_id17_38_ from endpoint endpoint0_ inner join discoverable_entity endpoint0_1_ on endpoint0_.id=endpoint0_1_.id inner join endpoint_identifier identifier1_ on endpoint0_.id=identifier1_.endpoint_id where identifier1_.durable_name like ('%'||$1||'%')
2019-04-15 09:33:52 UTC [11429-1] podm@podm ERROR: operator does not exist: text ~~ bytea at character 1291

Can anyone help resolve the error?