Manual ISO build error

78 views
Skip to first unread message

Nate Adcock

unread,
Sep 16, 2016, 12:56:07 PM9/16/16
to SIMP Q&A Forum
Hi, when manually building SIMP 5.1.X or 5.2.X with CentOS7, getting a puppetfile.tracking error (no such file or dir) and rake aborts. I followed the Setting up and building SIMP pages, so not sure what is wrong. Seems like it created all the proper build paths and bins, etc. See sreenshot...thanks in advance.
CaptureRAKEError.PNG

Trevor Vaughan

unread,
Sep 16, 2016, 1:26:01 PM9/16/16
to Nate Adcock, SIMP Q&A Forum
Which branch did you check out in simp-core?

Could you provide the git hashref?

Thanks,

Trevor

On Fri, Sep 16, 2016 at 12:56 PM, Nate Adcock <nate...@gmail.com> wrote:
Hi, when manually building SIMP 5.1.X or 5.2.X with CentOS7, getting a puppetfile.tracking error (no such file or dir) and rake aborts. I followed the Setting up and building SIMP pages, so not sure what is wrong. Seems like it created all the proper build paths and bins, etc. See sreenshot...thanks in advance.

--
You received this message because you are subscribed to the Google Groups "SIMP Q&A Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to simp+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/simp/a71ee6de-7f2d-4149-b92b-8a75355f2f6b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Trevor Vaughan
Vice President, Onyx Point, Inc

-- This account not approved for unencrypted proprietary information --

Nate Adcock

unread,
Sep 19, 2016, 12:55:10 PM9/19/16
to SIMP Q&A Forum, nate...@gmail.com
Thanks for the response... 5.1.X. I was able to get around this error by copying the puppetfile.tracking to the build directory, however the build is still aborting with an error that could not find any module dirs in the puppetfile.tracking. I updated the module directory in the .tracking file to an absolute path (i.e. /home/simp/simp-core/src/puppet/modules, etc.), but those directories were not there (i.e.modules or gemfiles). I created them but still getting the same error.


On Friday, September 16, 2016 at 1:26:01 PM UTC-4, Trevor Vaughan wrote:
Which branch did you check out in simp-core?

Could you provide the git hashref?

Thanks,

Trevor
On Fri, Sep 16, 2016 at 12:56 PM, Nate Adcock <nate...@gmail.com> wrote:
Hi, when manually building SIMP 5.1.X or 5.2.X with CentOS7, getting a puppetfile.tracking error (no such file or dir) and rake aborts. I followed the Setting up and building SIMP pages, so not sure what is wrong. Seems like it created all the proper build paths and bins, etc. See sreenshot...thanks in advance.

--
You received this message because you are subscribed to the Google Groups "SIMP Q&A Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to simp+uns...@googlegroups.com.

Trevor Vaughan

unread,
Sep 19, 2016, 1:09:27 PM9/19/16
to Nate Adcock, SIMP Q&A Forum
Hi Nate,

What directory are you in, and what exact command are you running to attempt the build?

Thanks,

Trevor

To unsubscribe from this group and stop receiving emails from it, send an email to simp+unsubscribe@googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/msgid/simp/38cb1ab7-a841-4a7b-8985-282482d3b877%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Nate Adcock

unread,
Sep 19, 2016, 1:16:20 PM9/19/16
to SIMP Q&A Forum, nate...@gmail.com
I am building in /tmp/CentOS_Build/centos7build. One dir up is where the "orig" bundles are (I am trying to build rake with CentOS7). I am running the build per instruction:

BUNDLE_GEMFILE=/path/to/simp-core/Gemfile rake -f /path/to/simp-core/Rakefile iso:build["/path/to/simp-core/build/DVD_Overlay/SIMP-DVD-CentOS-4.2.0-RC1.tar.gz"]

whereby in my case path to /simp-core is /home/simp/simp-core, and the DVD overlay is version 5.2.2...

Trevor Vaughan

unread,
Sep 19, 2016, 1:57:10 PM9/19/16
to Nate Adcock, SIMP Q&A Forum
Ugh...and, once again, we find out that our docs need to be updated!

Can you try: BUNDLE_GEMFILE=/path/to/simp-core/Gemfile rake -f /path/to/simp-core/Rakefile build:auto[5.1.X,/dir/with/ISOs,/path/to/simp-core/build/DVD_Overlay/SIMP-DVD-CentOS-4.2.0-RC1.tar.gz]

I'm fundamentally beginning to think that the most difficult part of a FOSS project is the documentation.

Thanks,

Trevor


