Sure. Will check this doc and follow the same.
Thanks Evgeniy, for the update.
Regards,
Raja.
On 25 October 2017 at 22:08, Evgeniy L wrote:
> Raja,
>
> From what I see, it looks like you have a problem with connectivity to the
> repositories (first fail it could not do "apt-get update" within
Raja,
>From what I see, it looks like you have a problem with connectivity to the
repositories (first fail it could not do "apt-get update" within timeout)
there are multiple ways you can solve it not to have such problems in the
future, e.g. mirror all external repositories to Fuel Master node.
One more trial, and it completed successfully this time.
May be it was building it incrementally, and timing out at some point every
time, until everything fell in place finally.
That was just a guest.
Thanks Evgeniy, for the support. Please do let me know if you get any more
hint from the logs I
>>That was just a guest.
Please read the above as ``That was just a guess.''
Regards,
Raja.
On 25 October 2017 at 16:20, Raja T Nair wrote:
> One more trial, and it completed successfully this time.
>
> May be it was building it incrementally, and timing out at some point
> every time, until
Tried once again, this time its a different error:
*Error*
Deployment has failed. All nodes are finished. Failed tasks:
Task[top-role-compute/3], Task[top-role-compute/2],
Task[top-role-compute/5], Task[top-role-compute/4] Stopping the deployment
process!
I don't know if I should continue doing th
Hello All,
I tried deploying again, without making any change.
It went past the 42% mark where it was stuck last time, and after around 2
hours, errored out again, with the following message:
*Error*
Deployment has failed. All nodes are finished. Failed tasks:
Task[primary-keystone/1] Stopping th
Thanks Evgeniy, for the support.
I ran the command on shell, and it immediately came out, leaving a line in
the logfile which said that all required images are present.
After this I re-ran the deployment. It went past the point, but errored
out, with the following info on the dashboard:
Error
Dep
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
Hello All,
We are trying to deploy one environment using Fuel 9.2, and it failed at
around 23%.
The error says:
<>
Error
Provision has failed. Failed to execute hook 'shell'
command: cd / && fa_build_image --image_build_dir /var/lib/fuel/ibp
--log-file /var/log/fuel-agent-env-1.log --data_drive
Thanks for the reply, John.
The issue is resolved now. As I told in my previous mail, I had only
completed the installation and fuelmenu setup.
Had not run this script: /usr/sbin/bootstrap_admin_node.sh
Once I completed this step, nginx started listening and now webUI is
accessible.
I used this i
Is nginx running?
On Tue, Oct 17, 2017 at 8:31 AM, Raja T Nair wrote:
> Hello All,
>
> I downloaded the latest Mirantis Openstack iso from the website and
> installed it as a virtualbox vm.
>
> Installation went through without any issue. the VM can communicate to the
> outside world using given
Hello All,
I downloaded the latest Mirantis Openstack iso from the website and
installed it as a virtualbox vm.
Installation went through without any issue. the VM can communicate to the
outside world using given IP: 10.10.31.2/24
But the web UI is not accessible. When I try to access it through
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
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
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
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:
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
Hi Guillermo, Adam,
while itself Fuel is open source technology [1], it still uses OpenStack
packages provided by Mirantis by default. Packages contain some fixes which
are required to ensure HA and some other defects which are not yet merged
in upstream (but we are actively pushing those).
It is
In a word, no. My experience has been that Fuel really is a Mirantis
product. Their distro, their support. Folks used to be able to install
RedHat RDO if they had access to a satellite server but no longer.
But that's how a lot of packages are these days. Ubuntu JujJu, SUSE Cloud
v4. RedHat RDO, V
Hello Everyone,
I am doing some research about Fuel, but I have a big doubt and seems there
is not a clear answer in the documents I have been reading. I dont want to
waste my time doing an installation to discover after that Fuel only
supports The OPenstack Mirantis Distribution.
So, the questio
20 matches
Mail list logo
