yahoo-eng-team team mailing list archive

[Rajesh <rajeshbasak716@xxxxxxxxx>]

Public bug reported:

My existing CentOS 6.7 qcow2 image had ssh password authentication
disabled. To remedy this I made necessary changes

#vi /etc/ssh/sshd_config 
comment PasswordAuthentication no and uncomment PasswordAuthentication yes.
#sudo service sshd restart
#chkconfig --level 5 sshd on

in an instance running this image.  Then, after shutting it down
(checked pausing it too) I took snapshot of it from cli.

[root@node-61 ~]# nova --version
2.18.1
[root@node-61 ~]# nova image-create e25a6289-d3f3-4ed1-8ab3-c4b828963c85 Meghadoop_snapshot_ready

Now, If I instantiate a new VM with the created snapshot
"Meghadoop_snapshot_ready", the changes made to sshdconfig is not
reflected i.e. the new VM's sshdconfig has PasswordAuthentication no.
However, the original instance, as expected, retains the changes made to
sshdconfig after starting (or resuming). So I guess this is not due to
dirty OS buffers etc.

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: snapshot

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1538007

Title:
  nova image-create snapshot does not reflect changes made to sshdconfig

Status in OpenStack Compute (nova):
  New

Bug description:
  My existing CentOS 6.7 qcow2 image had ssh password authentication
  disabled. To remedy this I made necessary changes

  #vi /etc/ssh/sshd_config 
  comment PasswordAuthentication no and uncomment PasswordAuthentication yes.
  #sudo service sshd restart
  #chkconfig --level 5 sshd on

  in an instance running this image.  Then, after shutting it down
  (checked pausing it too) I took snapshot of it from cli.

  [root@node-61 ~]# nova --version
  2.18.1
  [root@node-61 ~]# nova image-create e25a6289-d3f3-4ed1-8ab3-c4b828963c85 Meghadoop_snapshot_ready

  Now, If I instantiate a new VM with the created snapshot
  "Meghadoop_snapshot_ready", the changes made to sshdconfig is not
  reflected i.e. the new VM's sshdconfig has PasswordAuthentication no.
  However, the original instance, as expected, retains the changes made
  to sshdconfig after starting (or resuming). So I guess this is not due
  to dirty OS buffers etc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1538007/+subscriptions