Update to go 1.12 and kube 1.16 - #40
Conversation
| ) | ||
|
|
||
| func main() { | ||
| logs.InitLogs() |
There was a problem hiding this comment.
How come we don't need this (where "this" is logging) anymore?
There was a problem hiding this comment.
Good point—should we also be switching glog out for klog?
There was a problem hiding this comment.
I found the moved package an restored it. kubernetes/kubernetes@ba81a54
I don't want to re-do log handling in this PR unless absolutely necessary
There was a problem hiding this comment.
Good point—should we also be switching glog out for klog?
I would say so. Looks like everything that is in vendor is using klog.
There was a problem hiding this comment.
I don't want to re-do log handling in this PR unless absolutely necessary
Agreed. Should be a separate PR.
The package moved in kubernetes/kubernetes@ba81a54
|
The unit test are presumably failing because CI is pegged to Go 1.10 - looks like the TLS symbol requires Go 1.12: |
|
Depends on openshift/release#5289 |
|
/retest all |
|
/retest |
|
/test all |
|
/retest |
1 similar comment
|
/retest |
This log init call now apparently re-initializes logging that is being initialized somewhere else during startup, causing a panic due to duplicate flag definitions.
|
Looks like the log init needs to go away after all, as some other package is already calling it. We can untangle logging in another PR. This code predates several iterations of log library migrations. |
|
Okay, I've done some more local testing and logging is screwed up enough that I need to fix it here after all. |
|
Various infra failures. /retest |
Paritally fix logging init. This is intended to fix things enough to let us move forward to refactoring all logging.
|
@openshift/sig-network-edge okay, I think I fixed logging "enough" to move forward — let's see the latest e2e runs to make sure things are being logged (even if we get some silly flag errors mixed amongst the output). My goal is to get this working enough that we can do a followup to rip out glog entirely. |
|
If we know what the logging issues are..., then: /lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: frobware, ironcladlou The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest |
Need I say more?