The problem occurs when I go through the web interface and am presented with the "Select update" dialog. The campaigner returns a 500 error. The error dialog then says:
No updates found. Create some updates first.
This part is identical to advancedtelematic/campaigner#133. The workaround is to use the REST APIs to create a campaign. However, this just "moves" the problem to another location. Now, when the client requests the list of available campaigns, it gets:
GET https://ota.ce:30443/campaigner/campaigns
Invalid campaigns object: {
"limit" : 50,
"offset" : 0,
"total" : 4,
"values" :
[
{
"autoAccept" : false,
"createdAt" : "2020-08-13T12:03:52Z",
"failureCode" : null,
"id" : "90ef82fa-a059-4a7d-a8bd-8b3da15d6ef6",
"mainCampaignId" : null,
"name" : "Campaign-4",
"namespace" : "default",
"status" : "finished",
"updateId" : "b750e3b4-8026-46ef-b7ae-3e8937174b2e",
"updatedAt" : "2020-08-13T12:03:58Z"
},
{
"autoAccept" : false,
"createdAt" : "2020-08-13T11:26:15Z",
"failureCode" : null,
"id" : "4e3c3652-af2e-494d-b9ab-76ce86e0db13",
"mainCampaignId" : null,
"name" : "Done FROM CURL",
"namespace" : "default",
"status" : "finished",
"updateId" : "b750e3b4-8026-46ef-b7ae-3e8937174b2e",
"updatedAt" : "2020-08-13T11:39:35Z"
}
]
}
got CampaignCheckComplete event
This is very different from what we had received from the OTA Connect commercial solution as shown below:
Campaign: {
"campaigns" :
[
{
"id" : "f06b3989-3592-4b3e-898b-2e08efc98935",
"metadata" : [],
"name" : " intel-x86-NUCv6-UP1-C1",
"size" : null
}
],
"deviceId" : "aecd65d5-0b97-443e-a711-d019fabde4bc"
}
It looks like the campaigns are not properly associated with the device group, yet my REST API request to create the campaign was successful and appears to match what is expected. The body of my campaign creation looks like:
{
"name": "Done FROM CURL",
"update": "86b80fde-70b1-4b94-aa4f-722b747fdbe4",
"groups": [
"737e91b8-0cb2-4601-a44b-7a749ecddb83"
],
"approvalNeeded": false
}
Is there something missing?
The problem occurs when I go through the web interface and am presented with the "Select update" dialog. The campaigner returns a 500 error. The error dialog then says:
No updates found. Create some updates first.
This part is identical to advancedtelematic/campaigner#133. The workaround is to use the REST APIs to create a campaign. However, this just "moves" the problem to another location. Now, when the client requests the list of available campaigns, it gets:
This is very different from what we had received from the OTA Connect commercial solution as shown below:
It looks like the campaigns are not properly associated with the device group, yet my REST API request to create the campaign was successful and appears to match what is expected. The body of my campaign creation looks like:
Is there something missing?