Latest build of master does not work - is there a good branch to use?

[screeley44]

[root@ip-10-0-30-112 ~]# oc get pods
NAME                                            READY   STATUS             RESTARTS   AGE
federation-controller-manager-76687dcbd-hbcc8   0/1     CrashLoopBackOff   12         38m


[root@ip-10-0-30-112 ~]# oc logs federation-controller-manager-76687dcbd-hbcc8
/root/controller-manager flag redefined: log_dir
panic: /root/controller-manager flag redefined: log_dir

goroutine 1 [running]:
flag.(*FlagSet).Var(0xc000096180, 0x160b8e0, 0xc000376500, 0x1479acc, 0x7, 0x14ab0bd, 0x2f)
	/usr/local/go/src/flag/flag.go:805 +0x529
flag.(*FlagSet).StringVar(0xc000096180, 0xc000376500, 0x1479acc, 0x7, 0x0, 0x0, 0x14ab0bd, 0x2f)
	/usr/local/go/src/flag/flag.go:708 +0x8a
flag.(*FlagSet).String(0xc000096180, 0x1479acc, 0x7, 0x0, 0x0, 0x14ab0bd, 0x2f, 0xc0003764f0)
	/usr/local/go/src/flag/flag.go:721 +0x8b
flag.String(0x1479acc, 0x7, 0x0, 0x0, 0x14ab0bd, 0x2f, 0xc00025df58)
	/usr/local/go/src/flag/flag.go:728 +0x69

using registry quay.io/screeley44/origin-federation-controller:v4.0.0 and quay.io/screeley44/federation-operator-registry:v4.0.0

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci-robot]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.