fix glog logging

[jboyd01]

force go flag initialization to satisfy glog that cmd line parameters have been initialized. Fixes #1187

"ERROR: logging before flag.Parse" is prefacing all log entries for Catalog Controller and API servers.

Workaround pulled from kubernetes/kubernetes#17162.

[jboyd01]

All set for review @pmorie. I reverted the code change and as we discussed, updated glide.yaml with the current sha1 from glide.lock for every package that lacked a version and changed glog to point to the previous version. I verified both API and Controller servers are logging correctly.

[MHBauer]

Why should we prefer this over the workaround?

[pmorie]

@MHBauer i think anything that adds specificity to the glide yaml is beneficial. I would also like to not be on a version of glog that main k8s is on, and the workaround is really silly (since we don't use flag)

[MHBauer]

not be on a version of glog that main k8s is on

What? Why?

[pmorie]

@MHBauer i don't want to hit some random bug on a newer version of dependency than main k8s is. That's not the issue here, but that's my general feeling on the subject.

[MHBauer]

Not being on a newer version of glog is okay.

I'm fine with glide cleanup in general.

I do not understand why we would we explicitly not sync with the same version of glog upstream-k8s has.

EDIT: dash for clarity.

[arschles]

Thanks @jboyd01

LGTM

[pmorie]

I do not understand why we would we explicitly not sync with the same version of glog upstream k8s has.

I think we might have a communication mismatch. This PR pins us to the version of glog k8s is on.

[MHBauer]

@pmorie okay, fine with me. I'm not sure how I could interpret "I would also like to not be on a version of glog that main k8s is on" as meaning we want the same version of k8s, but okay.

EDIT: indication that emphasis is mine.

[MHBauer]

LGTM

didn't check that the version matching is true, but assuming good faith that it is.

[pmorie]

k8s is on

Oops, I meant "isn't on"