I'm not sure if these options should be set, because they are required only
if PXE server is on different host from DHCP server, which is not the case
for Fuel.
On Thu, Oct 26, 2017 at 8:25 AM, Ken Houle
wrote:
> Evgeniy L:
>
>
>
> Thank you for the information. I have a
lled, but a different version i think:
> root@node-4:~# dpkg -l fuel-ha-utils
> Desired=Unknown/Install/Remove/Purge/Hold
> | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/
> trig-aWait/Trig-pend
> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> ||/ Name
Hi,
fuel_pkgs/9 means that "fuel_pkgs" task failed on node with id 9, find the
node with this id using "fuel node" (run it from Fuel node), ssh to the
nodes and look for errors in /var/log/puppet.log.
If Nova service was running before, it should be running even after
fuel_pkgs task failed on one
Hi Ken,
Fuel uses Cobbler which uses DNSMasq to provide DHCP and PXE boot, if the
issue is hardware specific, you can try to search if anybody else had such
problems with DNSMasq PXE boot and similar hardware.
Thanks,
On Wed, Oct 25, 2017 at 7:12 AM, Ken Houle
wrote:
> All:
>
>
>
> First off n
evels) in run'
>>>>> 2017-10-24 17:13:43ERR(/Stage[main]/Apt::Update/Exec[apt_update])
>>>>> /usr/lib/ruby/vendor_ruby/puppet/util/execution.rb:186:in `execute'
>>>>> 2017-10-24 17:13:43ERR(/Stage[main]/Apt::Update/Exec[apt_update])
>>&g
Hi,
Yes, execution expired, means that it could not build an image within
required period of time.
The message you see can be used to build an image (copy paste into console
"command"), also there is a file with logs /var/log/fuel-agent-env-1.log,
which you can use to try to identify where the pro
Hi Jim,
It's possible to change the amount of space required for base system, but
it will require to change partitioning schema in release model.
You can retrieve it from Nailgun using:
curl -H "X-Auth-Token: $(fuel token)"
http://172.29.194.19:8000/api/v1/releases// | python -m
json.tool > rel.j
Hi,
Try following this guide:
https://docs.mirantis.com/openstack/fuel/fuel-7.0/operations.html#howto-backup-and-restore-fuel-master
Thanks,
On Sun, Sep 24, 2017 at 11:57 PM, Raja T Nair wrote:
> Hello All,
>
> Can somebody help me with info on how to migrate OR backup/restore fuel
> server to
Hi,
I've never tried installing 11 version, but this looks suspicious:
fuelmenu=10.0.0
I think it should be version 11, not 10.
Thanks,
On Thu, Sep 21, 2017 at 9:30 AM, Tomas Brännström <
tomas.a.brannst...@tieto.com> wrote:
> Hi
> I'm trying to install the Fuel 11 release in a Virtualbox VM,
l settings on a Dell
> r610 server.
>
> I checked all of the logs in /var/log/nailgun and none of them indicate
> any errors that I can see. There are also plenty of nailgun related
> processes running on the Fuel server.
>
> On 04/05/2017 10:14 AM, Evgeniy L wrote:
>
>&g
Hi,
Could you please elaborate on the issue? What do you see after reset? How
does consequent deployment fail?
Thanks,
On Tue, Apr 4, 2017 at 10:32 PM, Waqas Riaz wrote:
> Hi,
>
> Does anyone know why Fuel's Reset Environment feature never works?
> The deployment after a reset always fails. I'
Hi,
Could you please clarify, do you receive this error in the UI? What do you
mean by "save any changes"?
I'm not sure if ranges can cause such behavior, please see logs
"/var/log/nailgun/app.log" and "/var/log/nailgun/api.log" for any
errors/python tracebacks.
Thanks,
On Mon, Apr 3, 2017 at 8:
es 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" wrote:
>
>> The repository contains packages important for OpenStack installation, as
>> an option I can suggest to create a mirr
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
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
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, pra
Hi,
There is a parameter reboot_timeout in /etc/astute/astuted.conf file on
Fuel node.
But there were some changes in provisioning process in latest versions, so
I'm not 100% sure that it will help.
Thanks,
On Fri, Mar 17, 2017 at 8:33 AM, Vimal Kumar wrote:
> 2017-03-17 15:31:56 ERROR [1236]
ur and I'm very limited by my remote-access
> technology in terms of copy-pasting things. If you really need additional
> feedback, I'll do my best to give you the full output)
>
>
> Regards
> --
> *De :* Evgeniy L
> *Envoyé :* 10 février 2
hat, rebuild the new bootstrap and environment images, then driver
> successfully updated.
>
> Thanks for the advice, really appreciate!
>
> Eddie.
>
> 2017-02-11 6:25 GMT+08:00 Evgeniy L :
>
>> You have several options:
>> 1. Build new repository and configure you
er_web
> > WSGIPassAuthorization On
>
>
> At this point, I am rather clueless and am starting to wonder if I am not
> breaking the OS further by stabbing in the dark. I wonder if this is
> leading anywhere, or whether I should just restart the Fuel installation
> from the Cent
Hi Gregory,
What version of Fuel do you use?
I'm not that familiar with openstack puppet library, can help only with
last question, you can override parameters using fuel Nailgun extension
which allows to override settings generated by Nailgun [1], these changes
can be applied by redeploying the
that inside a Fuel Master node. And add package name into
> the installation list so that DKMS module will install during bootstrap
> image or environment image build.
>
> Is that feasible?
>
> Thanks,
> Eddie.
>
> 2017-02-08 2:18 GMT+08:00 Evgeniy L :
>
>> Hi,
>&g
Hi,
Bootstrap image is used only when node is in discovery state (before
provisioning is done), when you send nodes for provisioning, Fuel builds an
image using repository from environment configuration, after the image is
built, it reuses it for future deployments you can find details in
document
Hi,
Try to access UI using "curl" from your machine and from Fuel Master:
1. If it's not available from your machine but available from Fuel Master,
make sure that your network is configured correctly use regular
troubleshooting techniques for that ping/traceroute/tcpdump.
2. If it's not available
Hi Russel,
Sorry for late response, there are different types of errors in 8.0 Fuel
(nodes->error_type field in db), if error caused by provisioning, those
nodes which have state=error, error_type=provision, will be re-provisioned,
with possible data lose, those node which failed to deploy state=e
25 matches
Mail list logo
