# Controlplane keeps hanging Travis CI logs not really verbose

**URL:** https://travis-ci.community/t/controlplane-keeps-hanging-travis-ci-logs-not-really-verbose/12453
**Category:** v2
**Tags:** build-env
**Created:** [December 7, 2021, 11:15pm UTC](https://travis-ci.community/t/controlplane-keeps-hanging-travis-ci-logs-not-really-verbose/12453 "2021-12-07T23:15:19Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![HILLBILLYHeisT](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/hillbillyheist/32/7476_2.png) [@HILLBILLYHeisT](https://travis-ci.community/u/HILLBILLYHeisT)
#### Post date: [December 7, 2021, 11:15pm UTC](https://travis-ci.community/t/controlplane-keeps-hanging-travis-ci-logs-not-really-verbose/12453/1 "2021-12-07T23:15:19Z")

</div>

I’m trying to deploy a Kong API gateway backed up with Postgres to Kubernetes subrouting to a Docker container.

After executing the step of `kubectl -n kong apply -f kong-control-plane-postgres.yaml` , then try to  
`kubectl get pods -n kong` , it returns the following pods which is always in Initializing status

> NAME READY STATUS RESTARTS AGE  
> kong-control-plane-6c8b4c89b7-heist 0/1 Init:0/2 0 19s  
> kong-control-plane-bootstrap-heist20/1 Init:0/1 0 19s  
> Postgres-heist 1/1 Running 0 84s

Try to debug the container through `kubectl logs kong-control-plane-bootstrap-bgfmg wait-for-postgres -n kong` , it shows the following error:

> nc: bad address ‘postgres.kong.svc’  
> waiting for db

Then just hangs through Travis CI? any ideas…

---

<div class="post-metadata">

### Author: ![Montana](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/montana/32/9566_2.png) [@Montana](https://travis-ci.community/u/Montana)
#### Post date: [December 7, 2021, 11:23pm UTC](https://travis-ci.community/t/controlplane-keeps-hanging-travis-ci-logs-not-really-verbose/12453/2 "2021-12-07T23:23:59Z")

</div>

Hey,

This is more of a Kong problem, but I’ll be glad to help you here, and honestly this is a little bit out of Travis CI’s wheelhouse.

The Kong control plane manifests a subroutine to bootstrap, this in turn pushes to the datastore. Can you check if it that ran or even was successful?

```auto
kubectl get job -n kong

```

You might want to `rev-parse` in `git`. You need to verify that exactly one parameter is provided, and that it can be turned into a raw 20-byte SHA-1 that can be used to access the object database. If so, emit it to the standard output; otherwise, error out.

```auto
git rev-parse --short HEAD
(commit number)

```

For more of a verbose output, you can run:

```auto
git fsck | awk '{print $3}' | xargs -I '{}' git show {} >> kong_contents

```

```auto
kubectl apply -f kong-namespace.yaml
./setup_certificate.sh
kubectl create -f postgres.yaml
kubectl get all -n kong #waited for postgres to be ready
kubectl -n kong apply -f kong-control-plane-postgres.yaml
kubectl get all -n kong

```

If you’re still having difficulty swap the init container with something you’re comfortable debugging from (Busybox, Ubuntu or even something like HashiCorp’s Vagrant.) Then change the command to `tail -f /dev/null` and then `kubectl exec` into it and try and determine why it can’t reach `PostGRES`.

You may want to checkout the documentation on [Kong’s website.](https://docs.konghq.com/gateway/2.6.x/plan-and-deploy/systemd/#main)

---

<div class="post-metadata">

### Author: ![HILLBILLYHeisT](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/hillbillyheist/32/7476_2.png) [@HILLBILLYHeisT](https://travis-ci.community/u/HILLBILLYHeisT)
#### Post date: [December 8, 2021, 4:07am UTC](https://travis-ci.community/t/controlplane-keeps-hanging-travis-ci-logs-not-really-verbose/12453/3 "2021-12-08T04:07:40Z")

</div>

Hey @montana,

You’re amazing! Is there anyway I can merge the whole branch, but only really specific commits from the other branch.

When running `git fsck | awk` this was the fix, but now I have this quagmire.

---

<div class="post-metadata">

### Author: ![Montana](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/montana/32/9566_2.png) [@Montana](https://travis-ci.community/u/Montana)
#### Post date: [December 8, 2021, 4:17am UTC](https://travis-ci.community/t/controlplane-keeps-hanging-travis-ci-logs-not-really-verbose/12453/4 "2021-12-08T04:17:52Z")

</div>

Yes there is a way @HILLBILLYHeisT,

Just use the `git cherry-pick` command. Ultimately the hash uniquely defines the commit - regardless of what branch it’s in.

So for example, you’ll run `git cherry-pick` then the `commit` you’re looking for:

```auto
git cherry-pick 123456

```

Now check, remove the `temp` branch and push:

```auto
git log
git branch -D otherrepo-master
git push origin master

```
