{"action":"opened","issue":{"url":"https://api.github.com/repos/kubernetes/test-infra/issues/8052","repository_url":"https://api.github.com/repos/kubernetes/test-infra","labels_url":"https://api.github.com/repos/kubernetes/test-infra/issues/8052/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/test-infra/issues/8052/comments","events_url":"https://api.github.com/repos/kubernetes/test-infra/issues/8052/events","html_url":"https://github.com/kubernetes/test-infra/issues/8052","id":323820032,"number":8052,"title":"403 Forbidden & ingress address error on setting up prow on CentOS7 baremetal ","user":{"login":"sipian","id":15672091,"avatar_url":"https://avatars2.githubusercontent.com/u/15672091?v=4","gravatar_id":"","url":"https://api.github.com/users/sipian","html_url":"https://github.com/sipian","followers_url":"https://api.github.com/users/sipian/followers","following_url":"https://api.github.com/users/sipian/following{/other_user}","gists_url":"https://api.github.com/users/sipian/gists{/gist_id}","starred_url":"https://api.github.com/users/sipian/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sipian/subscriptions","organizations_url":"https://api.github.com/users/sipian/orgs","repos_url":"https://api.github.com/users/sipian/repos","events_url":"https://api.github.com/users/sipian/events{/privacy}","received_events_url":"https://api.github.com/users/sipian/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-05-16T23:16:09Z","updated_at":"2018-05-16T23:16:09Z","closed_at":null,"author_association":"NONE","body":"I am setting up prow on 1 [packet.net](https://www.packet.net/) CentOS7 machine using [getting_started.md](https://github.com/kubernetes/test-infra/blob/master/prow/getting_started.md).\r\n\r\nOn creating a cluster with minikube, I get an address(10.0.2.15) on running `kubectl get ingress ing`. \r\n\r\nBut deck pod logs are \r\n`{\"component\":\"deck\",\"error\":\"response has status \\\"403 Forbidden\\\" and body \\\"{\\\"kind\\\":\\\"Status\\\",\\\"apiVersion\\\":\\\"v1\\\",\\\"metadata\\\":{},\\\"status\\\":\\\"Failure\\\",\\\"message\\\":\\\"prowjobs.prow.k8s.io is forbidden: User \\\\\\\"system:serviceaccount:default:default\\\\\\\" cannot list prowjobs.prow.k8s.io in the namespace \\\\\\\"default\\\\\\\"\\\",\\\"reason\\\":\\\"Forbidden\\\",\\\"details\\\":{\\\"group\\\":\\\"prow.k8s.io\\\",\\\"kind\\\":\\\"prowjobs\\\"},\\\"code\\\":403}\\n\\\"\",\"level\":\"warning\",\"msg\":\"Error updating job list.\",\"time\":\"2018-05-16T22:56:10Z\"}`\r\nSimilar 403 Forbidden message are in horologium, plank, sinker pods too.\r\n\r\nWhen I tried to create cluster using [kubeadm](https://kubernetes.io/docs/setup/independent/create-cluster-kubeadm/), I **do not** get an address on running `kubectl get ingress ing` & the pod logs are similar to minikube logs.\r\n\r\nIs this because of #7950? What is the fix for this error?\r\n\r\nAlso, I want to know, to set up prow on my packet.net infrastructure do I need to create kubernetes-ingress-nginx-controller deployment manually before deploying prow? (https://github.com/kubernetes/ingress-nginx/blob/master/docs/deploy/index.md) \r\n\r\n/area prow"}}
{"actor":{"display_login":"sipian"}}