Closed tochi-y closed 5 years ago
Elastic search data:
{
"_index": "u0_ad.cell",
"_type": "_doc",
"_id": "O9q7ILXOSAWDSjl-WSr4Gg",
"_version": 1,
"_score": 1,
"_routing": "pcsCell",
"_source": {
"p": 1568187671899,
"a": {},
"b": null,
"s": {
"Name": "unitadmin"
},
"c": null,
"t": null,
"d": {},
"u": 1568187671899,
"h": {
"Owner": "personium-localunit:/unitadmin/#unitadmin"
},
"l": {},
"n": null,
"type": "Cell"
}
}
Data in the elasticsearch are different between unitadmin and the cell created by UnitManager.
personium-localunit:/unitadmin/#unitadmin
personium-localunit:unitadmin/#unitadmin
In v1.7.18, the Owner data should be stored as personium-localunit:{cellname}/
. But the shellscript called from the ansible playbook gives a parameter as personium-localunit:/{cellname}
.
So it is not a personium-core problem. The shellscript should be fixed.
I closed this issue and created the following issue. https://github.com/personium/ansible/issues/109
After deploying a personium unit v1.7.18b using ansible playbook, UnitManager cannot display cells.
But the same personium unit replaced with v1.7.17, the unitadmin cell is normally displayed with the UnitManager. Is this a personium-core v1.7.18b bug? And is this related with #479?
There are differences between v1.7.17 and v1.7.18b in calling APIs as followings.
v.1.7.17
GET
https://personium.example/__ctl/Cell?$top=500&$orderby=__updated%20desc
GET
https://personium.example/__ctl/Cell?$top=0&$inlinecount=allpages
v.1.7.18
GET
https://personium.example/__ctl/Cell?$top=500&$orderby=__updated%20desc
GET
https://personium.example/__ctl/Cell?$top=0&$inlinecount=allpages