facing issues deploying purser on OpenShift

[canit00]

Attempting to deploy purser on OpenShift facing one of many issues in particular: kreddyj/purser:controller-1.0.2

Pod starts up fine

cat purser-6df8954b94-v5xg6-pod-description.txt 
Name:               purser-6df8954b94-v5xg6
Namespace:          purser
Priority:           0
PriorityClassName:  <none>
Node:               aio.domain.us/192.168.122.99
Start Time:         Sat, 12 Oct 2019 15:52:24 -0400
Labels:             app=purser
                    pod-template-hash=2894510650
Annotations:        openshift.io/scc=restricted
Status:             Running
IP:                 10.128.0.219
Controlled By:      ReplicaSet/purser-6df8954b94
Containers:
  purser-controller:
    Container ID:  docker://8fddf12979d85664e8bcc1f4622d591b6842aca6da13004f283f640277818917
    Image:         kreddyj/purser:controller-1.0.2
    Image ID:      docker-pullable://docker.io/kreddyj/purser@sha256:5d050cde94a49b2c73445dd61221e91ce0f107fa4374a5c604ef270628dfa6d5
    Port:          3030/TCP
    Host Port:     0/TCP
    Command:
      /controller
    Args:
      --log=info
      --interactions=disable
      --dgraphURL=purser-db
      --dgraphPort=9080
    State:          Running
      Started:      Sat, 12 Oct 2019 15:52:28 -0400
    Ready:          True
    Restart Count:  0
    Limits:
      cpu:     300m
      memory:  1000Mi
    Requests:
      cpu:        300m
      memory:     1000Mi
    Environment:  <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from purser-service-account-token-jfb4k (ro)
Conditions:
  Type              Status
  Initialized       True 
  Ready             True 
  ContainersReady   True 
  PodScheduled      True 
Volumes:
  purser-service-account-token-jfb4k:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  purser-service-account-token-jfb4k
    Optional:    false
QoS Class:       Guaranteed
Node-Selectors:  node-role.kubernetes.io/compute=true
Tolerations:     node.kubernetes.io/memory-pressure:NoSchedule
Events:
  Type    Reason     Age   From                     Message
  ----    ------     ----  ----                     -------
  Normal  Scheduled  55m   default-scheduler        Successfully assigned purser/purser-6df8954b94-v5xg6 to aio.domain.us
  Normal  Pulling    55m   kubelet, aio.domain.us  pulling image "kreddyj/purser:controller-1.0.2"
  Normal  Pulled     55m   kubelet, aio.domain.us  Successfully pulled image "kreddyj/purser:controller-1.0.2"
  Normal  Created    55m   kubelet, aio.domain.us  Created container
  Normal  Started    55m   kubelet, aio.domain.us  Started container

However, purser pod logs show errors opening/writing purser.log and I find no option to set the log path - such that I could attach a PV or emptyDir.

cat purser-6df8954b94-v5xg6-pod.log 
time="2019-10-12T19:52:28Z" level=error msg="failed to open file purser.log, open purser.log: permission denied"
INFO[0006] Purser server started on port `localhost:3030` 
INFO[0006] CloudProvider: aws, Region: us-east-1  

Attaching full log.
purser-6df8954b94-v5xg6-pod.log

If one would extend the logging options would /pkg/utils/logutil.go be the right place? Also what other location will this container need write access to? It appears that it is attempting to write to / ? Just trying to understand the following errors:

^[[36mINFO^[[0m[0207] Pod with xid: (purser:purser-6df8954b94-v5xg6) persisted in dgraph
Failed to write to log, invalid argument
^[[36mINFO^[[0m[0207] Container with xid: (purser:purser-6df8954b94-v5xg6:purser-controller) persisted in dgraph
Failed to write to log, invalid argument

go version go1.12.10 linux/amd64

oc v3.11.135
kubernetes v1.11.0+d4cacc0
features: Basic-Auth GSSAPI Kerberos SPNEGO

Server https://aio.domain.us:8443
openshift v3.11.135
kubernetes v1.11.0+d4cacc0

[kreddyj]

Hi @canit00, thanks for pointing out the issue. We are publishing the logs into Stdout and a file purser.log. The controller doesn't have enough permissions to create and open log file purser.log so it is throwing an error. We are looking into the issue and will get back to you with the right permission in case of openshift.

Kubernetes saves the logs that are published to Stdout, which we can use it instead of the purser.log file. Other than the logging issue, is the purser service running properly?

[canit00]

Thank you @kreddyj! If purser.log can be removed completely that be ideal. Also having issues with the UI container due to the user it wants to run as so it fails to start up. I decided to raise one issue at a time. I'll start looking into the UI issue next. TL;DR purser not running properly. But would love to get it there. 😀