Bug #3176
closed
ENC output base64 encoded
Added by Romain Vrignaud about 11 years ago.
Updated almost 11 years ago.
Description
Hello,
In my new setup (Foreman 1.3) installed from sources,
I have ENC output encoded in base64 (see below).
It seems that it's this commit (91ad276d660) that's bringing
this buggy behavior.
---
classes:
!binary "YmFzZQ==":
!binary "YmFzZTo6cGxvdWY=":
!binary "YmluZDo6c2xhdmU=":
!binary "cG9zdGZpeA==":
!binary "dXNlcjo6Zml0emRzbA==":
parameters:
puppetmaster: !binary |-
amFpbC5maXR6ZHNsLm5ldA==
foreman_env: !binary |-
cHJvZHVjdGlvbg==
environment: !binary |-
cHJvZHVjdGlvbg==
My only thought is that no longer loading Puppet into the app has changed the behaviour?
The base64 encoded ENC output is still valid, so I don't think the test would break even if .to_yaml provided base64-encoded data.
I forgot to say, I don't see this on my installations - all Ruby 1.9.3. Which Ruby version are you using Romain?
I'm on Ubuntu 13.04 with ruby 1.9.3p194
- Status changed from New to Feedback
It seems this is caused by the 'mysql' adapter somehow, perhaps something is triggering it to return strings with the wrong encoding (a guess). However the 'mysql2' adapter appears to work correctly, so please install foreman-mysql2 and change the adapter in /etc/foreman/database.yml to adapter2.
- Status changed from Feedback to Closed
Bug solved by switching to mysql2.
Also available in: Atom
PDF