>
> > What if user choose CentOS bootstrap? We ship it on ISO, so why do
> > we need to show error message?
>
> CentOS bootstrap still is not activated
>
Its pretty simple case-flow:
If selected ubuntu:
- Try build
-- Notify if build and activate fail
-- Notify if build and activate ok
If sel
> Bootstrap building *is* a part of master node deployment.
Not always, user can set flag `skip_default_img_build` then building
bootstrap will not executed.
> If you guys show "deployment is successful" before running building
bootstrap,
> then it's something you have to fix.
fuel-bootstrap-cli
> As I already told deployment was finished, but bootstrap wasn't built.
Bootstrap building *is* a part of master node deployment. If you guys
show "deployment is successful" before running building bootstrap,
then it's something you have to fix.
> Fuel deploying => WebUI blocked => deployment
> We keep it As Is, and say "user should not use Fuel until Fuel
> Master deployment is finished".
Yep deployment can be finished, but was it successful? As I already told
deployment was finished, but bootstrap wasn't built. Command for building
bootstrap wasn't called because of some reason.
> W
> I really don't like setting the error message as the default one in
> the DB schema and consider it as a last resort solution. If
> possible update the message to error one just before you start
> to build the image.
+1.
> What about add some check or some message
> "Fuel-master Deployment in p
Actually, its gloval problem :
UI accessible for user *earlier* then deployment has been done. I think we
should also handle this somehow - otherwise user can start doing "some
things" like spawning HW - and fail .
What about add some check or some message "Fuel-master Deployment in
progress, plea
Hi,
I really don't like setting the error message as the default one in the DB
schema and consider it as a last resort solution. If possible update the
message to error one just before you start to build the image.
2015-12-15 18:48 GMT+03:00 Artur Svechnikov :
> Hi folks,
> Recently was introduc
