So I’m very new to foreman, but I’m investigating it as a solution for some
work issues. it was recomended as an alternative to Spacewalk and it looks
promising, however …
I installed on a centos 7 server built in Google Cloud Platform. Right
away, I got a server configuration error when i started Foreman (which
installed without error). This is, i think, because foreman thinks that my
server can be accessed via the placeholder hostname assigned by google, but
that’s not a huge issue. Using the assigned IP i can access the system
fine.
However, when i try to install Katello, no luck. I followed the
instructions found on the foreman site
(Foreman :: Plugin Manuals) but
upon trying to run “yum -y install katello” I’m getting dependency errors.
Specifically about the only available version of rubygem (tfm stuff) being
too recent (for example version 0.9.1 when the install wants < 0.9.0
I’m not really sure what to do with it at this point, but an assist would
be appreciated. Here’s a pastebin of the error I get when following the
website instructions. https://pastebin.com/NqsbkHJN
It sounds like you may have installed Foreman and then attempted to add
Katello onto it.
For most Foreman plugins that is a good approach but Katello is currently
special. You need to install Foreman using the Katello install procedure
which installs Foreman and Katello simultaneously.
Regards,
–Tony
···
On Monday, December 11, 2017 at 3:07:49 PM UTC-5, Joe Auerbach wrote:
So I’m very new to foreman, but I’m investigating it as a solution for
some work issues. it was recomended as an alternative to Spacewalk and it
looks promising, however …
I installed on a centos 7 server built in Google Cloud Platform. Right
away, I got a server configuration error when i started Foreman (which
installed without error). This is, i think, because foreman thinks that my
server can be accessed via the placeholder hostname assigned by google, but
that’s not a huge issue. Using the assigned IP i can access the system
fine.
However, when i try to install Katello, no luck. I followed the
instructions found on the foreman site ( https://theforeman.org/plugins/katello/3.2/installation/index.html) but
upon trying to run “yum -y install katello” I’m getting dependency errors.
Specifically about the only available version of rubygem (tfm stuff) being
too recent (for example version 0.9.1 when the install wants < 0.9.0
So I’m very new to foreman, but I’m investigating it as a solution for
some work issues. it was recomended as an alternative to Spacewalk and it
looks promising, however …
I installed on a centos 7 server built in Google Cloud Platform. Right
away, I got a server configuration error when i started Foreman (which
installed without error). This is, i think, because foreman thinks that my
server can be accessed via the placeholder hostname assigned by google, but
that’s not a huge issue. Using the assigned IP i can access the system
fine.
However, when i try to install Katello, no luck. I followed the
instructions found on the foreman site ( https://theforeman.org/plugins/katello/3.2/installation/index.html) but
upon trying to run “yum -y install katello” I’m getting dependency errors.
Specifically about the only available version of rubygem (tfm stuff) being
too recent (for example version 0.9.1 when the install wants < 0.9.0
So I’m very new to foreman, but I’m investigating it as a solution for
some work issues. it was recomended as an alternative to Spacewalk and it
looks promising, however …
I installed on a centos 7 server built in Google Cloud Platform. Right
away, I got a server configuration error when i started Foreman (which
installed without error). This is, i think, because foreman thinks that my
server can be accessed via the placeholder hostname assigned by google, but
that’s not a huge issue. Using the assigned IP i can access the system
fine.
However, when i try to install Katello, no luck. I followed the
instructions found on the foreman site (https://theforeman.org/
plugins/katello/3.2/installation/index.html) but upon trying to run “yum
-y install katello” I’m getting dependency errors. Specifically about the
only available version of rubygem (tfm stuff) being too recent (for
example version 0.9.1 when the install wants < 0.9.0
Well, that’s unexpected. Am I better off just scrapping this server and
spinning up a fresh one?if I’m doing that I might as well as if there’s
currently a preferred distro. I installed on centos 7.
It sounds like you may have installed Foreman and then attempted to add
Katello onto it.
For most Foreman plugins that is a good approach but Katello is currently
special. You need to install Foreman using the Katello install procedure
which installs Foreman and Katello simultaneously.
Regards,
–Tony
On Monday, December 11, 2017 at 3:07:49 PM UTC-5, Joe Auerbach wrote:
So I’m very new to foreman, but I’m investigating it as a solution for
some work issues. it was recomended as an alternative to Spacewalk and it
looks promising, however …
I installed on a centos 7 server built in Google Cloud Platform. Right
away, I got a server configuration error when i started Foreman (which
installed without error). This is, i think, because foreman thinks that my
server can be accessed via the placeholder hostname assigned by google, but
that’s not a huge issue. Using the assigned IP i can access the system
fine.
However, when i try to install Katello, no luck. I followed the
instructions found on the foreman site (https://theforeman.org/plugin
s/katello/3.2/installation/index.html) but upon trying to run “yum -y
install katello” I’m getting dependency errors. Specifically about the
only available version of rubygem (tfm stuff) being too recent (for
example version 0.9.1 when the install wants < 0.9.0
So I’m very new to foreman, but I’m investigating it as a solution for
some work issues. it was recomended as an alternative to Spacewalk and it
looks promising, however …
I installed on a centos 7 server built in Google Cloud Platform. Right
away, I got a server configuration error when i started Foreman (which
installed without error). This is, i think, because foreman thinks that my
server can be accessed via the placeholder hostname assigned by google, but
that’s not a huge issue. Using the assigned IP i can access the system
fine.
However, when i try to install Katello, no luck. I followed the
instructions found on the foreman site (https://theforeman.org/plugin
s/katello/3.2/installation/index.html) but upon trying to run “yum -y
install katello” I’m getting dependency errors. Specifically about the
only available version of rubygem (tfm stuff) being too recent (for
example version 0.9.1 when the install wants < 0.9.0
Okay, so the katello install went great and now I’m into the installing
foreman bit. Specifically here: foreman-installer --scenario katello
. I have to admit, i have no idea what options are normal. If
I’m jus tlooking to store and manage repos and the like is selecting the
Generic option okay here? Just foreman-installer --scenario katello
Generic?
Well, that’s unexpected. Am I better off just scrapping this server and
spinning up a fresh one?if I’m doing that I might as well as if there’s
currently a preferred distro. I installed on centos 7.
It sounds like you may have installed Foreman and then attempted to add
Katello onto it.
For most Foreman plugins that is a good approach but Katello is currently
special. You need to install Foreman using the Katello install procedure
which installs Foreman and Katello simultaneously.
Regards,
–Tony
On Monday, December 11, 2017 at 3:07:49 PM UTC-5, Joe Auerbach wrote:
So I’m very new to foreman, but I’m investigating it as a solution for
some work issues. it was recomended as an alternative to Spacewalk and it
looks promising, however …
I installed on a centos 7 server built in Google Cloud Platform. Right
away, I got a server configuration error when i started Foreman (which
installed without error). This is, i think, because foreman thinks that my
server can be accessed via the placeholder hostname assigned by google, but
that’s not a huge issue. Using the assigned IP i can access the system
fine.
However, when i try to install Katello, no luck. I followed the
instructions found on the foreman site (https://theforeman.org/plugin
s/katello/3.2/installation/index.html) but upon trying to run “yum -y
install katello” I’m getting dependency errors. Specifically about the
only available version of rubygem (tfm stuff) being too recent (for
example version 0.9.1 when the install wants < 0.9.0
Yes, the defaults should work fine for you. You can always enable other
plugins (look at foreman-installer --full-help | grep enable) later if
you decide you need some functionality that one of them provides.
Okay, so the katello install went great and now I’m into the installing
foreman bit. Specifically here: foreman-installer --scenario katello
. I have to admit, i have no idea what options are normal. If
I’m jus tlooking to store and manage repos and the like is selecting the
Generic option okay here? Just foreman-installer --scenario katello
Generic?
Well, that’s unexpected. Am I better off just scrapping this server and
spinning up a fresh one?if I’m doing that I might as well as if there’s
currently a preferred distro. I installed on centos 7.
It sounds like you may have installed Foreman and then attempted to add
Katello onto it.
For most Foreman plugins that is a good approach but Katello is
currently special. You need to install Foreman using the Katello install
procedure which installs Foreman and Katello simultaneously.
Regards,
–Tony
On Monday, December 11, 2017 at 3:07:49 PM UTC-5, Joe Auerbach wrote:
So I’m very new to foreman, but I’m investigating it as a solution for
some work issues. it was recomended as an alternative to Spacewalk and it
looks promising, however …
I installed on a centos 7 server built in Google Cloud Platform. Right
away, I got a server configuration error when i started Foreman (which
installed without error). This is, i think, because foreman thinks that my
server can be accessed via the placeholder hostname assigned by google, but
that’s not a huge issue. Using the assigned IP i can access the system
fine.
However, when i try to install Katello, no luck. I followed the
instructions found on the foreman site (https://theforeman.org/plugin
s/katello/3.2/installation/index.html) but upon trying to run “yum -y
install katello” I’m getting dependency errors. Specifically about the
only available version of rubygem (tfm stuff) being too recent (for
example version 0.9.1 when the install wants < 0.9.0
This worked great for the install. I’m getting what looks like a pretty
common error when trying to add a repo to my first product. “There was an
issue with the backend service pulp: 500 Internal Server Error”. Anyone
have any idea what that one is about?
···
On Tue, Dec 12, 2017 at 11:25 AM, Andrew Kofink akofink@redhat.com wrote:
Yes, the defaults should work fine for you. You can always enable other
plugins (look at foreman-installer --full-help | grep enable) later if
you decide you need some functionality that one of them provides.
Okay, so the katello install went great and now I’m into the installing
foreman bit. Specifically here: foreman-installer --scenario katello
. I have to admit, i have no idea what options are normal. If
I’m jus tlooking to store and manage repos and the like is selecting the
Generic option okay here? Just foreman-installer --scenario katello
Generic?
Well, that’s unexpected. Am I better off just scrapping this server and
spinning up a fresh one?if I’m doing that I might as well as if there’s
currently a preferred distro. I installed on centos 7.
It sounds like you may have installed Foreman and then attempted to add
Katello onto it.
For most Foreman plugins that is a good approach but Katello is
currently special. You need to install Foreman using the Katello install
procedure which installs Foreman and Katello simultaneously.
Regards,
–Tony
On Monday, December 11, 2017 at 3:07:49 PM UTC-5, Joe Auerbach wrote:
So I’m very new to foreman, but I’m investigating it as a solution for
some work issues. it was recomended as an alternative to Spacewalk and it
looks promising, however …
I installed on a centos 7 server built in Google Cloud Platform.
Right away, I got a server configuration error when i started Foreman
(which installed without error). This is, i think, because foreman thinks
that my server can be accessed via the placeholder hostname assigned by
google, but that’s not a huge issue. Using the assigned IP i can access
the system fine.
However, when i try to install Katello, no luck. I followed the
instructions found on the foreman site (https://theforeman.org/plugin
s/katello/3.2/installation/index.html) but upon trying to run “yum -y
install katello” I’m getting dependency errors. Specifically about the
only available version of rubygem (tfm stuff) being too recent (for
example version 0.9.1 when the install wants < 0.9.0
This worked great for the install. I’m getting what looks like a pretty
common error when trying to add a repo to my first product. “There was an
issue with the backend service pulp: 500 Internal Server Error”. Anyone
have any idea what that one is about?
On Tue, Dec 12, 2017 at 11:25 AM, Andrew Kofink akofink@redhat.com > wrote:
Yes, the defaults should work fine for you. You can always enable other
plugins (look at foreman-installer --full-help | grep enable) later if
you decide you need some functionality that one of them provides.
Okay, so the katello install went great and now I’m into the installing
foreman bit. Specifically here: foreman-installer --scenario katello
. I have to admit, i have no idea what options are normal. If
I’m jus tlooking to store and manage repos and the like is selecting the
Generic option okay here? Just foreman-installer --scenario katello
Generic?
Well, that’s unexpected. Am I better off just scrapping this server
and spinning up a fresh one?if I’m doing that I might as well as if there’s
currently a preferred distro. I installed on centos 7.
It sounds like you may have installed Foreman and then attempted to
add Katello onto it.
For most Foreman plugins that is a good approach but Katello is
currently special. You need to install Foreman using the Katello install
procedure which installs Foreman and Katello simultaneously.
Regards,
–Tony
On Monday, December 11, 2017 at 3:07:49 PM UTC-5, Joe Auerbach wrote:
So I’m very new to foreman, but I’m investigating it as a solution
for some work issues. it was recomended as an alternative to Spacewalk and
it looks promising, however …
I installed on a centos 7 server built in Google Cloud Platform.
Right away, I got a server configuration error when i started Foreman
(which installed without error). This is, i think, because foreman thinks
that my server can be accessed via the placeholder hostname assigned by
google, but that’s not a huge issue. Using the assigned IP i can access
the system fine.
However, when i try to install Katello, no luck. I followed the
instructions found on the foreman site (https://theforeman.org/plugin
s/katello/3.2/installation/index.html) but upon trying to run “yum
-y install katello” I’m getting dependency errors. Specifically about the
only available version of rubygem (tfm stuff) being too recent (for
example version 0.9.1 when the install wants < 0.9.0
No entries, sadly. Seems like this is the code block with pulp errors.
i’m afraid I’m not conversant in pulp.
pasted for ease of reading (I hope)
/opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.5.0.1/app/models/katello/ping.rb:52:in
`block in ping_pulp_with_auth’
/opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.5.0.1/app/models/katello/ping.rb:48:in
`ping_pulp_with_auth’
2017-12-12 19:08:53 11fa8b06 [foreman-tasks/action] [E] There was an issue
with the backend service pulp: 500 Internal Server Error (RuntimeError)
2017-12-12 19:08:53 11fa8b06 [foreman-tasks/action] [E] There was an issue
with the backend service pulp: 500 Internal Server Error (RuntimeError)
2017-12-12 19:08:53 11fa8b06 [app] [E] RuntimeError: There was an issue
with the backend service pulp: 500 Internal Server Error
This worked great for the install. I’m getting what looks like a pretty
common error when trying to add a repo to my first product. “There was an
issue with the backend service pulp: 500 Internal Server Error”. Anyone
have any idea what that one is about?
On Tue, Dec 12, 2017 at 11:25 AM, Andrew Kofink akofink@redhat.com >> wrote:
Yes, the defaults should work fine for you. You can always enable other
plugins (look at foreman-installer --full-help | grep enable) later if
you decide you need some functionality that one of them provides.
Okay, so the katello install went great and now I’m into the installing
foreman bit. Specifically here: foreman-installer --scenario katello
. I have to admit, i have no idea what options are normal. If
I’m jus tlooking to store and manage repos and the like is selecting the
Generic option okay here? Just foreman-installer --scenario katello
Generic?
Well, that’s unexpected. Am I better off just scrapping this server
and spinning up a fresh one?if I’m doing that I might as well as if there’s
currently a preferred distro. I installed on centos 7.
It sounds like you may have installed Foreman and then attempted to
add Katello onto it.
For most Foreman plugins that is a good approach but Katello is
currently special. You need to install Foreman using the Katello install
procedure which installs Foreman and Katello simultaneously.
Regards,
–Tony
On Monday, December 11, 2017 at 3:07:49 PM UTC-5, Joe Auerbach wrote:
So I’m very new to foreman, but I’m investigating it as a solution
for some work issues. it was recomended as an alternative to Spacewalk and
it looks promising, however …
I installed on a centos 7 server built in Google Cloud Platform.
Right away, I got a server configuration error when i started Foreman
(which installed without error). This is, i think, because foreman thinks
that my server can be accessed via the placeholder hostname assigned by
google, but that’s not a huge issue. Using the assigned IP i can access
the system fine.
However, when i try to install Katello, no luck. I followed the
instructions found on the foreman site ( https://theforeman.org/plugins/katello/3.2/installation/index.html)
but upon trying to run “yum -y install katello” I’m getting dependency
errors. Specifically about the only available version of rubygem (tfm
stuff) being too recent (for example version 0.9.1 when the install wants <
0.9.0
Basically, a new package, python-django16, got pushed to EPEL that had a
’Provides: python-django’ set, overriding the ‘python-django’ package. For
some reason, when this package gets installed, pulp can’t find it’s
libraries properly and has been giving a lot of ‘import not found’ errors
for pulp code.
I have been in contact with the package maintainer to correct this issue
(there is a bug link in the above e-mail), and it should be resolved
shortly, as the update is already in bodhi. I’m waiting for it to
propagate to testing repos to give it some karma to help get it released.
The workaround we have been using is to ‘yum install python-django’
(without the 16) for now until this issue is resolved. (it should also be
safe to remove python-django16)
We apologize for any inconveniences to any parties involved
Basically, a new package, python-django16, got pushed to EPEL that had a
‘Provides: python-django’ set, overriding the ‘python-django’ package. For
some reason, when this package gets installed, pulp can’t find it’s
libraries properly and has been giving a lot of ‘import not found’ errors
for pulp code.
I have been in contact with the package maintainer to correct this issue
(there is a bug link in the above e-mail), and it should be resolved
shortly, as the update is already in bodhi. I’m waiting for it to
propagate to testing repos to give it some karma to help get it released.
The workaround we have been using is to ‘yum install python-django’
(without the 16) for now until this issue is resolved. (it should also be
safe to remove python-django16)
We apologize for any inconveniences to any parties involved
There will not. The issue here is python-django16 is erroneously installed due to a packaging error
in an upstream repo (epel). The manual fix here is to get the system into the correct state,
therefore there will be no need to 'fix' it later after the upstream repo is fixed. It will just
continue to work as it did prior to this past weekend for new installs.
···
On Tue, 2017-12-12 at 18:32 -0500, Joe Auerbach wrote:
Thanks! That's a big help. If we use that manual fix I presume we will have a second manual fix
when the package comes out live?
thanks. that worked like a charm here. Up and running. Now to try to find
an AWS APL that will work as well (they gave me grief on my spacewalk
install and I have a feeling they will not be a LOT easier with foreman,
but we'll see) .
···
On Wed, Dec 13, 2017 at 8:19 AM, Patrick Creech <pcreech@redhat.com> wrote:
On Tue, 2017-12-12 at 18:32 -0500, Joe Auerbach wrote:
> Thanks! That's a big help. If we use that manual fix I presume we will
have a second manual fix
> when the package comes out live?
>
There will not. The issue here is python-django16 is erroneously
installed due to a packaging error
in an upstream repo (epel). The manual fix here is to get the system into
the correct state,
therefore there will be no need to 'fix' it later after the upstream repo
is fixed. It will just
continue to work as it did prior to this past weekend for new installs.
--
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users\.
For more options, visit https://groups.google.com/d/optout\.
John Mitsch
Red Hat Engineering
(860)-967-7285
irc: jomitsch
···
On Wed, Dec 13, 2017 at 9:01 AM, Joe Auerbach <joe.auerbach@gmail.com> wrote:
thanks. that worked like a charm here. Up and running. Now to try to
find an AWS APL that will work as well (they gave me grief on my spacewalk
install and I have a feeling they will not be a LOT easier with foreman,
but we'll see) .
On Wed, Dec 13, 2017 at 8:19 AM, Patrick Creech <pcreech@redhat.com> > wrote:
On Tue, 2017-12-12 at 18:32 -0500, Joe Auerbach wrote:
> Thanks! That's a big help. If we use that manual fix I presume we
will have a second manual fix
> when the package comes out live?
>
There will not. The issue here is python-django16 is erroneously
installed due to a packaging error
in an upstream repo (epel). The manual fix here is to get the system
into the correct state,
therefore there will be no need to 'fix' it later after the upstream repo
is fixed. It will just
continue to work as it did prior to this past weekend for new installs.
--
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users\.
For more options, visit https://groups.google.com/d/optout\.
--
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users\.
For more options, visit https://groups.google.com/d/optout\.
