Octal numbers in Yaml deserialized as decimal numbers

[morfj]

V1ConfigMapVolumeSource -> DefaultMode requires an integer and its quite common in YAML files that this is written as an octal number (e.g.: 0777). It seems however that the parser is interpreting it as a decimal number. Serializing it back into a YAML string sets the property to 777 which gets rejected by the cluster's validation.

[brendandburns]

We'll investigate how to do this, I'm not sure how YAML defines hex vs decimal number formats. It may be a bug in the YAML parser...

[brendandburns]

I reproduced this in a unit test, but I'm not sure why it is happening. It definitely looks like the Yaml parser supports octal numbers, and a simple octal parse -> int works correctly.

I will continue to investigate.

[brendandburns]

Figured it out. There's a bug in the YamlDotNet library.

I sent a fix to them, but I don't know how long it will take to get it released. We also need to update the YamlDotNet version to be latest anyway (#504)

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten