15 Mar
2018
15 Mar
'18
9:53 p.m.
Well damn, Bruno... Horrible and ugly as this may sound, glad I wasn't the
only one. But why did nobody seem to have any clue of the issue? I've been
struggling with this for weeks now, and chatting about it for over a week,
and nobody seemed to be aware of what you and I experienced with the chef
builds. I was very clear about the fact that I was building from chef, and
nobody said a word about it being a known issue.
I VERY much agree, that the chef server should either be taken offline, or
at the VERY LEAST no longer linked from the main page of libremesh.org,
until these issues have been resolved.
Hopefully by experience (and publicizing of it) will get the ball rolling
in the right direction, on that.
On Thu, Mar 15, 2018 at 2:54 PM, bruno vianna <bruno(a)pobox.com> wrote:
In the end, the solution came from installing an image on each directly
downloaded from libremesh.org, instead of built
on the chef server.
Seems the chef server is building them broken.
We had the same experience at the installations we've made. IMHO, the new
chef should be off-line until these issues are worked out. It's been
creating a frustrating experience for many users.
On the other hand, the lime-sdk cooker script is working really well.
Bruno
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users