vserver guest results in always container

[Niels Jansen]

for resizeing filesystems cc_resizefs.py, needs to check if the running system is a container, this is done in util.py.

for vservers the test always ends up true, since the VxID: line in /proc/self/status sometimes has a space, or a tab or noting.

to make the detection work a bit better i added .strip() to the compare line.

now my vserver enabled host is resized as expected.

I have added a small patch.

my example /procy/self/status:

root@niels-6:~# cat /proc/self/status
Name: cat
State: R (running)
Tgid: 3319
Pid: 3319
PPid: 3165
TracerPid: 0
Uid: 0 0 0 0
Gid: 0 0 0 0
FDSize: 256
Groups: 0
VmPeak: 4372 kB
VmSize: 4372 kB
VmLck: 0 kB
VmPin: 0 kB
VmHWM: 608 kB
VmRSS: 608 kB
VmData: 312 kB
VmStk: 136 kB
VmExe: 48 kB
VmLib: 1788 kB
VmPTE: 32 kB
VmSwap: 0 kB
Threads: 1
SigQ: 1/16074
SigPnd: 0000000000000000
ShdPnd: 0000000000000000
SigBlk: 0000000000000000
SigIgn: 0000000000000000
SigCgt: 0000000000000000
CapInh: 0000000000000000
CapPrm: ffffffffffffffff
CapEff: ffffffffffffffff
CapBnd: ffffffffffffffff
Cpus_allowed: 3
Cpus_allowed_list: 0-1
Mems_allowed: 00000000,00000001
Mems_allowed_list: 0
VxID: 0
NxID: 0
voluntary_ctxt_switches: 2
nonvoluntary_ctxt_switches: 0

[Dan Watkins (oddbloke)]

Hi Niels,

Sorry we haven't go to this before, but we are doing bug triage now. Is this still an issue you're seeing?

Thanks!

[Launchpad Janitor (janitor)]

[Expired for cloud-init because there has been no activity for 60 days.]

[James Falcon (falcojr)]

Tracked in Github Issues as https://github.com/canonical/cloud-init/issues/2585