Hi,
Same host activation flow should work on the master as well as the
management network will not be created as part of the host activation.
So reverted changes were already merged by commit
bdd8966d97e1e02e775ee6f755d0a3637a668911
For more details about host installation see:
Hi Moti,
Not sure I understand your comment about host activation flow.
commit bdd8966d97e1e02e775ee6f755d0a3637a668911 (engine: Remove mgmt
network setup from host activation) is present in our code base, but we
were not using the host activation flow.
Here's what we tried to do.
Add a
On 06/04/2013 09:52 AM, Sahina Bose wrote:
Hi Moti,
Not sure I understand your comment about host activation flow.
commit bdd8966d97e1e02e775ee6f755d0a3637a668911 (engine: Remove mgmt
network setup from host activation) is present in our code base, but we
were not using the host activation
Hi Sahina,
I was able to reproduce it on my setup, it seems that when a host was
already installed and the user re-installed it, it failed to check the
host availability.
I fixed the host polling by the engine by commit
5c03a936df3a09473f1a05b973680c02280d7a5c.
You can either build from master
Host installation went through successfully after reverting the change
eca95e192ebf3e1fe0e9440bb8fac694214ca8fd (Change Iaf82e104: engine:
Allow engine to configure management network ).
Thanks,
Kanagaraj
On 06/04/2013 12:23 AM, Dead Horse wrote:
Seeing this as well but during host activation
