-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
/etc/iiab/uuid is never created if SD's 1st boot is in RPi Zero W #229
Comments
From what I can see a pass through 1-prep is required to recreate the uuid . I'd double check the behaviour on a freshly cloned rpi3 it should behave the same if runansible or the console has not been used yet. Fix for in the field |
@georgejhunt reminds me that xscenet@openvpn will most likely fail when the file /etc/iiab/uuid is absent. |
@georgejhunt, can you explain what auto-creates /etc/iiab/uuid during RPi3 boot, when none exists after dd / cloning? Is roles/openvpn/templates/announcer somehow involved? (As compared to the proposed approach @ PR #271 for example!) |
At one earlier time, uuid was created when admin-console gathered facts.
But Tim did not like using the fact gathering script for the purpose of
making sure that uuid existed. And at this point we do not have another
start up script that we can all agree upon. A simple place to put it would
be in rc.local -- but that has not been successful as a suggestion for this
sort of thing
I've written a PR which creates a "iiab-startup.sh" script in /usr/libexec
that is stimulated by systemd unit file. We can put the check for uuid
there.
…On Thu, Nov 23, 2017 at 12:02 PM, A Holt ***@***.***> wrote:
@georgejhunt <https://github.com/georgejhunt>, can you explain what
auto-creates /etc/iiab/uuid during RPi3 boot, when none exists after dd /
cloning?
Is roles/openvpn/templates/announcer
<https://github.com/iiab/iiab/blob/master/roles/openvpn/templates/announcer>
somehow involved?
(As compared to the proposed approach @ PR #271
<#271> for example!)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#229 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AB04HIlalk_kkaeaTI65cjKQamDlSBWgks5s5c9FgaJpZM4PRLXu>
.
|
TODO, now that PR #559 's been merged:
...can likely be abbreviated to:
|
Appears fixed: @tim-moody & @georgejhunt can you confirm? |
FYI this works in RPi3, but not in RPi Zero W.
Context: I (and others in Haiti etc) follow George's routine to "rm /etc/iiab/uuid /etc/iiab/handle" on the source image, and then use "dd" to clone IIAB to many other microSD's.
A /etc/iiab/uuid is then automatically created(*) during the first boot of each clone IF the 1st boot occurs in an RPi3.
However there appears to be a timing-or-similar bug when 1st boot occurs in an RPi Zero W machine, such that /etc/iiab/uuid is never created.
The text was updated successfully, but these errors were encountered: