search

dxc-technology / Hanlon-Microkernel

A small (in-memory) Microkernel used by the Hanlon server for discovery of new nodes
Other
20 stars 21 forks source link

error:: Missing metadata file for microkernel #8

Closed sankarvema closed 10 years ago

sankarvema commented 10 years ago

Created a debug mk and everything went on well without issue. But when I am trying to add the mk to hanlon is gives error

error:: Missing metadata file '/home/user/wspace/ohan/129a-issue-fix/image/mk/3xNWGVYNLBds5ozkt8kZdc/iso-metadata.yaml'

tjmcs commented 10 years ago

I need to understand better what you are doing here. Are you building a debug instance of the standard MK from this project? If not, how have you modified it? If it's the former, this sounds more like a Hanlon issue than a Hanlon-Microkernel issue. If it's the latter, this sounds more like an issue with how you built your custom MK. In either case, more detail is needed to sort the problem out (perhaps the custom MK itself? at a minimum a more complete description of how your MK was built)...

sankarvema commented 10 years ago

@tjmcs I tried adding the production mk from Hanlon releases. That is working fine. Getting issue with the debug build prepared by me

sankarvema commented 10 years ago

@tjmcs When i compare new mk iso with the production image i see metadata yaml missing in the debug iso

sankarvema commented 10 years ago

It turns out that I was missing couple of tools (advdef, 7zip) on my machine. Also I was running as non root user with sudo with no ruby available at root. With all these build_initial_directories.sh and rebuildiso.sh were failing.

Installing advdef, 7zip and fakeroot solved the issue. I am able to build the mk as non root user.

Thanks @tjmcs

tjmcs commented 10 years ago

No worries, @sankarvema; glad it was easy (relatively) to resolve this issue. As an aside, the other change we had to make to your system to get things building successfully was to get the fakeroot package installed so that you could run the first shell script in the bundle build process under that (the command was something like fakeroot ./build_initial_directories.sh if I remember correctly). Without the fakeroot command, that shell script failed to execute with a bunch of errors due to attempts to run the cpio command as a non-root user.