To unsubscribe from this group and stop receiving emails from it, send an email to simp+unsubscribe@googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/msgid/simp/3dcff452-16e7-4ad0-9816-ffb650ba31d0%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Nate Adcock

unread,
Sep 19, 2016, 2:28:47 PM9/19/16
to SIMP Q&A Forum, nate...@gmail.com
LOL, docs is a never-ending battle, agreed. I ran the command, and attached the output (see end of Build Error file), and also my puppet.tracking file. It went through basically the same exercise, and built a new dir called SIMP_ISO_STAGING with all the packages, however can't find an actual ISO, and it appears the same error about puppet was produced (module dir issue)...
CentOS7Package Build Errors
Puppetfile.tracking

Trevor Vaughan

unread,
Sep 19, 2016, 4:21:11 PM9/19/16
to Nate Adcock, SIMP Q&A Forum
Well, that's certainly unexpected.

Can you try running the command from the 'simp-core' directory as just `rake build:auto[5.1.X,/dir/with/ISOs,/path/to/simp-core/build/DVD_Overlay/SIMP-DVD-CentOS-4.2.0-RC1.tar.gz]`

It may be that we have inadvertently bound ourselves to the current directory incorrectly at some point.

If you want to know *exactly* how we build it, you can see this test file https://github.com/simp/simp-core/blob/5.1.X/spec/acceptance/suites/default/00_iso_build_spec.rb#L135

Thanks,

Trevor

To unsubscribe from this group and stop receiving emails from it, send an email to simp+unsubscribe@googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/msgid/simp/2cb46c5d-7058-4d0b-80af-d5436a613f88%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Nate Adcock

unread,
Sep 19, 2016, 5:15:20 PM9/19/16
to SIMP Q&A Forum, nate...@gmail.com
Same error. Could it be a simple path issue? I added /home/simp/simp-core to $PATH in .bash_profile. The src, puppet/modules, and rubygems folders are there (since I created them), but should they have come in when I prepped with the git clone? Thanks for your help, by the way...

Trevor Vaughan

unread,
Sep 19, 2016, 8:58:01 PM9/19/16
to Nate Adcock, SIMP Q&A Forum
Ah, yes, those should have come in when you ran build:auto.

Can you try a fresh simp-core clone and then just run build:auto from there?

Thanks,

Trevor

To unsubscribe from this group and stop receiving emails from it, send an email to simp+unsubscribe@googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/msgid/simp/4f4229b4-9126-406a-bb92-03046792d7be%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Nate Adcock

unread,
Sep 19, 2016, 9:07:14 PM9/19/16
to Trevor Vaughan, SIMP Q&A Forum
Yes, I can try that, but I did one earlier today, and that did not help. I basically ran back through the whole setting up the build env, because I just figured I missed something. I just got kicked off the network for some reason so will try this first thing in the AM. Again thanks for your patience. 

To view this discussion on the web visit https://groups.google.com/d/msgid/simp/4f4229b4-9126-406a-bb92-03046792d7be%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--
Trevor Vaughan
Vice President, Onyx Point, Inc

-- This account not approved for unencrypted proprietary information --

--
You received this message because you are subscribed to a topic in the Google Groups "SIMP Q&A Forum" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/simp/oXfjP1J9YsA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to simp+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/simp/CANs%2BFoWGe5%3DtWOP8mb%3DSjDZO5bO5dE9s1Kg-hSypx0UjEBwGmw%40mail.gmail.com.

Trevor Vaughan

unread,
Sep 20, 2016, 9:13:59 AM9/20/16
to Nate Adcock, SIMP Q&A Forum
No problem. I'm sorry that you're having so many issues.

This is our usual method for building so I'm not quite sure what's happening.

Trevor

To unsubscribe from this group and stop receiving emails from it, send an email to simp+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--
Trevor Vaughan
Vice President, Onyx Point, Inc

-- This account not approved for unencrypted proprietary information --

--
You received this message because you are subscribed to a topic in the Google Groups "SIMP Q&A Forum" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/simp/oXfjP1J9YsA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to simp+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/simp/CANs%2BFoWGe5%3DtWOP8mb%3DSjDZO5bO5dE9s1Kg-hSypx0UjEBwGmw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Mark Kraft

unread,
Sep 20, 2016, 8:00:50 PM9/20/16
to SIMP Q&A Forum
I thinks it's because the mirror you are using for clamav no longer exists. That's the issue I had to work around last week.

Mark

Nate Adcock

