on-08:~$ kubectl get pods
NAME READY STATUS
RESTARTS AGE
flaggedrevspromotioncheck-7cbfff44fc-q55gm 0/1 ContainerCreating 0
5m18s
Best regards,
Count Count
On Thu, Jan 9, 2020 at 10:58 PM Bryan Davis wrote:
> I am happy to announc
NAME READY STATUS RESTARTS AGE
countcounttest-6b58f5c547-mf4jx 0/1 ContainerCreating 0 77s
I will leave that running. If the container gets created I might also be
able to reproduce the segfault.
Best regards,
Count Count
On Sun, Jan 12, 2020
/usr/lib/uwsgi/plugins/python_plugin.so:
cannot open shared object file: No such file or directory !!!
On Sun, Jan 12, 2020 at 11:42 PM Alex Monk wrote:
> Hi Count Count, I believe I may have sorted out an issue that prevented
> some pods (depending partially on luck) from creating containers. Your pod
ter are not
>> using. I doubt it's the source problem as uwsgi shouldn't be segfaulting
>> over some problem talking to LDAP...
>> Needs further investigation by someone during the week I think.
>>
>> On Sun, 12 Jan 2020 at 23:00, Count Count
>> wrote:
>
gt; inside the image/application code rather than the cluster itself anyway.
>>>> I notice the pod on the new cluster seems to be using the sssd variant
>>>> of the toolforge-python37-web image, which pods in the old cluster are not
>>>> using. I doubt it
