0.7.5: parse_ssh_config failing in ssh_util.py

[Mark Horstman]

I've been successfully using cloud-init 0.7.4 in a centos 6.5 image I created under an icehouse environment we're running. When I recently created a new centos 6.5 image and yum installed cloud-init (from http://download.fedoraproject.org/pub/epel/6/x86_64) , I got 0.7.5 (cloud-init.x86_64 0:0.7.5-10.el6.centos.2). 0.7.5 is failing in places 0.7.4 wasn't like setting up the ssh keys for the user. I turned on DEBUG for cloud-init console logging in /etc/cloud/cloud.cfg.d/05_logging.cfg:

   [handler_consoleHandler]
   class=StreamHandler
   level=DEBUG
   formatter=arg0Formatter
   args=(sys.stderr,)

and here's /var/log/cloud-init-output.log http://pastebin.ubuntu.com/8869713/

Attached is a zip file containing copies of my /etc/ssh/sshd_config temporary keys I used that were generated via the OpenStack gui.

[Mark Horstman (mah042)]

It seems to have something to do with the last line I added to /etc/ssh/sshd_config:
PermitRootLogin=no

If I remove that line, parse_ssh_config() in ssh_util.py no longer fails

[Anthony D'Atri (aad-r)]

I've experienced issues with 2.7.4 and a similar append of lines to sshd_config. cloud-init appears to eat a terminal newline, leaving the file without one, which alone can cause problems that are only made worse by future edits like:

echo "PermitRootLogin without-password" >>/etc/ssh/sshd_config

in that this can result in the last line of the file looking like:

ServerAliveInterval 300PermitRootLogin without-password

which prevents sshd from starting at next reboot. I've taken to echoing several blank lines onto the end of the file to avoid this.

--aad

> It seems to have something to do with the last line I added to /etc/ssh/sshd_config:
> PermitRootLogin=no
>
> If I remove that line, parse_ssh_config() in ssh_util.py no longer fails
>
> --
> You received this bug notification because you are subscribed to cloud-
> init.
> Matching subscriptions: cloud-init
> https://bugs.launchpad.net/bugs/1391303
>
> Title:
> 0.7.5: parse_ssh_config failing in ssh_util.py
>
> Status in Init scripts for use on cloud images:
> New
>
> Bug description:
> I've been successfully using cloud-init 0.7.4 in a centos 6.5 image I
> created under an icehouse environment we're running. When I recently
> created a new centos 6.5 image and yum installed cloud-init (from
> http://download.fedoraproject.org/pub/epel/6/x86_64) , I got 0.7.5
> (cloud-init.x86_64 0:0.7.5-10.el6.centos.2). 0.7.5 is failing in
> places 0.7.4 wasn't like setting up the ssh keys for the user. I
> turned on DEBUG for cloud-init console logging in
> /etc/cloud/cloud.cfg.d/05_logging.cfg:
>
> [handler_consoleHandler]
> class=StreamHandler
> level=DEBUG
> formatter=arg0Formatter
> args=(sys.stderr,)
>
> and here's /var/log/cloud-init-output.log
> http://pastebin.ubuntu.com/8869713/
>
> Attached is a zip file containing copies of my /etc/ssh/sshd_config
> temporary keys I used that were generated via the OpenStack gui.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/cloud-init/+bug/1391303/+subscriptions

[Mark Horstman (mah042)]

It would seem cloud-init doesn't like the "=" in "PermitRootLogin=no" in /etc/ssh/sshd_config. Also, something, I assume cloud-init, is removing the last <LF> from /etc/ssh/sshd_config.

If I change the /etc/ssh/sshd_config line I added from:
PermitRootLogin=no
to:
PermitRootLogin no

it no longer fails. Sshd does not complain about the "=".

It would seem cloud-init can't deal with "=" as var/val assignments in /etc/ssh/sshd_config and it's erroneously removing the last <LF> from the file (/etc/ssh/sshd_config).

This is strictly a guess based upon the behavior observed through trial and error, I have not examined the source code.

[Dan Watkins (oddbloke)]

I'm looking at fixing the '=' problem now.

[Dan Watkins (oddbloke)]

The attached branch should fix the '=' problem.

[Scott Moser (smoser)]

This is fixed in cloud-init 0.7.7.

[James Falcon (falcojr)]

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