1. Show the logfile to see the bootstrap process is finished without any errors. 2. It depends on the Fuel version, http://10.20.0.2/cobbler/boot in some cases can't be seen through the web browser. 3. You shouldn't do anything only reboot the slave node. If fuel-bootstrap executed correctly - your slave node should boot. 4. Also, there can be a problem in the VirtualBox settings, please don't touch network/interfaces and use only fuel-virtualbox scripts to configure them.
On Tue, Jun 28, 2016 at 6:28 PM, Alioune <baliou...@gmail.com> wrote: > Maksim, > The bootstrap process woks fine without error but the slave can boot from > network. > I think that the issue is due TFTP process, it tries to reach > http://10.20.0.2/cobbler/boot, I used my web browser but there is not > directory named boot in cobbler folder. > Should the bootstrap create this directory ? > > On 28 June 2016 at 15:59, Maksim Malchuk <mmalc...@mirantis.com> wrote: > >> You can start build command with debug options enabled for example and >> copy/paste output: >>> >>> fuel-bootstrap --verbose --debug build --activate >>> >> >> Very bad idea to remove logfile, it's better to empty it not remove. >> >> If you don't have the logfile, so recreate it with command: >> >>> touch /var/log/fuel-bootstrap-image-build.log >>> >> >> >> On Tue, Jun 28, 2016 at 4:09 PM, Alioune <baliou...@gmail.com> wrote: >> >>> I've removed /var/log/fuel-bootstrap-image-build.log, created new >>> bootstrap ubuntu again after setting proxy parameters and reboot. >>> After the there is no /var/log/fuel-bootstrap-image-build.log create >>> from the new bootstrap but slave doesn't boot correctly. >>> Is there another way to detect slave nodes without creating image ? >>> Regards, >>> [image: Inline images 2] >>> >>> On 28 June 2016 at 13:34, Maksim Malchuk <mmalc...@mirantis.com> wrote: >>> >>>> You have an issue with connectivity from the Fuel master node to >>>> http://archive.ubuntu.com >>>> from the log: >>>> >>>>> Command: debootstrap --include=ca-certificates,apt-transport-https >>>>> --verbose --no-check-gpg --arch=amd64 trusty >>>>> /tmp/tmp1K2haC.fuel-agent-image http://archive.ubuntu.com/ubuntu >>>>> Exit code: 1 >>>>> Stdout: 'I: Retrieving Release \nE: Failed getting release file >>>>> http://archive.ubuntu.com/ubuntu/dists/trusty/Release\n' >>>>> Stderr: '' >>>>> Failed to execute command: Unexpected error while running command. >>>>> >>>>> please check your network connectivity, maybe firewall or nat settings. >>>> >>>> >>>> On Tue, Jun 28, 2016 at 2:28 PM, Alioune <baliou...@gmail.com> wrote: >>>> >>>>> Hi all, >>>>> I tried to create ubuntu bootstrap using [0] but the slave can still >>>>> not booting. You can find the bootstrap log following [1]. >>>>> >>>>> Noticed that I've deleted the depot [2] from fuelmenu because it >>>>> generated an error "URL for repository mos is not accessible". >>>>> >>>>> Regards, >>>>> >>>>> [0] fuel-bootstrap build --ubuntu-release trusty --activate >>>>> [1] >>>>> https://drive.google.com/folderview?id=0B-bfET74f0WZWE9Uc1lVOXJLcWM&usp=sharing >>>>> [2] http://127.0.0.1:8080/ubuntu/x86_64/ mos8.0 main restricted >>>>> >>>>> On 27 June 2016 at 17:48, Maksim Malchuk <mmalc...@mirantis.com> >>>>> wrote: >>>>> >>>>>> Maybe the problem because you create the CentOS bootstrap which is >>>>>> deprecated now. >>>>>> If You really need the CentOS bootstrap, need to look into the >>>>>> mentioned log file for this issue. >>>>>> >>>>>> >>>>>> On Mon, Jun 27, 2016 at 6:33 PM, Alioune <baliou...@gmail.com> wrote: >>>>>> >>>>>>> Thanks for your response, >>>>>>> >>>>>>> I've created and activated a new centOS bootstrap as suggested Sergi. >>>>>>> Now the fuel-slave tries to boot from network but it fails at step >>>>>>> TFTP http://10.20.0.2/cobbler/boot (unable to locate configuration >>>>>>> file ). >>>>>>> The bootstrap zip was generated in >>>>>>> /tmp/a721103c-8693-4c58-985d-3f8223bdbc88.tar.gz, it seems that the >>>>>>> slave >>>>>>> can not retreive the config files of the bootstrap. >>>>>>> Are there additional config to do on the master side ? >>>>>>> Regards >>>>>>> >>>>>>> fuel-bootstrap list >>>>>>> >>>>>>> +--------------------------------------+--------------------------------------+--------+ >>>>>>> | uuid | label >>>>>>> | status | >>>>>>> >>>>>>> +--------------------------------------+--------------------------------------+--------+ >>>>>>> | a721103c-8693-4c58-985d-3f8223bdbc88 | >>>>>>> a721103c-8693-4c58-985d-3f8223bdbc88 | active | >>>>>>> | centos | deprecated >>>>>>> | | >>>>>>> >>>>>>> +--------------------------------------+--------------------------------------+--------+ >>>>>>> >>>>>>> On 27 June 2016 at 16:58, Sergii Golovatiuk < >>>>>>> sgolovat...@mirantis.com> wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> I would suggest to build image from CLI using [0]. That will give >>>>>>>> more details to you. >>>>>>>> >>>>>>>> [0] >>>>>>>> http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-install-guide/bootstrap/bootstrap_builder.html >>>>>>>> >>>>>>>> -- >>>>>>>> Best regards, >>>>>>>> Sergii Golovatiuk, >>>>>>>> Skype #golserge >>>>>>>> IRC #holser >>>>>>>> >>>>>>>> On Mon, Jun 27, 2016 at 3:20 PM, Maksim Malchuk < >>>>>>>> mmalc...@mirantis.com> wrote: >>>>>>>> >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> The error about an internet connection is the only common case. >>>>>>>>> You should check the actual error in the log file >>>>>>>>> /var/log/fuel-bootstrap-image-build.log. >>>>>>>>> You can also share this file with us via any public service >>>>>>>>> (GoogleDrive, DropBox, etc) and we will check it for you. >>>>>>>>> >>>>>>>>> On Mon, Jun 27, 2016 at 4:08 PM, Maksim Malchuk < >>>>>>>>> mmalc...@mirantis.com> wrote: >>>>>>>>> >>>>>>>>>> Hi, >>>>>>>>>> >>>>>>>>>> The error about an internet connection is the only common case. >>>>>>>>>> You should check the actual error in the log file >>>>>>>>>> /var/log/fuel-bootstrap-image-build.log. >>>>>>>>>> You can also share this file with us via any public service >>>>>>>>>> (GoogleDrive, DropBox, etc) and we will check it for you. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Mon, Jun 27, 2016 at 1:43 PM, Alioune <baliou...@gmail.com> >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> hi all, >>>>>>>>>>> >>>>>>>>>>> I'm trying to install fuel in VirtualBox, the fuel master is >>>>>>>>>>> correctly running but I'm receiving the this error on the fuel GUI: >>>>>>>>>>> >>>>>>>>>>> WARNING: Failed to build the bootstrap image, see >>>>>>>>>>> /var/log/fuel-bootstrap-image-build.log for details. >>>>>>>>>>> Perhaps your Internet connection is broken. Please fix the >>>>>>>>>>> problem and run `fuel-bootstrap build --activate`. >>>>>>>>>>> While you don't activate any bootstrap - new nodes cannot be >>>>>>>>>>> discovered and added to cluster. >>>>>>>>>>> For more information please visit >>>>>>>>>>> https://docs.mirantis.com/openstack/fuel/fuel-master/ >>>>>>>>>>> >>>>>>>>>>> The fuel server has access to internet even though it could not >>>>>>>>>>> find depots during install, I ran "yum update" and reboot but I >>>>>>>>>>> still get >>>>>>>>>>> this error. >>>>>>>>>>> I configured a fuel-slave server boot from network attached to >>>>>>>>>>> the fuel-master but the process failed also. >>>>>>>>>>> Any help please to solve this ? >>>>>>>>>>> >>>>>>>>>>> Regards, >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> __________________________________________________________________________ >>>>>>>>>>> OpenStack Development Mailing List (not for usage questions) >>>>>>>>>>> Unsubscribe: >>>>>>>>>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >>>>>>>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Best Regards, >>>>>>>>>> Maksim Malchuk, >>>>>>>>>> Senior DevOps Engineer, >>>>>>>>>> MOS: Product Engineering, >>>>>>>>>> Mirantis, Inc >>>>>>>>>> <vgor...@mirantis.com> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Best Regards, >>>>>>>>> Maksim Malchuk, >>>>>>>>> Senior DevOps Engineer, >>>>>>>>> MOS: Product Engineering, >>>>>>>>> Mirantis, Inc >>>>>>>>> <vgor...@mirantis.com> >>>>>>>>> >>>>>>>>> >>>>>>>>> __________________________________________________________________________ >>>>>>>>> OpenStack Development Mailing List (not for usage questions) >>>>>>>>> Unsubscribe: >>>>>>>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >>>>>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> __________________________________________________________________________ >>>>>>>> OpenStack Development Mailing List (not for usage questions) >>>>>>>> Unsubscribe: >>>>>>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >>>>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Best Regards, >>>>>> Maksim Malchuk, >>>>>> Senior DevOps Engineer, >>>>>> MOS: Product Engineering, >>>>>> Mirantis, Inc >>>>>> <vgor...@mirantis.com> >>>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> Best Regards, >>>> Maksim Malchuk, >>>> Senior DevOps Engineer, >>>> MOS: Product Engineering, >>>> Mirantis, Inc >>>> <vgor...@mirantis.com> >>>> >>> >>> >> >> >> -- >> Best Regards, >> Maksim Malchuk, >> Senior DevOps Engineer, >> MOS: Product Engineering, >> Mirantis, Inc >> <vgor...@mirantis.com> >> > > -- Best Regards, Maksim Malchuk, Senior DevOps Engineer, MOS: Product Engineering, Mirantis, Inc <vgor...@mirantis.com>
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev