Atom feed of this document
  
 

 Recover from a UID/GID mismatch

When running OpenStack Compute, using a shared file system or an automated configuration tool, you could encounter a situation where some files on your compute node are using the wrong UID or GID. This causes a number of errors, such as being unable to do live migration or start virtual machines.

The following procedure runs on nova-compute hosts, based on the KVM hypervisor, and could help to restore the situation:

 

Procedure 4.9. To recover from a UID/GID mismatch

  1. Ensure you do not use numbers that are already used for some other user/group.

  2. Set the nova uid in /etc/passwd to the same number in all hosts (for example, 112).

  3. Set the libvirt-qemu uid in /etc/passwd to the same number in all hosts (for example, 119).

  4. Set the nova group in /etc/group file to the same number in all hosts (for example, 120).

  5. Set the libvirtd group in /etc/group file to the same number in all hosts (for example, 119).

  6. Stop the services on the compute node.

  7. Change all the files owned by user nova or by group nova. For example:

    # find / -uid 108 -exec chown nova {} \; # note the 108 here is the old nova uid before the change
    # find / -gid 120 -exec chgrp nova {} \;
  8. Repeat the steps for the libvirt-qemu owned files if those needed to change.

  9. Restart the services.

  10. Now you can run the find command to verify that all files using the correct identifiers.

Questions? Discuss on ask.openstack.org
Found an error? Report a bug against this page

loading table of contents...