|Priority:||4 - Normal|
|Created by:||Former user|
|Reported by:||Former user|
|Assigned to:||Former user|
Fixed: A fix for this issue is checked into the tree and tested.
(Resolution Date: 2015-08-17T20:13:44.000Z)
2015-08-20 Vasa (Release Date: 2015-08-20)
Ubuntu 14.04 certified:
root@48663c5b-e4d0-62f3-ae44-cc6b8014d4a2:~# ruby test.rb &
root@48663c5b-e4d0-62f3-ae44-cc6b8014d4a2:~# cat /proc/1696/cmdline | tr '\000' '\n'
Ubuntu 14.04 in LX zone:
root@674dd9a3-b9bc-c8a4-b9d9-968c6dac7d03:~# ruby test.sh &
root@674dd9a3-b9bc-c8a4-b9d9-968c6dac7d03:~# cat /proc/88219/cmdline | tr '\000' '\n'
Interestingly, they both behave as expected when tested with Perl or Bash called in the same way.
This appears to be occurring due to ruby manipulating the argv array during runtime. LX currently walks argv to construct /proc/<pid>/cmdline unlike Linux, which stores start/end pointers for argv contents.
I'm trying to understand this ticket in Andrew's absence.
Patrick, I'm not sure if you've got access to the above test.rb and test.sh scripts/machines, and based on your recent comment it looks like you've already got the information you need here, but if you need me to help out at all here then let me know.
Are there customers being negatively impacted by this, or is it simply an observed delta between LX and Linux?
The customer here has reported this when attempting to get their Chef scripts to run on lx.
According to the customer, this is a blocker in their attempts to move from KVM Ubuntu to lx, which they're eager to do.
I'm not certain if this is an issue with Chef itself, or some part of their Chef cookbooks. I can find this out if it helps.
Is there an update that I can provide to the customer in this case?
I have authored a fix. It is going through review now.