Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove skip evaluation of symlinks to data root on IoT Core #38020

Merged
merged 2 commits into from
Jul 15, 2019

Conversation

thaJeztah
Copy link
Member

This fix was added in 8e71b1e (#33498) to work around a go issue (golang/go#20506).

That issue was fixed in golang/go@66c03d3,
which is part of Go 1.10 and up. This reverts the changes that were made in
8e71b1e, and are no longer needed.

@@ -120,8 +120,6 @@ func IsWindowsClient() bool {

// IsIoTCore returns true if the currently running image is based off of
// Windows 10 IoT Core.
// @engine maintainers - this function should not be removed or modified as it
// is used to enforce licensing restrictions on Windows.
func IsIoTCore() bool {
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like this function is no longer used in our code, so perhaps we can remove it altogether (a quick search on GitHub also didn't show any users of this)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, this is the last user of this function after #38000

@thaJeztah
Copy link
Member Author

ping @jhowardmsft @darstahl PTAL 🤗

@lowenna
Copy link
Member

lowenna commented Oct 11, 2018

@taylorb-microsoft Can you loop in one of the IoT guys to verify. I believe this is OK, but I'd like their verification first.

@thaJeztah
Copy link
Member Author

Thanks! Yes; this was purely based on that comment, so would be good to double check 🤗

@darstahl
Copy link
Contributor

I no longer have an environment to test this, but LGTM pending verification that it works as intended on an IoT build.

@codecov
Copy link

codecov bot commented Oct 12, 2018

Codecov Report

❗ No coverage uploaded for pull request base (master@44a3267). Click here to learn what that means.
The diff coverage is 0%.

@@            Coverage Diff            @@
##             master   #38020   +/-   ##
=========================================
  Coverage          ?   37.32%           
=========================================
  Files             ?      609           
  Lines             ?    45231           
  Branches          ?        0           
=========================================
  Hits              ?    16882           
  Misses            ?    26056           
  Partials          ?     2293

@lowenna
Copy link
Member

lowenna commented Oct 12, 2018

Hold fire on this - internal testing is throwing an issue. It's being investigated.

@thaJeztah thaJeztah changed the title Remove skip evaluation of symlinks to data root on IoT Core [WIP] Remove skip evaluation of symlinks to data root on IoT Core Oct 18, 2018
@lowenna
Copy link
Member

lowenna commented Nov 14, 2018

@jiria Following on from our discussion yesterday, are you OK with this? I think it's safe now, but if you can confirm.

@jiria
Copy link
Contributor

jiria commented Nov 14, 2018

@jhowardmsft looks good to me.

@thaJeztah thaJeztah changed the title [WIP] Remove skip evaluation of symlinks to data root on IoT Core Remove skip evaluation of symlinks to data root on IoT Core Nov 14, 2018
@thaJeztah
Copy link
Member Author

rebased, and removed "WIP"

@thaJeztah
Copy link
Member Author

rebased again; @jhowardmsft @kolyshkin PTAL

This fix was added in 8e71b1e to work around
a go issue (golang/go#20506).

That issue was fixed in
golang/go@66c03d3,
which is part of Go 1.10 and up. This reverts the changes that were made in
8e71b1e, and are no longer needed.

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
@thaJeztah
Copy link
Member Author

thaJeztah commented Jul 14, 2019

Experimental failure looks to be a flaky; https://jenkins.dockerproject.org/job/Docker-PRs-experimental/45949/console

11:18:38 FAIL: docker_api_swarm_node_test.go:75: DockerSwarmSuite.TestAPISwarmNodeDrainPause
11:18:38 
11:18:38 Creating a new daemon
11:18:38 [dc139d4dd25da] waiting for daemon to start
11:18:38 [dc139d4dd25da] waiting for daemon to start
11:18:38 [dc139d4dd25da] daemon started
11:18:38 
11:18:38 Creating a new daemon
11:18:38 [d53117bd699ed] waiting for daemon to start
11:18:38 [d53117bd699ed] waiting for daemon to start
11:18:38 [d53117bd699ed] daemon started
11:18:38 
11:18:38 waited for 707.626002ms (out of 30s)
11:18:38 waited for 9.542429ms (out of 30s)
11:18:38 waited for 18.527488ms (out of 30s)
11:18:38 waited for 2.227709728s (out of 30s)
11:18:38 waited for 8.748001ms (out of 30s)
11:18:38 docker_api_swarm_node_test.go:103:
11:18:38     waitAndAssert(c, defaultReconciliationTimeout*2, reducedCheck(sumAsIntegers, d1.CheckActiveContainerCount, d2.CheckActiveContainerCount), checker.Equals, instances)
11:18:38 docker_utils_test.go:435:
11:18:38     c.Assert(v, checker, args...)
11:18:38 ... obtained int = 2
11:18:38 ... expected int = 1
11:18:38 ... output: "801028f0f936\ne5772591d4b2\n"
11:18:38 
11:18:38 waited for 1m0.063567148s (out of 1m0s)
11:18:38 [dc139d4dd25da] Stopping daemon
11:18:38 [dc139d4dd25da] exiting daemon
11:18:38 [dc139d4dd25da] Daemon stopped
11:18:38 [d53117bd699ed] Stopping daemon
11:18:38 [d53117bd699ed] exiting daemon
11:18:38 [d53117bd699ed] Daemon stopped

Daemon logs attached:

d53117bd699ed.log

time="2019-07-14T11:17:29.017856674Z" level=error msg="error in agentInit: failed to create memberlist: Could not set up network transport: failed to obtain an address: Failed to start TCP listener on \"0.0.0.0\" port 7946: listen tcp 0.0.0.0:7946: bind: address already in use"
time="2019-07-14T11:17:29.017973645Z" level=error msg="error in agentInit: failed to create memberlist: Could not set up network transport: failed to obtain an address: Failed to start TCP listener on \"0.0.0.0\" port 7946: listen tcp 0.0.0.0:7946: bind: address already in use"
time="2019-07-14T11:18:33.144068234Z" level=error msg="agent: session failed" backoff=100ms error=EOF module=node/agent node.id=vtpt9qjni2iiv4gkef4rl7c0f
time="2019-07-14T11:18:33.230004641Z" level=error msg="agent: session failed" backoff=300ms error="rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = \"transport: Error while dialing dial tcp 127.0.0.1:2477: connect: connection refused\"" module=node/agent node.id=vtpt9qjni2iiv4gkef4rl7c0f
time="2019-07-14T11:18:33.429552477Z" level=error msg="agent: session failed" backoff=700ms error="rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = \"transport: Error while dialing dial tcp 127.0.0.1:2477: connect: connection refused\"" module=node/agent node.id=vtpt9qjni2iiv4gkef4rl7c0f
time="2019-07-14T11:18:33.697972438Z" level=error msg="agent: session failed" backoff=1.5s error="rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = \"transport: Error while dialing dial tcp 127.0.0.1:2477: connect: connection refused\"" module=node/agent node.id=vtpt9qjni2iiv4gkef4rl7c0f

dc139d4dd25da.log

time="2019-07-14T11:17:28.210168437Z" level=error msg="error reading the kernel parameter net.ipv4.neigh.default.gc_thresh1" error="open /proc/sys/net/ipv4/neigh/default/gc_thresh1: no such file or directory"
time="2019-07-14T11:17:28.210183375Z" level=error msg="error reading the kernel parameter net.ipv4.neigh.default.gc_thresh2" error="open /proc/sys/net/ipv4/neigh/default/gc_thresh2: no such file or directory"
time="2019-07-14T11:17:28.210195867Z" level=error msg="error reading the kernel parameter net.ipv4.neigh.default.gc_thresh3" error="open /proc/sys/net/ipv4/neigh/default/gc_thresh3: no such file or directory"
time="2019-07-14T11:17:28.297891584Z" level=error msg="error reading the kernel parameter net.ipv4.vs.expire_nodest_conn" error="open /proc/sys/net/ipv4/vs/expire_nodest_conn: no such file or directory"
time="2019-07-14T11:17:33.046943421Z" level=error msg="failed to update task to REMOVE" error="update out of sequence" module=node node.id=owzw1jvmh1ovxpmpdut7nzyh5
time="2019-07-14T11:18:33.143549161Z" level=error msg="failed to remove node" error="rpc error: code = Aborted desc = dispatcher is stopped" method="(*Dispatcher).Session" node.id=owzw1jvmh1ovxpmpdut7nzyh5 node.session=op23nfmjvobnaek7ds3yo5o74
time="2019-07-14T11:18:33.143688555Z" level=error msg="failed to remove node" error="rpc error: code = Aborted desc = dispatcher is stopped" method="(*Dispatcher).Session" node.id=vtpt9qjni2iiv4gkef4rl7c0f node.session=13w16v5a0m1wtoni0jopeebf4
time="2019-07-14T11:18:33.144002407Z" level=error msg="failed to receive changes from store watch API" error="rpc error: code = Unknown desc = context canceled"
time="2019-07-14T11:18:33.945690551Z" level=error msg="failed to get event" error="rpc error: code = Unavailable desc = transport is closing" module=libcontainerd namespace=dc139d4dd25da

@thaJeztah
Copy link
Member Author

ok, this is rebased and green

@jhowardmsft @cpuguy83 @AkihiroSuda PTAL

Copy link
Member

@lowenna lowenna left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM @jiria FYI

Copy link
Member

@cpuguy83 cpuguy83 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@cpuguy83 cpuguy83 merged commit ffabf0d into moby:master Jul 15, 2019
@thaJeztah thaJeztah deleted the remove_iot_check branch July 15, 2019 18:14
@thaJeztah thaJeztah added this to the 20.03.0 milestone Apr 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants