@george1421 thanks for your quick response. I believe that all users we create through the web UI are admin users. I come into a very odd situation.
- I created image 1 and captured the info through computer A with the default fog user. This image 1 works perfectly fine when I deploy to computer B and C
- I then created a new user, called test, without the API enabled, and removed the default user fog through the UI (default user had UI enabled). Since the image 1 is created through the fog user, everything still works fine with deployment
- Now we don’t have the default user fog, I use the user test to create image 2 and capture info through computer D. I then deploy this image 2 to computer B, everything looks fine. When I deploy the image 2 to computer C, the problem occurs. The problem happens when it tries to expand the /dev/sda2, right after the cloning process is done with the message “cloning successfully” is printed out.
Computers A,B, and D are actually the same type. Computer C is a newer version of them but should be the same.
To prove that fog user is important, I build another fog project and keep the fog user when creating new image. I use computer A to get the image and deploy to computer C. Everything works perfectly.
like what I said, this is just something odd. For now I will keep the fog user when creating images