No network interfaces found GIT 4724

[Marcus Allen]

Using github’s 4724 version, we are no longer able to image. PXE boots, we choose quick image, and the next screen tells us: no network interfaces found

This worked up until the upgrade. Just curious what may have caused this. My snapshot didnt save properly somehow, so I don’t have the ability to go back unfortunately.

Just curious if anyone has any ideas on where to start.

EDIT:
Forgot to include that it is CentOS7 and worked fine prior to the upgrade. I’m trying to figure out which version we had before.

[Marcus Allen]

@Tom-Elliott said:

If you don’t mind opening a separate thread please regarding this now new issue. With the new thread can you post the fog servers Apache error logs?

No problem: https://forums.fogproject.org/topic/5822/checking-in-error-on-git-7428

Thanks for your help again!

[Tom Elliott]

@Marcus-Allen said:

Hey Tom! Thanks for helping with this. We dont get that error anymore and now get a “Checking in… that just keeps counting” Any ideas on that? I rebooted FOG as well.

If you don’t mind opening a separate thread please regarding this now new issue. With the new thread can you post the fog servers Apache error logs?

[Marcus Allen]

Hey Tom! Thanks for helping with this. We dont get that error anymore and now get a “Checking in… that just keeps counting” Any ideas on that? I rebooted FOG as well.

[Tom Elliott]

Please upgrade again.

I know you just did it this morning.

There was a bug I found in the underlying building infrastructure that the builders of buildroot have deprecated. This mean the the original methods I had in place to produce our needed initd scripts and inittab were being overwritten.

Because of the overwriting I filed a bug with Buildroot. They reported back that using the system/skeleton method as I was doing was deprecated and that we should use the rootfs layover. I have since done this and all appears to be properly working.

Sorry about the issue being presented in the first place, but I assure you it was completely unintentional. I had already fixed the inittab issue, but I overlooked the /etc/init.d directory.