unread,
Sep 21, 2016, 9:18:02 AM9/21/16
to SIMP Q&A Forum
So, I got the initial build ISO to complete, but when I deployed SIMP on a VM, I see that the kickstart has specified #ROOTPASS# as enc password for root. I changed that to encrypted string in the src, but when I rerun the build:auto command again, it gets to the pkg builds and just sits there. Eventually the process hangs the server, and I have to hard reset (let it sit there overnight). The server is literally not doing anything but rake at this point.

Trevor Vaughan

unread,
Sep 21, 2016, 10:26:52 AM9/21/16
to Nate Adcock, SIMP Q&A Forum
Hi Nate,

My guess is that you ran out of entropy.

Try installing 'haveged' and spinning it up before building.

Trevor

--
You received this message because you are subscribed to the Google Groups "SIMP Q&A Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to simp+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/simp/9ee84247-5026-4ef6-bc7f-065960e4599c%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Nate Adcock

unread,
Sep 21, 2016, 10:42:18 AM9/21/16
to SIMP Q&A Forum, nate...@gmail.com
Haha, what a riot. One can never have enough entropy! I checked the /proc/sys/kernel/random/entropy_avail and I had 3K+ number there. rngd was also running. I did a rake clobber, and reran the build again. Looks like I got better entropy this time, because it rebuilt. How do I do a simple rebuild of the ISO in the future to make a simple change like this (update a puppet or kickstart config file). Is there an easy way to make minor config changes to the ISO with rake without going through an entire build? Sorry for my noobness showing.

On Wednesday, September 21, 2016 at 10:26:52 AM UTC-4, Trevor Vaughan wrote:
Hi Nate,

My guess is that you ran out of entropy.

Try installing 'haveged' and spinning it up before building.

Trevor
On Wed, Sep 21, 2016 at 9:18 AM, Nate Adcock <nate...@gmail.com> wrote:
So, I got the initial build ISO to complete, but when I deployed SIMP on a VM, I see that the kickstart has specified #ROOTPASS# as enc password for root. I changed that to encrypted string in the src, but when I rerun the build:auto command again, it gets to the pkg builds and just sits there. Eventually the process hangs the server, and I have to hard reset (let it sit there overnight). The server is literally not doing anything but rake at this point.

On Tuesday, September 20, 2016 at 8:00:50 PM UTC-4, Mark Kraft wrote:
I thinks it's because the mirror you are using for clamav no longer exists. That's the issue I had to work around last week.

Mark

--
You received this message because you are subscribed to the Google Groups "SIMP Q&A Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to simp+uns...@googlegroups.com.

Trevor Vaughan

unread,
Sep 21, 2016, 10:43:45 AM9/21/16
to Nate Adcock, SIMP Q&A Forum
Ah, if you want to just make minor ISO updates, you can unpack the tarball that gets generated under build/DVD_Overlay, re-tar it, and then use the short form of:

rake build:auto[5.1.X, <path to ISO>, <path to Tarball>]

Trevor

To unsubscribe from this group and stop receiving emails from it, send an email to simp+unsubscribe@googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/msgid/simp/97ceceb1-89a7-44e0-9c0f-9a9c4ee0d81c%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Nate Adcock

unread,
Sep 21, 2016, 1:00:51 PM9/21/16
to SIMP Q&A Forum, nate...@gmail.com
I have tried setting an encrypted password string in the pupclient...cfg in the ks directory (made using python command-
echo 'import crypt,getpass; print crypt.crypt(getpass.getpass(), "$6$16_CHARACTER_SALT_HERE")' | python -
), and updated per your instructions (I verified the new ISO has my change), but can't seem to login root in the build OS once built? Am I setting the correct config file or is this being overridden somewhere else? Thanks again, I'm like "this close" to actually setting up my SIMP puppet host!

Trevor Vaughan

unread,
Sep 21, 2016, 1:04:25 PM9/21/16
to Nate Adcock, SIMP Q&A Forum
Did you try the default password of 'RootPassword'?

Trevor

To unsubscribe from this group and stop receiving emails from it, send an email to simp+unsubscribe@googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/msgid/simp/67e4f32d-2f95-4486-81b8-3f30aecb9045%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Nate Adcock

unread,
Sep 21, 2016, 1:13:44 PM9/21/16
to SIMP Q&A Forum, nate...@gmail.com
Embarrassingly, uh no...and that worked, by the way. Again, thanks, and think I can stop bugging you now. Again, much thanks for your help!

Trevor Vaughan

unread,
Sep 21, 2016, 1:16:04 PM9/21/16
to Nate Adcock, SIMP Q&A Forum
Not a problem!

To unsubscribe from this group and stop receiving emails from it, send an email to simp+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/simp/e40981b8-a32c-41ba-97ec-7ad9a9641a0d%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages