Issue Installing SIMP Built from Source

[nwrig...@yahoo.com]

Hi,

My coworker and I built SIMP 5.1.X from master using RHEL 7.2, and it built with no errors. However, upon attempting to install this on our machine, we get the following error:

"Error

The following software marked for installation has errors. This is likely caused by an error with your installation source.

openssh conflicts with selinux-policy-3.13.1-60.el7.noarch"

Can you provide us with any ideas as to why this might occur and what steps to take next?

Thanks so much,

Natalie Wright

[Trevor Vaughan]

Hi Natalie,

It looks like this might be an associated bug https://bugzilla.redhat.com/show_bug.cgi?id=1373297 and that this might be a bug in the upstream vendor packaging.

Do you need to use 5.1.X? Would it be possible to try the 5.2.X build?

Alternatively, you might need to check your source repositories and ensure that a compatible version of openssh and selinux-policy are both in place there.

Thanks,

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/12f2042e-6b98-4693-8d09-90334f91ee24%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Trevor Vaughan
Vice President, Onyx Point, Inc

(410) 541-6699 x788

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

[nwrig...@yahoo.com]

We started over installing from source, and checked out tag 5.2.0-0. We copied our Red Hat repositories file into the repos folder, and started to build. We ran "bundle install", followed by "bundle exec rake build:auto[5.1.X,<path-to-iso-folder>]". It fails with errors about being unable to download packages from the repositories. Do you have any ideas as to what this sounds like? Thanks!

On Tuesday, November 8, 2016 at 1:07:16 PM UTC-6, Trevor Vaughan wrote:

Hi Natalie,

It looks like this might be an associated bug https://bugzilla.redhat.com/show_bug.cgi?id=1373297 and that this might be a bug in the upstream vendor packaging.

Do you need to use 5.1.X? Would it be possible to try the 5.2.X build?

Alternatively, you might need to check your source repositories and ensure that a compatible version of openssh and selinux-policy are both in place there.

Thanks,

Trevor

On Tue, Nov 8, 2016 at 11:44 AM, nwright079 via SIMP Q&A Forum <si...@googlegroups.com> wrote:

Hi,

My coworker and I built SIMP 5.1.X from master using RHEL 7.2, and it built with no errors. However, upon attempting to install this on our machine, we get the following error:

"Error

The following software marked for installation has errors. This is likely caused by an error with your installation source.

openssh conflicts with selinux-policy-3.13.1-60.el7.noarch"

Can you provide us with any ideas as to why this might occur and what steps to take next?

Thanks so much,

Natalie Wright

--
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.

To view this discussion on the web visit https://groups.google.com/d/msgid/simp/12f2042e-6b98-4693-8d09-90334f91ee24%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Trevor Vaughan]

Hi Natalie,

If you look in build/yum_data/SIMP5.2.0_RHEL7.2_x86_64 under your clone of the 'simp-core' repo, you should see a 'repos' directory.

This contains yum repo files that we use to try and download all of our dependencies, which are listed in the 'packages.yaml' file beside it.

You'll note, if you look in this file, that many of the files are listed with a 'source' of something like the 'Red Hat Optional Repository'. These files are not available without a license so there is no canonical URI that we can provide for the packages and you'll need to have your own internal repo.

We do this so that we can both guarantee, and document, our download sources for the packages that we use in our ISO builds.

If you want to skip this step, you'll need to get all of the packages listed in that file from a location of your choosing and add them to a 'packages' folder in the same directory.

There is a README file that should cover this in the 'build' directory just under the simp-core clone. We'll get this added into the main documentation as well to reduce confusion.

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/93f026bb-5197-4084-9376-7f47151b631b%40googlegroups.com.

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

[nwrig...@yahoo.com]

We've created a repo file that contains the Red Hat Updates and Optional Repositories, and we do have those correctly set up on the machine. It should be pulling from them, and it has in the past when we used the unstable 5.1.X branch.

To view this discussion on the web visit https://groups.google.com/d/msgid/simp/93f026bb-5197-4084-9376-7f47151b631b%40googlegroups.com.

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

[Trevor Vaughan]

Can you try using those files with yum directly and see if there is some issue with your repo setup?

I think it's yum -c <path/to/file>

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/c5c477c4-b144-4dc5-802c-c401f0f53e82%40googlegroups.com.

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

[nwrig...@yahoo.com]

We tried that, and there's no issue with our repo setup, the command works. However, RedHat has removed those older packages (which we were unable to download) from their repositories. We're now downloading them individually and putting them in the packages folder.

To view this discussion on the web visit https://groups.google.com/d/msgid/simp/c5c477c4-b144-4dc5-802c-c401f0f53e82%40googlegroups.com.

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

[Trevor Vaughan]

Ah! That was certainly friendly of them.

If there are newer packages, you should be able to update the local package list using the 'rake build:yum:sync[RHEL,7.2]' Rake task.

Back up anything that you have, or do this in another repo checkout as you might end up with issues.

