Could you please elaborate on what is "services"? Do you want to assign additional roles to already deployed node?
On Thu, Mar 30, 2017 at 11:12 PM, pratik dave <prtkd...@gmail.com> wrote: > Thanks I have created a mirror and deployment done successfully. > > One more thing can we add more services to already added nodes? > > Or we have to scale down add services and again scale up? > > On Mar 30, 2017 9:12 PM, "Evgeniy L" <e...@mirantis.com> wrote: > >> The repository contains packages important for OpenStack installation, as >> an option I can suggest to create a mirror of the repository on Fuel Master >> [1]. >> >> Thanks, >> >> [1] https://docs.openstack.org/developer/fuel-docs/userdocs/ >> fuel-install-guide/local-repo.html >> >> On Wed, Mar 29, 2017 at 11:23 PM, pratik dave <prtkd...@gmail.com> wrote: >> >>> Hi, >>> >>> Otherwise if you can help to configure repository for this would be >>> grateful. >>> >>> Thanks >>> >>> On Mar 30, 2017 11:23 AM, "pratik dave" <prtkd...@gmail.com> wrote: >>> >>>> Hi, >>>> >>>> Thank you so much for your inputs , we could able to resolve the issue. >>>> >>>> Now, We are able to setup controller node successfully. However we are >>>> getting below error in compute node. >>>> >>>> *2017-03-29 16:32:45 ERR ERROR: Unable to fetch url >>>> 'http://mirror.fuel-infra.org/mos-repos/ubuntu/9.0/ >>>> <http://mirror.fuel-infra.org/mos-repos/ubuntu/9.0/>', error 'No route to >>>> host - connect(2)'. * >>>> *Please verify node connectivity to this URL, or remove it from the >>>> settings page if it is invalid. on node node-22.domain.tld* >>>> >>>> Looking at the error we felt server is not able to reach internet to >>>> download some repos. We have already provided Public domain interface for >>>> compute but we could see we do not get any route for it. >>>> >>>> *root@node-22:~# ip route* >>>> *default via 192.168.0.3 dev br-mgmt* >>>> *10.20.0.0/24 <http://10.20.0.0/24> dev br-fw-admin proto kernel >>>> scope link src 10.20.0.4* >>>> *unreachable 169.254.169.254 scope host* >>>> *192.168.0.0/24 <http://192.168.0.0/24> dev br-mgmt proto kernel >>>> scope link src 192.168.0.5* >>>> *192.168.1.0/24 <http://192.168.1.0/24> dev br-storage proto kernel >>>> scope link src 192.168.1.3* >>>> >>>> Default route goes to br-mgmt which is tagged vlan and does not go to >>>> internet. Public interface does not come up for compute node where >>>> controller node br-ex takes that IP and connects to internet. >>>> >>>> It is asking to remove from settings if it doesn't require, can we >>>> remove that from settings? >>>> >>>> Please suggest. >>>> >>>> Thanks. >>>> >>>> On Mar 29, 2017 11:16 PM, "Evgeniy L" <e...@mirantis.com> wrote: >>>> >>>>> Look like default gateway (*10.144.243.129*) from node, where puppet >>>>> failed is not available . >>>>> >>>>> On Tue, Mar 28, 2017 at 1:42 AM, pratik dave <prtkd...@gmail.com> >>>>> wrote: >>>>> >>>>>> Hello Everyone, >>>>>> >>>>>> I am still stuck with this issue. >>>>>> >>>>>> As it looks like network config issue would like to explain how I >>>>>> configured my network configuration here. >>>>>> >>>>>> We have fuel master node with two NIC. >>>>>> >>>>>> NIC1- Connected to Public network(vlan1120 ) >>>>>> NIC1- Connected for PXE boot(PG_OSP4NET) >>>>>> >>>>>> We have fuel controller and fule compute nodes with 3 NICs. >>>>>> >>>>>> NIC1- VLAN1120 >>>>>> NIC2- test-vlan1120 >>>>>> NIC3- PG_OSP4NET >>>>>> >>>>>> ############################### >>>>>> >>>>>> Now in network configuration tab I have three parts like PXE admin, >>>>>> storage and management. >>>>>> >>>>>> I am not touching anything on storage and management just changing >>>>>> public network with my vlan1120 network range. >>>>>> >>>>>> One more thing observed is if I use vlan tagging it goes ahead and >>>>>> gives me error as 'No route to host for compute node' >>>>>> >>>>>> Any help on this would be appropriated. >>>>>> >>>>>> On Mar 27, 2017 11:28 PM, "pratik dave" <prtkd...@gmail.com> wrote: >>>>>> >>>>>>> Dear Evgeniy, >>>>>>> >>>>>>> I have got below puppet logs from dashboard of fuel. >>>>>>> >>>>>>> Could you please help me to resolve the issue and make my Mirantis >>>>>>> OpenStack environment run successfully? >>>>>>> >>>>>>> Below are logs: >>>>>>> >>>>>>> ------------------------------------------------------------ >>>>>>> -------------- >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> (/Stage[main]/Osnailyfacter::Netconfig::Netconfig/Ping_host[10.144.243.129]/ensure) >>>>>>> change from down to up failed: Timeout waiting for host '10.144.243.129' >>>>>>> status to become 'up' after 60 seconds!* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR /usr/bin/puppet:8:in `<main>'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> /usr/lib/ruby/vendor_ruby/puppet/util/command_line.rb:92:in `execute'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> /usr/lib/ruby/vendor_ruby/puppet/util/command_line.rb:146:in `run'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> /usr/lib/ruby/vendor_ruby/puppet/application.rb:381:in `run'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> /usr/lib/ruby/vendor_ruby/puppet/util.rb:496:in `exit_on_fail'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> /usr/lib/ruby/vendor_ruby/puppet/application.rb:381:in `block in run'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> /usr/lib/ruby/vendor_ruby/puppet/application.rb:507:in `plugin_hook'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> /usr/lib/ruby/vendor_ruby/puppet/application.rb:381:in `block (2 >>>>>>> levels) in >>>>>>> run'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> /usr/lib/ruby/vendor_ruby/puppet/application/apply.rb:159:in >>>>>>> `run_command'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> /usr/lib/ruby/vendor_ruby/puppet/application/apply.rb:198:in `main'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR /usr/lib/ruby/vendor_ruby/puppet.rb:246:in >>>>>>> `override'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> /usr/lib/ruby/vendor_ruby/puppet/context.rb:64:in `override'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> /usr/lib/ruby/vendor_ruby/puppet/application/apply.rb:236:in `block in >>>>>>> main'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> /usr/lib/ruby/vendor_ruby/puppet/application/apply.rb:302:in >>>>>>> `apply_catalog'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> /usr/lib/ruby/vendor_ruby/puppet/configurer.rb:133:in `run'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR /usr/lib/ruby/vendor_ruby/puppet.rb:246:in >>>>>>> `override'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> /usr/lib/ruby/vendor_ruby/puppet/context.rb:64:in `override'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> /usr/lib/ruby/vendor_ruby/puppet/configurer.rb:134:in `block in run'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> /usr/lib/ruby/vendor_ruby/puppet/configurer.rb:227:in `run_internal'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> /usr/lib/ruby/vendor_ruby/puppet/configurer.rb:119:in `apply_catalog'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> /usr/lib/ruby/vendor_ruby/puppet/util.rb:160:in `benchmark'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR /usr/lib/ruby/1.9.1/benchmark.rb:295:in >>>>>>> `realtime'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> /usr/lib/ruby/vendor_ruby/puppet/util.rb:161:in `block in benchmark'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> /usr/lib/ruby/vendor_ruby/puppet/configurer.rb:120:in `block in >>>>>>> apply_catalog'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> /usr/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:168:in `apply'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> /usr/lib/ruby/vendor_ruby/puppet/transaction/report.rb:112:in >>>>>>> `as_logging_destination'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> /usr/lib/ruby/vendor_ruby/puppet/util/log.rb:149:in `with_destination'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> /usr/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:169:in `block in >>>>>>> apply'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> /usr/lib/ruby/vendor_ruby/puppet/transaction.rb:138:in `evaluate'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> /usr/lib/ruby/vendor_ruby/puppet/graph/relationship_graph.rb:118:in >>>>>>> `traverse'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> /usr/lib/ruby/vendor_ruby/puppet/transaction.rb:147:in `block in >>>>>>> evaluate'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> /usr/lib/ruby/vendor_ruby/puppet/util.rb:334:in `thinmark'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR /usr/lib/ruby/1.9.1/benchmark.rb:295:in >>>>>>> `realtime'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> /usr/lib/ruby/vendor_ruby/puppet/util.rb:335:in `block in thinmark'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> /usr/lib/ruby/vendor_ruby/puppet/transaction.rb:147:in `block (2 >>>>>>> levels) in >>>>>>> evaluate'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> /usr/lib/ruby/vendor_ruby/puppet/transaction.rb:147:in `call'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> /usr/lib/ruby/vendor_ruby/puppet/transaction.rb:217:in `eval_resource'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> /usr/lib/ruby/vendor_ruby/puppet/transaction.rb:204:in `apply'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> /usr/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:20:in >>>>>>> `evaluate'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> /usr/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:81:in >>>>>>> `perform_changes'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> /usr/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:128:in >>>>>>> `sync_if_needed'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> /usr/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:204:in >>>>>>> `sync'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> /usr/lib/ruby/vendor_ruby/puppet/property.rb:581:in `sync'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> /usr/lib/ruby/vendor_ruby/puppet/property.rb:503:in `set'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> /usr/lib/ruby/vendor_ruby/puppet/property.rb:178:in `call_provider'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> /etc/puppet/modules/osnailyfacter/lib/puppet/provider/ping_host/ping_host.rb:38:in >>>>>>> `ensure='* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR >>>>>>> /usr/lib/ruby/vendor_ruby/puppet/util/errors.rb:106:in `fail'* >>>>>>> >>>>>>> *2017-03-27 17:18:57 ERR Timeout waiting for host '10.144.243.129' >>>>>>> status to become 'up' after 60 seconds!* >>>>>>> >>>>>>> ------------------------------------------------------------ >>>>>>> -------------- >>>>>>> >>>>>>> On Mar 27, 2017 10:12 PM, "pratik dave" <prtkd...@gmail.com> wrote: >>>>>>> >>>>>>>> Hi Evgeniy, >>>>>>>> >>>>>>>> Thanks for your reply. >>>>>>>> >>>>>>>> I went to /var/log bt I could not find puppet.log anywhere. Is it >>>>>>>> possible for you to guide? >>>>>>>> >>>>>>>> Please refer below screenshot. >>>>>>>> >>>>>>>> On Mar 27, 2017 9:23 PM, "Evgeniy L" <e...@mirantis.com> wrote: >>>>>>>> >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> *netconfig* task is responsible for network configuration. >>>>>>>>> *21* - specifies a node id, where task failed, use `fuel node | >>>>>>>>> grep 21` to find ip address of the node, go to the node using ssh and >>>>>>>>> see >>>>>>>>> results of puppet execution "/var/log/puppet.log". >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> >>>>>>>>> On Mon, Mar 27, 2017 at 7:56 AM, pratik dave <prtkd...@gmail.com> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Hi, >>>>>>>>>> >>>>>>>>>> I am trying to deploy openstack ubuntu using FUEL 9.0. >>>>>>>>>> >>>>>>>>>> I am adding 2 nodes and selecting controller and compute+cinder; >>>>>>>>>> i am getting below eeror on controller node while openstack >>>>>>>>>> deployment. >>>>>>>>>> >>>>>>>>>> *13:17:11* >>>>>>>>>> >>>>>>>>>> *Deployment has failed. All nodes are finished. Failed tasks: >>>>>>>>>> Task[netconfig/21] Stopping the deployment process!* >>>>>>>>>> >>>>>>>>>> *13:17:11* >>>>>>>>>> >>>>>>>>>> *Failed to deploy node 'Untitled (b1:04)': Unknown error* >>>>>>>>>> >>>>>>>>>> Any help on this would be appriciated. >>>>>>>>>> >>>>>>>>>> Thanks. >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Mailing list: http://lists.openstack.org/cgi >>>>>>>>>> -bin/mailman/listinfo/openstack >>>>>>>>>> Post to : openstack@lists.openstack.org >>>>>>>>>> Unsubscribe : http://lists.openstack.org/cgi >>>>>>>>>> -bin/mailman/listinfo/openstack >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>> >>
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack