Pivotal Knowledge Base

Follow

icm deploy reports Expected puppet tar file does not exist

Environment

  • PCC 2.2.1

Symptom

Puppet sync fails with error

[ERROR] Expected puppet tar file, /home/gpadmin/17.tar.gz, does not exist.
[INFO] Cleaning up old status files
[INFO] Checking yum repo file
[ERROR] Expected puppet tar file, /home/gpadmin/17.tar.gz, does not exist.

Cause

This problem is most likely a result of some permission issue on the pivotal command center admin node. The command used to sync the tar files as followed:

massh hostfile push /var/lib/gphd/gphdmgr/clusters/tarz/17.tar.gz

Fix

Some things to check

  • Make sure gpadmin has permissions to access this tar file. if not then the directory /var/lib/gphd/gphdmgr/clusters was created when root umask is set to something other then 022
    • ls -l /var/lib/gphd/gphdmgr/clusters/tarz/17.tar.gz
  • Make sure the default umask is 022 for root and gpadmin user. If not then you need to delete all extracted tarballs and uninstall/reinstall PCC
    • If default umask is 022 then a new file and dir permissions should look like the following ( dir=755, file=644 )
      [root@pccadmin ~]# mkdir newDir
      [root@pccadmin ~]# touch newFile
      [root@pccadmin ~]# ls -l
      drwxr-xr-x  2 root root  4096 Oct 17 10:09 newDir
      -rw-r--r--  1 root root     0 Oct 17 10:09 newFile
  • Login any of the cluster node and verify if write permission are there under directory as indicated in the error, i.e "/home/gpadmin". ICM might fail to push this files if there are permission issues for gpadmin user.

Comments

Powered by Zendesk