Closed CuraDevelopment closed 11 months ago
I will see what I can do. Notice that this will cause existing certificates to be blacklisted.
I have created a change task to be handled on a PreCAB meeting tomorrow, Tuesday 24/10. I have suggested the change to be carried out on Thursday 26/10 9-10. I will report on status after the PreCAB meeting. Notice, that once this change has been implemented, the previous certificates can no longer be used.
@CuraDevelopment the deployment will most likely be scheduled for 13-14 on Thursday. Will you be able to verify after deployment, or will you wait to see the result of the following night's transfers?
We won't be able to see it until nighttime. We expect that it will fail for some customers until they've had the certificate changed - the synchronization task should automatically resume.
FYI: The change windows has been moved to 14-15 on Thursday 26/10
@CuraDevelopment : The new public keys are now active. I will look into status tomorrow wrt. Cura transfers
@CuraDevelopment we don't see any successful ingest from Cura clients this morning. Can you confirm that the certificates have not been changed on your side?
Aalbertslund should be on the new certificate.. but 10 more customers are added today.
FYI @CuraDevelopment: we have not seen data from any of your municipalities over the weekend.
@CuraDevelopment: We are seeing thousands of your calls being rejected on a daily basis, and the number increases every day. Any updates from you on this issue?
@ohetrifork a hotfix is delivered today, hopefully that will solve the issue for most of the customers.
Great, I see traffic from 11 of your municipalities this morning:
Updated pem files for coumna_cura to klgateway. Can you allow this PR to be merged no later than 27/10/2023. We've assumed that the client_id's have not been changed.