Samer, you could always use `dockerctl check all|` command.
On Wed, Mar 30, 2016 at 2:47 PM, Adam Heczko wrote:
> Samer my 2c are:
> after Fuel node reboot just run 'docker ps -a' to get information if all
> containers have been already running.
>
> On Wed, Mar 30, 2016 at 1:07 PM, Samer Machara
Samer my 2c are:
after Fuel node reboot just run 'docker ps -a' to get information if all
containers have been already running.
On Wed, Mar 30, 2016 at 1:07 PM, Samer Machara <
samer.mach...@telecom-sudparis.eu> wrote:
> Thanks,
>Problem solved by magic. It looks like, the nailgun service t
Thanks,
Problem solved by magic. It looks like, the nailgun service take some time to
start up in my computer.
- Original Message -
From: "Samer Machara"
To: "OpenStack Development Mailing List"
Sent: Wednesday, March 30, 2016 12:39:35 PM
Subject: Re: [Fuel] [Openstack] Problem af
Hi Vladimir,
I'm using fuel 7.0, Which log I need to see?
- Original Message -
From: " Vladimir Kuklin vkuklin at mirantis.com
To: "OpenStack Development Mailing List"
Sent: Wed Mar 30 10:06:22 UTC 2016
Subject: [Fuel] [Openstack] Problem after reboot fuel-master VM
Hi, Samer
It se
Hi, Samer
It seems that Nailgun has not started. Could you please provide us with the
version of Fuel you are using? You can find logs for nailgun in:
for <9.0/pre-Mitaka versions
/var/log//nailgun/
for current Mitaka:
/var/log/nailgun/
On Wed, Mar 30, 2016 at 12:38 PM, Samer Machara <
samer.m
Hello,
I have rebooted the "fuel-master" VM and after that, I cannot access the Fuel
UI. What I am missing. Please check the image to see the error.
Another question, How can I rediscover a node that was removed from the pool of
available nodes, and also add new nodes to the pool. I clone a fu
