Detect cpu platform fails on containers

[fvella]

By running ck detect platform.cpu
I got the following error:

OS CK UOA:            linux-64 (4258b5fe54828a50)

OS name:              Ubuntu 18.04.2 LTS
Short OS name:        Linux 4.15.0
Long OS name:         Linux-4.15.0-45-generic-x86_64-with-Ubuntu-18.04-bionic
OS bits:              64
OS ABI:               x86_64

Platform init UOA:    42818da3a0789331
CK error: [platform.cpu] problem opening text file=/proc/cpuinfo ([Errno 107] Transport endpoint is not connected: '/proc/cpuinfo')!

The problem is related to VMWare container we use but can affect some CK workflows.

[gfursin]

Hi @fvella. Can you please tell me the version of the VMWare and how you created a container?
Or maybe you can share a sample container which I could test on my machine, please?
Thanks!

[fvella]

I do not have this information. I have to ask the ICT team this information.

[gfursin]

Sure. Do you mind to ask them, please? This may help! Thanks!

[gfursin]

Hey @fvella . I just installed VMWare Workstation Player 15 and set up a VM with Ubuntu 18.04.02. I then installed CK and tried "ck detect platform.cpu" - it worked fine on my machine:

OS CK UOA:            linux-64 (4258b5fe54828a50)

OS name:              Ubuntu 18.04.2 LTS
Short OS name:        Linux 4.18.0
Long OS name:         Linux-4.18.0-15-generic-x86_64-with-Ubuntu-18.04-bionic
OS bits:              64
OS ABI:               x86_64

Platform init UOA:    42818da3a0789331

Number of logical processors: 1
CPU name:                     Intel(R) Core(TM) i5-7300HQ CPU @ 2.50GHz
CPU ABI:                      
CPU features:                 fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon nopl xtopology tsc_reliable nonstop_tsc cpuid pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch cpuid_fault invpcid_single pti ssbd ibrs ibpb stibp fsgsbase tsc_adjust bmi1 avx2 smep bmi2 invpcid mpx rdseed adx smap clflushopt xsaveopt xsavec xsaves arat flush_l1d arch_capabilities

CPU frequency:
  CPU0 = 2496.0 MHz
CPU max frequency:
  CPU0 = 0 MHz

It's a weird problem which I can't reproduce. We need to find help from someone who understands what happens - maybe your colleagues who ran this VM?