Bug #1467

invalid entry added to autosign.conf

Added by Adrian Bridgett over 1 year ago. Updated 12 months ago.

Status:Closed Start:01/23/2012
Priority:Normal Due date:
Assigned to:- % Done:

0%

Category:-
Target version:-
Backlog:No Difficulity:
Votes: 0

Description

When building the server "foreman-basic.example.com", this entry was added to /etc/puppet/autosign.conf. Using Foreman v0.4.1

["[]foreman-basic.example.com\n"]

(in case that gets mangled, that's open-square-bracket, double-quote, open-square-bracket, close-square-bracket, foreman-basic.example.com, backslash, n, double-quote, close-square-bracket.

Not sure where to start looking TBH (I have foreman-proxy installed as well, I took a quick look through the code but my ruby skills are too weak at the moment).

History

Updated by Ohad Levy over 1 year ago

how did you enter those ? the only way I could see if happening if someone enter that manually at at More > Proxies > Autosign and entered that text there.

if you have the logs from foreman that reproduce that, that would be great.

Updated by Adrian Bridgett over 1 year ago

I certainly didn't do that and don't remember altering any code that might do so. I was altering some other parts (see http://theforeman.org/issues/1461), maybe that's why.

more->smart->proxies->autosign says:

smart_proxy_autosign_url failed to generate from {:smart_proxy_id=>#<SmartProxy id: 2, name: "Smart Proxy", url: "http://192.168.122.1:18443", created_at: "2012-01-19 17:38:04", updated_at: "2012-01-19 17:48:58">, :action=>"destroy", :controller=>"SmartProxies::Autosign", :id=>"[\"[]foreman-basic.example.com\\n\"]", :auth_ation=>:destroy}, expected: {:action=>"destroy", :controller=>"SmartProxies::Autosign"}, diff: {:smart_proxy_id=>#<SmartProxy id: 2, name: "Smart Proxy", url: "http://192.168.122.1:18443", created_at: "2012-01-19 17:38:04", updated_at: "2012-01-19 17:48:58">, :id=>"[\"[]foreman-basic.example\\n\"]", :auth_ation=>:destroy}

I wonder if there's something up with my ruby install (I have both 1.8 and 1.9 installed - it's not fabulously clean).

Updated by Adrian Bridgett over 1 year ago

In case it helps, several rebuilds later autosign.conf now looks like this:

["[\"[\\\"[]foreman-basic.example.com\\\\n\\\"]foreman-basic.example.com\\n\"]foreman-basic.example.com\n"]

Updated by Ohad Levy over 1 year ago

  • Status changed from New to Need more information

do you know if you are using a smart proxy or not? could you paste the logs of when you add a new host? for both the proxy and foreman?

thanks!

Updated by Adrian Bridgett over 1 year ago

Sorry the delay - I thought I'd at least answered your first question. Yes we were using a smart proxy.

I've done a new install on a new server and I'm not seeing this behaviour any more.

Updated by leon rockmore over 1 year ago

autosign.conf is a very simple file that simply lists the objects which will be automatically signed. Good post to share. All your posts are helpful.
litigation lawyers rahleigh nc

Updated by bruce banner over 1 year ago

My computer shows an error in autosign.conf.I have no idea what this error is. Is it possible that this could be due to a virus?
sales tax auditor

Updated by rudy shweitzer about 1 year ago

I will surely try to update more things according to this as this is great help to me. Good post to share. Thanks for sharing.
reverse phone lookup

Updated by Benjamin Papillon 12 months ago

  • Status changed from Need more information to Closed

If you don't see the issue anymore, let me close the ticket.
Please, don't hesitate to open another one if the problem appears again!

Also available in: Atom PDF