<div dir="ltr"><div>OK - turns out the compute node was not resolving names. I reset the name server on the vlan100 interface and it seems to get<br></div>pas that now<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Dec 18, 2015 at 4:53 PM, John Menke <span dir="ltr"><<a href="mailto:jmjava@gmail.com" target="_blank">jmjava@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Tailing the logs on the compute node -- seeing some failing requests to repos- will sift through that and post more info.<br></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Dec 18, 2015 at 4:00 PM, John Menke <span dir="ltr"><<a href="mailto:jmjava@gmail.com" target="_blank">jmjava@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">This should be<div><br></div><div><pre style="overflow:auto;font-family:Consolas,'Liberation Mono',Menlo,Courier,monospace;font-size:13.6px;margin-top:0px;font-stretch:normal;line-height:1.45;padding:16px;border-radius:3px;word-wrap:normal;color:rgb(51,51,51);margin-bottom:0px!important;background-color:rgb(247,247,247)"><pre style="white-space:pre-wrap;overflow:auto;font-family:Consolas,'Liberation Mono',Menlo,Courier,monospace;font-size:13.6px;margin-top:0px;font-stretch:normal;line-height:1.45;padding:16px;border-radius:3px;word-wrap:normal;margin-bottom:0px!important">interface Vlan100
ip address 192.168.1.240 255.255.255.0
ip helper-address 192.168.1.1
no shutdown
!</pre></pre></div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Dec 18, 2015 at 3:17 PM, Alex Schultz <span dir="ltr"><<a href="mailto:aschultz@mirantis.com" target="_blank">aschultz@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span>On Fri, Dec 18, 2015 at 12:52 PM, John Menke <span dir="ltr"><<a href="mailto:jmjava@gmail.com" target="_blank">jmjava@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><div><div>Alex,<br><br></div>Thanks for the reply. i was able to get around the issue. I rebooted all my instances and the mcollective error went away. <br><br></div></div></div></blockquote><div><br></div></span><div>Yes rebooting the node will restart mcollective and cause it to reconnect. So that's one way to fix it.</div><span><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><div></div><div>mco ping from fuel now returns<br><br></div><div>11 time ...<br></div><div>12 time ...<br></div><div>13 time...<br></div><div>master tim...<br></div><div><br></div>Now it's complaining that it can't hit some repos from the compute node. I logged into the compute node and can ping the<br></div>repo domains...checking the nailgun and astute logs as it's asking now.<div><div><br></div></div></div></blockquote><div><br></div></span><div>So do your compute nodes have public access to the internet with your network configuration? If not you may need to use fuel-createmirror to create a local repository mirrors. <a href="https://docs.mirantis.com/openstack/fuel/fuel-7.0/operations.html#setting-up-local-mirrors" target="_blank">https://docs.mirantis.com/openstack/fuel/fuel-7.0/operations.html#setting-up-local-mirrors</a></div><div> </div><div>Thanks,</div><div>-Alex</div><div><div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Dec 18, 2015 at 1:29 PM, Alex Schultz <span dir="ltr"><<a href="mailto:aschultz@mirantis.com" target="_blank">aschultz@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Hey John,<div><br><div class="gmail_extra"><br><div class="gmail_quote"><span>On Fri, Dec 18, 2015 at 11:15 AM, John Menke <span dir="ltr"><<a href="mailto:jmjava@gmail.com" target="_blank">jmjava@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><table style="border-spacing:0px;border-collapse:collapse;width:1130px;max-width:100%;margin-bottom:20px;color:rgb(82,89,96);font-family:'Open Sans',helvetica,arial,tahoma,verdana,sans-serif;font-size:14px;line-height:20px"><tbody><tr><td style="padding:8px;line-height:1.42857;vertical-align:top;border-top-width:1px;border-top-style:solid;border-top-color:rgb(238,238,238);white-space:nowrap;background-color:rgb(246,196,195)"><br><br><br>2015-12-17 20:49:36</td><td style="padding:8px;line-height:1.42857;vertical-align:top;border-top-width:1px;border-top-style:solid;border-top-color:rgb(238,238,238);white-space:nowrap;background-color:rgb(246,196,195)">ERR</td><td style="font-family:monospace;padding:8px;line-height:1.42857;vertical-align:top;border-top-width:1px;border-top-style:solid;border-top-color:rgb(238,238,238);white-space:pre-wrap;font-size:12.6px;background-color:rgb(246,196,195)">[566] Error running RPC method verify_networks: Network verification not avaliable because nodes ["1"] not avaliable via mcollective, trace:
["/usr/lib64/ruby/gems/2.1.0/gems/astute-7.0.0/lib/astute/orchestrator.rb:196:in `validate_nodes_access'",
"/usr/lib64/ruby/gems/2.1.0/gems/astute-7.0.0/lib/astute/orchestrator.rb:148:in `check_dhcp'",
"/usr/lib64/ruby/gems/2.1.0/gems/astute-7.0.0/lib/astute/server/dispatcher.rb:121:in `check_dhcp'",
"/usr/lib64/ruby/gems/2.1.0/gems/astute-7.0.0/lib/astute/server/dispatcher.rb:109:in `block in verify_networks'",
"/usr/lib64/ruby/gems/2.1.0/gems/astute-7.0.0/lib/astute/server/dispatcher.rb:107:in `each'",
"/usr/lib64/ruby/gems/2.1.0/gems/astute-7.0.0/lib/astute/server/dispatcher.rb:107:in `verify_networks'",
"/usr/lib64/ruby/gems/2.1.0/gems/astute-7.0.0/lib/astute/server/server.rb:146:in `dispatch_message'",
"/usr/lib64/ruby/gems/2.1.0/gems/astute-7.0.0/lib/astute/server/server.rb:107:in `block in dispatch'",
"/usr/lib64/ruby/gems/2.1.0/gems/astute-7.0.0/lib/astute/server/task_queue.rb:64:in `call'",
"/usr/lib64/ruby/gems/2.1.0/gems/astute-7.0.0/lib/astute/server/task_queue.rb:64:in `block in each'",
"/usr/lib64/ruby/gems/2.1.0/gems/astute-7.0.0/lib/astute/server/task_queue.rb:56:in `each'",
"/usr/lib64/ruby/gems/2.1.0/gems/astute-7.0.0/lib/astute/server/task_queue.rb:56:in `each'",
"/usr/lib64/ruby/gems/2.1.0/gems/astute-7.0.0/lib/astute/server/server.rb:105:in `each_with_index'",
"/usr/lib64/ruby/gems/2.1.0/gems/astute-7.0.0/lib/astute/server/server.rb:105:in `dispatch'",
"/usr/lib64/ruby/gems/2.1.0/gems/astute-7.0.0/lib/astute/server/server.rb:89:in `block in perform_main_job'"]</td></tr></tbody></table><div>I have a new Fuel 7.0 and I am experiencing this issue when i try to run verify network from the UI.</div><div><br></div><div>Steps to recreate:</div><div><br></div><div>1. Install Fuel 7 via USB - verify it has access to public internet via eth1</div><div>2. PXE boot my servers and they connect and get ips from fuel server over eth0</div><div>3. Login to Fuel UI and create a new Environment - accept all defaults</div><div>4. Provision nodes (all nodes found) using Add Node</div><div>5. Click Verify Networks on the Network Tab</div><div><br></div><div>The above message appears.</div><div><br></div><div>I have checked dockerctl list -l to make sure all the docker instances are running. Have been searching through the log files, but this is the only thing i can find so far.</div><span><font color="#888888"><div><br></div></font></span></div></blockquote><div><br></div></span><div>What is the output of 'mco ping' from the fuel master? The verification process attempts to launch commands on the remote nodes via mcollective. So if they aren't responding it will fail like this. You may also want to check the mcollective logs on node that is failing to see if it's having issues communicating with the master.</div><div><br></div><div>Also if you pop in to #fuel on freenode we can help troubleshoot further in realtime.</div><div><br></div><div>Thanks,</div><div>-Alex</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><span><font color="#888888"><div></div><div>John</div></font></span></div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div></div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div></div></div></div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div></div></div><br></div></div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>