@Enrico Tassi : can you have a look at this CI run - it did work the night before. I did restart it - it is not an intermittent issue.
it seems a connectivity issue, security.ubuntu.com down...
@Enrico Tassi I don't quite get what is going on.
security.ubuntu.com seems to work from 3 different networks I tried. Still CI fails consistently. Is the name server of github broken?
According to https://status.canonical.com/ the security archive is on
not the DNS, since mine resolves to the same IPs...
The same CI cannot reach
Actually, there is the VM and the LXD container.. it could also be there the problem, but we just call an existing action
Yes, this is also what I see. So Github network infrastructure is broken? That's what I meant with name server - the github internal name server (I guess they have one - even I have a few).
Yes and interestingly it did work until last night.
Maybe I try a local build.
I would try to update the snapcraft action to 1.2
OK, let me piggy back this in the 2022.09.1 PR.
sorry, I was looking at the wrong action
There is version 1.1.2 while we run 1.0.9
OK, I try this.
Look here: https://github.com/snapcore/action-build/commit/07c9fa149882563bf8edc39c35023e4ae6148a46
I've no clue, but seems worth trying
I see. The PR is running - we should know in a few minutes (it usually fails after 5).
Seems to have worked - the job runs since 10 minutes now ...
Maybe we can just use
@v1 , so that all minor version are automatic. This is what they recommend usually.
I see. I guess I should do this with all actions we use ...
But after the release.
Good we found the issue, since I had to rebuild the installers for the school and I was hit by that too.
Last updated: Jan 30 2023 at 11:03 UTC