Investigate 1954 certificate always regenerated #2006
Conversation
| @@ -419,6 +419,7 @@ func runActionForeachMachine(actionName string, machines []*host.Host) []error { | |||
| go machineCommand(actionName, machine, serialChan) | |||
| if err := <-serialChan; err != nil { | |||
| log.Errorln(err) | |||
| errs = append(errs, err) | |||
dgageot
force-pushed
the
1954-certificate-always-regenerated
branch
2 times, most recently
from
b08e262
to
3bcc832
Compare
dgageot
force-pushed
the
1954-certificate-always-regenerated
branch
from
3bcc832
to
c9217e8
Compare
| dialer := &net.Dialer{ | ||
| Timeout: time.Second * 2, | ||
| } | ||
|
|
||
| _, err = tls.DialWithDialer(dialer, "tcp", addr, tlsConfig) | ||
| if err != nil { | ||
| log.Debugf("Certs are not valid: %s", err) |
There was a problem hiding this comment.
@carolynvs: Does your output refer to this line: #1954 (comment) ?
There was a problem hiding this comment.
Yes line 216 from this diff above causes that message to be printed on the client and on the server I see that error about cert dates in docker.log on the host.
There was a problem hiding this comment.
@dgageot @nathanleclaire We should probably keep this debugging line in the release? It helps debugging when people are not capable of building some debugging PR by simply posting those lines in their issue...
There was a problem hiding this comment.
Sure, more debugging output usually helps.
Signed-off-by: David Gageot <david@gageot.net>
dgageot
force-pushed
the
1954-certificate-always-regenerated
branch
from
30a9399
to
e2b6a83
Compare
dgageot
changed the title
|
@nathanleclaire @dmp42 Can you please take a look? |
|
LGTM |
…ated Investigate 1954 certificate always regenerated
|
we are hunting this down, it seems a valid date issue, boot2docker having a bad |
|
too late but LGTM |
So, this does not solve anything but adds more logs during the certificates validation.