ManageIQ / manageiq-automation_engine / 3827
86%
master: 86%

LAST BUILD BRANCH: jansa
DEFAULT BRANCH: master
Ran
Jobs 2
Files 181
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
3827

Pull #431

travis-ci

web-flow 
Explicitly pass a local URI for our client's DRb.start_service

While testing some workspace instantiantion at home, I was seeing this in the
logs:

```
[----] E, [2020-03-12T16:35:06.554957 #39577:3ff30d01cf44] ERROR -- : <AEMethod available_resource_groups>   DRb::DRbConnError: druby://92.242.140.21:54933 - #<Errno::ETIMEDOUT: Operation timed out - connect(2) for "92.242.140.21" port 54933>
[----] E, [2020-03-12T16:35:06.556663 #39577:3ff30d01cf44] ERROR -- : <AEMethod available_resource_groups>   (drbunix:///var/folders/bf/hh6xb_k15wbfzg4tlbkzch300000gn/T/automation_engine20200312-39577-6nm7ah) /Users/joerafaniello/.rubies/ruby-2.6.5/lib/ruby/2.6.0/drb/drb.rb:744:in `rescue in block in open'
```

Note, the drbunix:///var/folders... unix socket being reported on one side but
the druby://92.242... TCP socket reporting a timeout.  Weird.

Using verizon fios dns at home, somehow DRb resolves DRb.start_service to a remote
DRb service, which I believe happens below because we're not passing a URI so we
have no hostname from this URI and it tries to resolve the local hostname:
https://github.com/ruby/ruby/blob/v2_6_5/lib/drb/drb.rb#L879-L884

irb(main):001:0> s = DRb.start_service
irb(main):002:0> s.uri
=> "druby://92.242.140.21:51000"

Note, this is the IP adderss of verizon's DNS assistance program, as mentioned
here:
https://askubuntu.com/questions/587895/why-is-the-ip-92-242-140-21-connecting-to-one-of-my-ports-is-it-malware#comment1583793_587954

We can avoid this entirely by explicitly telling DRb to use a local URI for our
DRb client:

irb(main):001:0> s = DRb.start_service("druby://localhost:0")
irb(main):002:0> s.uri
=> "druby://localhost:51010"

We've seen this weird thing in the past where our server was using unix sockets
and the client was failing, trying to access a TCP DRb server.  The solution in
the past was to remove the TCP socket option from the server but I believe the
problem might actually have been what you see above, in the DRb cl... (continued)
Pull Request #431: Explicitly pass a local URI for our client's DRb.start_service

5104 of 5942 relevant lines covered (85.9%)

368.2 hits per line

Jobs
ID Job ID Ran Files Coverage
1 3827.1 (2.5.7, RUBY_GC_HEAP_GROWTH_MAX_SLOTS=300000 RUBY_GC_HEAP_INIT_SLOTS=600000 RUBY_GC_HEAP_GROWTH_FACTOR=1.25) 181
85.92
 Travis Job 3827.1
2 3827.2 (2.6.5, RUBY_GC_HEAP_GROWTH_MAX_SLOTS=300000 RUBY_GC_HEAP_INIT_SLOTS=600000 RUBY_GC_HEAP_GROWTH_FACTOR=1.25) 181
85.9
 Travis Job 3827.2
Source Files on build 3827