Adding to my below post , I would like to inform that I upgraded the kernel 
to CentOS 6.5 X86_64

[root@puppet ~]# uname -a
Linux puppet.xoriant.in 2.6.32-431.20.3.el6.x86_64 #1 SMP Thu Jun 19 
21:14:45 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Issue still persists

On Wednesday, 9 July 2014 14:29:40 UTC+5:30, Varun Utagikar wrote:
>
> Hello
>
> I am trying to implement role-profile structure . I have referred below 
> mentioned docs/links :
>
>
> https://ask.puppetlabs.com/question/1655/an-end-to-end-roleprofile-example-using-hiera/
> https://projects.puppetlabs.com/issues/16667
>
> I have hit a brick wall. I am trying to pull a file on an agent from a 
> master where I have defined a sample role and profile structure. I have 
> tested using Puppet 3.6.2 , Puppet 3.6.1 and the free enterprise version of 
> Puppet. I am getting the same error :
>
> <agentsnip>
> Error: /Stage[main]/Siler/File[/tmp/a]: Could not evaluate: Could not 
> retrieve file metadata for puppet:///puppet/modules/siler/a: Error 400 on 
> SERVER: Not authorized to call find on 
> /file_metadata/puppet/modules/siler/a with {:links=>"follow", 
> :source_permissions=>"ignore"}
> Wrapped exception:
> Error 400 on SERVER: Not authorized to call find on 
> /file_metadata/puppet/modules/siler/a with {:links=>"follow", 
> :source_permissions=>"ignore"}
> </agentsnip>
>
> <mastersnip>
> Debug: Evaluating match for Route /^\/v2\.0/
> Debug: Did not match path 
> ("/production/file_metadata/puppet/modules/siler/a")
> Debug: Evaluating match for Route /.*/
> Error: Not authorized to call find on 
> /file_metadata/puppet/modules/siler/a with {:links=>"follow", 
> :source_permissions=>"ignore"}
> Debug: Routes Registered:
> Debug: Route /^\/v2\.0/
> </mastersnip>
>
> My puppet dir. hierarchy :
>
> puppet/
> ├── auth.conf
> ├── environments
> │   └── example_env
> │       ├── manifests
> │       ├── modules
> │       └── README.environment
> ├── fileserver.conf
> ├── manifests
> │   ├── nodes
> │   │   └── pu.pp
> │   └── site.pp
> ├── modules
> │   ├── profile
> │   │   └── manifests
> │   │       └── init.pp
> │   ├── role
> │   │   └── manifests
> │   │       └── init.pp
> │   ├── siler
> │   │   ├── file
> │   │   │   ├── a
> │   │   │   ├── b
> │   │   │   ├── c
> │   │   │   ├── d
> │   │   │   └── e
> │   │   └── manifests
> │   │       └── init.pp
> │   └── xyz
> │       ├── files
> │       │   └── xyz
> │       └── manifests
> │           └── init.pp
> └── puppet.conf
>
> I am attaching my sample manifest files. 
> I am using CentOS 6.3 x86_64 on both master and agent.
> # uname -a
> Linux puppet.example.in 2.6.32-279.el6.x86_64 #1 SMP Fri Jun 22 12:19:21 
> UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
> # cat /etc/redhat-release
> CentOS release 6.3 (Final)
>
> I am using /etc/hosts file for name resolution.
>
> I tried in vain all the troubleshooting steps that i could find . I am not 
> sure whether its just a simple configuration issue or a bug. I am unable to 
> troubleshoot further due to non availability of documentation on 
> role-profile definitions.I request you to help me in sorting this out.
>
> Varun A Utagikar
> p.s. - Sorry for the long mail.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/be721f80-98bb-44f0-a9ff-ee904a90b6cf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to