This is where you might have had your original issue since it's possible that RH didn't update their dependency tree properly and you need a later version of either openssh or selinux-policy.

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/36ee2da5-9089-4c66-91df-4b67ade7abdf%40googlegroups.com.

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

[nwrig...@yahoo.com]

Thanks! That makes sense. We resolved those issues by updating the package list, and after checking out tag 5.2.0-0, we started the build again to discover this error:

pupmod-simp-2.0.1-2016.noarch from base,

unresolved deps: puppet >= 0:4.6.0

Is this trying to pull puppet 4? It was my understanding that puppet 4 was incompatible with this.

[Trevor Vaughan]

Ah, I actually just answered that one on another thread.

Add the word 'stable' to the end of your rake build list.

Thanks,

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/15a62765-009f-461f-bc27-855de85cda79%40googlegroups.com.

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

[Trevor Vaughan]

Would you mind sending along the package diffs for RHEL?

Thanks,

Trevor

[Trevor Vaughan]

Hi Natalie,

Apologies but I gave you some bad advise based on the way things used to work.

The correct answer can be found at the end of https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/simp/UfiZ0mQpJjI/xKwFjfaBBgAJ

Thanks,

Trevor

[nwrig...@yahoo.com]

We were wrong about the packages being missing from the repository (apparently they were in the repository, with two exceptions: python-traceback2-1.4.0-2.el7.noarch.rpm and ruby-ldap-0.9.16-1.el7.x86_64.rpm were not there, and we individually downloaded those and placed them in the packages folder), so all necessary packages are there (with those two exceptions). Unfortunately, it's (for whatever reason) still not able to automatically download these packages, even after copying the Red Hat repo into the repos folder, like you had mentioned (we had to run yumdownloader <package_name> for each of these):

apr-util-1.5.2-6.el7.x86_64.rpm

apr-util-ldap-1.5.2-6.el7.x86_64.rpm

boost-regex-1.53.0-23.el7.x86_64.rpm

hmaccalc-0.9.13-4.el7.x86_64.rpm

kernel-3.10.0-229.14.1.el7.x86_64.rpm

libarchive-devel-3.1.2-7.el7.x86_64.rpm

libevent-2.0.21-4.el7.x86_64.rpm

libreswan-3.15-5.el7_1.x86_64.rpm

libselinux-2.2.2-6.el7.x86_64.rpm

libselinux-python-2.2.2-6.el7.x86_64.rpm

libselinux-ruby-2.2.2-6.el7.x86_64.rpm

libselinux-static-2.2.2-6.el7.x86_64.rpm

libselinux-utils-2.2.2-6.el7.x86_64.rpm

libsepol-2.1.9-3.el7.x86_64.rpm

libsepol-static-2.1.9-3.el7.x86_64.rpm

libyaml-0.1.4-11.el7_0.x86_64.rpm

linux-firmware-20140911-0.1.git365e80c.el7.noarch.rpm

mod_ldap-2.4.6-40.el7.x86_64.rpm

openssh-6.6.1p1-22.el7_1.x86_64.rpm

openssh-askpass-6.6.1p1-22.el7_1.x86_64.rpm

openssh-clients-6.6.1p1-22.el7_1.x86_64.rpm

openssh-keycat-6.6.1p1-22.el7_1.x86_64.rpm

openssh-ldap-6.6.1p1-22.el7_1.x86_64.rpm

openssh-server-6.6.1p1-22.el7_1.x86_64.rpm

rrdtool-1.4.8-8.el7.x86_64.rpm

rubygem-rake-0.9.6-25.el7_1.noarch.rpm

selinux-policy-3.13.1-60.el7.noarch.rpm

selinux-policy-3.13.1-102.el7_3.4.noarch.rpm

source-highlight-3.1.6-6.el7.x86_64.rpm

syslinux-tftpboot-4.05-12.el7.x86_64.rpm

unbound-libs-1.4.20-26.el7.x86_64.rpm

All that aside, we will try the commands from the other thread you linked and check up there for resolutions regarding the build errors that poster is reporting.

[nwrig...@yahoo.com]

Thanks again for the help, by the way. We were able to successfully build 5.2.0. We are currently installing it on our machine, which is now taking upwards of 16 hours. Just wondering, is this normal or expected? Thanks.

[Trevor Vaughan]

Hi Natalie,

I've never seen a system that took more than 40 minutes to install with the exception of systems with massive disks.

Also, if you enabled disk encryption, and have a large disk, you may have to wait for that.

The final issue may be that your system lacks enough entropy. Try switching terminals and moving the mouse a lot and going random things in the keyboard for a while.

Check the various consoles and see if any errors have been reported as well.

Thanks,

Trevor

On Nov 16, 2016 10:45 AM, "nwright079 via SIMP Q&A Forum" <si...@googlegroups.com> wrote:

Thanks again for the help, by the way. We were able to successfully build 5.2.0. We are currently installing it on our machine, which is now taking upwards of 16 hours. Just wondering, is this normal or expected? Thanks.

--

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/243bd045-b47e-416d-bded-9aa38a26d30e%40googlegroups.com.