Re: [Openstack] Mirantis Fuel 9.2 - nailgund not available when attempting to save changes to cloud environment

2017-04-14 Thread sil...@gmail.com
Please consider this matter closed (at least for me). We ended up replacing our the HP DL180 gen 6 controller/Fuel servers with Dell r610s and the problem is now non-existent. I'm not sure what the problem was related to however I can tell you I've received that same 'nailgun server not avail

Re: [Openstack] Mirantis Fuel 9.2 - nailgund not available when attempting to save changes to cloud environment

2017-04-05 Thread Evgeniy L
Given the fact that you can see settings tab with parameters, the error "Nailgun server is unavailable. Please check your connection and contact your system administrator." most likely means that Nailgun responded with 5xx error, which may happen because of some unhandled exception. 1. We need to

Re: [Openstack] Mirantis Fuel 9.2 - nailgund not available when attempting to save changes to cloud environment

2017-04-05 Thread sil...@gmail.com
When I attempt to save any changes to a cloud environment I've created, such as within 'Setting' changing 'Hypervisor type' in the 'Compute' setting menu from 'QEMU' to 'KVM', the save button circles for about 7-8secs and then a pop-up dialog box comes up that says: OpenStack Settings Configur

Re: [Openstack] Mirantis Fuel 9.2 - nailgund not available when attempting to save changes to cloud environment

2017-04-05 Thread Evgeniy L
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:

[Openstack] Mirantis Fuel 9.2 - nailgund not available when attempting to save changes to cloud environment

2017-04-03 Thread sil...@gmail.com
Has anyone had a problem with Mirantis Fuel giving a 'nailgund not available' error when attempting to save any changes to a cloud environment? I'm encountering this problem after a fresh install of Mirantis Fuel 9.0 and then immediately upgrading to 9.2 (didn't even login to the Fuel web inte