Cinder

  1. Bug #1367189
  2. Comment #7

Comment 7 for bug 1367189

Revision history for this message
Jay Bryant (jsbryant) wrote :

Tao,

I found the change I was thinking of: https://review.openstack.org/#/c/129756/

commit c22038b9005070e51224f5057aac9f73cf4d0340
Author: Tomoki Sekiyama <email address hidden>
Date: Mon Oct 20 14:32:55 2014 -0400

    TgtAdm: Don't change CHAP username/password on live migration

    As tgtd doesn't update CHAP username/password while the initiator is
    connected, CHAP username/password must not be changed while a Nova
    instance are performing live-migration; otherwise the compute node
    which the instance migrates to cannot login to the volume and the
    migration process is aborted.

    This fixes TgtAdm implementation not to regenerate random
    username/password every time initialize_connection is called.
    Also, it enables CHAP auth in unit tests of TargetAdmin helpers.

    Change-Id: I48729a33fada62a7c8e4fe500b1e39533d898701
    Closes-Bug: #1383509

I am wondering if that change has made it so we don't have issues any more. I remember looking at this problem and thinking it looked like the credentials were getting messed up. Could you follow up and see if this appears plausible?

Thanks!