yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1498753@xxxxxxxxxxxxxxxxxx>]

[Expired for cloud-init because there has been no activity for 60 days.]

** Changed in: cloud-init
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1498753

Title:
  Cloud-init hangs vagrant machines with LDAP on boot

Status in cloud-init:
  Expired

Bug description:
  
  # Using vagrant + virtualbox as the virtual machine provider.
  # Vagrantfile contains the box definition as next:
  	config.vm.define "user" do |user|
                  user.vm.box = "ubuntu/trusty64"
                  user.vm.network "private_network", ip: "192.168.11.12"
          end

  # This issue was faced within setting up LDAP authentication to this
  virtual server.

  # The original "what was done" flow was:
  # install LDAP modules
  apt-get install libpam-ldap nscd
  # add pam_mkhomedir.so to /etc/pam.d/common-sessions

  # and edit /etc/nsswitch.conf to look like: 
  passwd: ldap compat
  group: ldap compat
  shadow: ldap compat

  # after restarting the services, everything works nicely
  # if the machine is rebooted, it hangs to the boot claiming that network cannot be set-up.
  # This happens even though 

  # however, everything works nicely even in reboot if the /etc/nsswitch.conf is other way round:
  passwd: compat ldap 
  group: compat ldap 
  shadow: compat ldap 
  # This method however breaks the authentication overrides

  # Furthermore searching the stuff it turned out that if /etc/nsswitch.conf is edited to use the LDAP first
  # even though the LDAP packages are not installed neither configured -> machine cannot boot
  # vagrant is waiting for authentication, using the virtualbox GUI one can find out what the machine is doing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1498753/+subscriptions