se '//localhost/candlepin'
> --user candlepin --password vh3MC4YwcHtZdPWwkU8RekeyPS6ByBAU failed!
> Check the output for error!
> Upgrade step migrate_candlepin failed. Check logs for more information.
>
> With ou without proxy, same error.
>
> Thx
>
>
> --
> You receiv
ers+unsubscr...@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.
>
--
Eric D. Helms
Red Hat Engineering
--
ps
> "Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to foreman-users+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.go
issue.
> If the only solution is to update to the latest release then we will have
> to eventually go with that, but if there is a solution that can used before
> getting to that stage, that would be greatly helpful.
>
> Katello-agent/goferd is running on all the hosts.
>
> Any other in
We are happy to announce the GA of Katello 3.4.5. This release contains a
large number of bug fixes for both small UI issues, user issues found while
using 3.4.4 and developer found issues that we felt would bring more
stability to users. There are some known Puppet 4 upgrade issues also
included
That should be fixed now, yum clean all to be safe and then yum upgrade to
ensure you have tfm-rubygem-bastion 5 .0.10.
On Aug 26, 2017 3:57 PM, "Jasper Connery" wrote:
> On a CentOS 7 server I'm currently trying to install Katello using the 3.4
> guide found here:
stop receiving emails from it, send an
> email to foreman-users+unsubscr...@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/
for breaking everyone.
--
Eric D. Helms
Red Hat Engineering
--
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+unsubscr...@googlegroups.co
; libraries: libruby.so.1.9: cannot open shared object file: No such file or
>>>>> directory
>>>>> [root@katello-test ~]# /opt/theforeman/tfm/root/usr/s
>>>>> hare/gems/gems/passenger-4.0.18/bin/passenger-status
>>>>> *** Phusion Passenger: no
id find errors
>> in that log, but not sure if they're related:
>>
>>> Jun 28 15:25:35 katello.internal qpidd[18457]: 2016-06-28 15:25:35
>>> [System] error Connection qpid No protocol received closing
>>> Jun 28 15:25:35 katello.internal qpidd[18457]: 2016-06-28
rote:
I commented out the Listen 443 line from /etc/httpd/conf.d/ports.conf.
Louis
On Aug 15, 2017, at 12:23 PM, Eric D Helms <eric.d.he...@gmail.com> wrote:
Which one did you remove? The one from sleeping.conf?
On Aug 15, 2017 12:12 PM, "Louis Bohm" <louisb...@gmail.com&
hare/passenger/helper-scripts/prespawn:87:in `socket'
> from /usr/share/passenger/helper-scripts/prespawn:91:in `head_request'
> from /usr/share/passenger/helper-scripts/prespawn:153:in `'
> /usr/share/passenger/helper-scripts/prespawn:113:in `initialize': No
> route to host - connect(2) (
il.com> wrote:
> Here is the documentation and it does not show it. I also do not remember
> it when I went from 3.2 to 3.3. But I will run it.
>
> Louis
>
> On Aug 15, 2017, at 11:59 AM, Eric D Helms <eric.d.he...@gmail.com> wrote:
>
> Absolutely, every time. Can you do
d address
>> Aug 15 09:02:35 fm pg_ctl: 2017-08-15 09:02:35 EDT HINT: Is another
>> postmaster already running on port 5432? If not, wait a few seconds and
>> retry.
>> Aug 15 09:02:35 fm pg_ctl: 2017-08-15 09:02:35 EDT FATAL: could not
>> create lock file "/var/run/p
l starts up fine.
>
> Louis
>
> On Wednesday, August 2, 2017 at 11:51:15 AM UTC-4, Eric Helms wrote:
>>
>> We are happy to announce the GA of Katello 3.4.4. This release contains
>> a large number of bug fixes for both small UI issues, user issues found
>> while us
mend to
>> please look at the changelog for a full list of changes:
>>
>> https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md
>>
>> Installation:
>> https://theforeman.org/plugins/katello/3.4/installation/index.html
>>
>> Upgrade:
>>
lo/3.4/upgrade/index.html
>>
>>
>> Bug reporting
>> =
>> If you come across a bug in your testing, please file it and note the
>> version of Katello or Foreman that you're using in the report.
>>
>> http://projects.theforeman.org/projects
eforeman.org/plugins/katello/3.4/upgrade/index.html
>>
>>
>> Bug reporting
>> =
>> If you come across a bug in your testing, please file it and note the
>> version of Katello or Foreman that you're using in the report.
>>
>> http://projects.
r(1, u'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify
>> failed (_ssl.c:579)'),))
>>
>> Even with this error, manual sync correctly updates the status.
>>
>> If I run it manually:
>> $ curl -X POST -u admin -H Content-Type:application/json
>> https://p-infra-katello.k
There are existing issues around this large feature and an RFC if you'd
like to contribute via review:
https://github.com/theforeman/rfcs/pull/17
I've written a script using both hammer and apipie to do comparisons I
could share.
On Aug 3, 2017 7:35 PM, "Lachlan Musicman"
I'll shed a little light on what should be happening. When the sync plan
kicks off, it kicks off async by Pulp. The system configures Pulp to have
an http notifier so that when Pulp finished it notifies Katello which
triggers a sync task to index and update new content t for the repositories.
The
reporting
=
If you come across a bug in your testing, please file it and note the
version of Katello or Foreman that you're using in the report.
http://projects.theforeman.org/projects/katello/issues/new
--
Eric D. Helms
Red Hat Engineering
--
You received this message because you
Hey Josh,
Is that error line the only stack trace there is?
On Jul 19, 2017 2:29 PM, "jpavel" wrote:
What's really strange is that I have thus plugin working on a test
installation, but I can't get it to work on production.
*NOT MY CODE*
ils from it, send an
> email to foreman-users+unsubscr...@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.
>
--
gt;>> Diaspora: gwmngil...@joindiaspora.com
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "foreman-dev" group.
>>> To unsubscribe from this group and stop receiving emails from
eiving emails from it, send
>>> an email to foreman-user...@googlegroups.com.
>>> To post to this group, send email to forema...@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/foreman-users.
>>> For more options, visit https://gr
if you find any further irregularities with these
repositories.
--
Eric D. Helms
Red Hat Engineering
--
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 for
..@joindiaspora.com
>
> --
> You received this message because you are subscribed to the Google Groups
> "foreman-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to foreman-dev+unsubscr...@googlegroups.com.
> For more options, visit
ecause 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+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Vis
or Foreman that you're using in the report.
http://projects.theforeman.org/projects/katello/issues/new
--
Eric D. Helms
Red Hat Engineering
--
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiv
in the report.
http://projects.theforeman.org/projects/katello/issues/new
--
Eric D. Helms
Red Hat Engineering
--
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, sen
This has been investigated and found to be a legitimate bug that can arise
in certain scenarios. We'll reply back here once we have the full issue and
solution worked out.
On Jun 6, 2017 6:29 AM, "Tim Hofmann" wrote:
> Hi Duncan,
>
> the client is definitely registered to the
Katello does not use the puppet certificates for a majority of
configuration which means that if you follow the Smart Proxy instructions
you pointed to you'll likely end up with a smart proxy that cannot
communicate back to the server.
Was your DHCP smart proxy an existing smart proxy or a fresh
Howdy,
You are the second user to report an issue around applicable packages in
3.4. Would you mind filing a redmine issue with details for us to
investigate?
Eric
On Jun 3, 2017 5:46 AM, "pascalp" wrote:
> Hello,
>
> ever since I updated Katello from 3.3 to 3.4 I
Howdy Tim,
Let's check a few items to narrow down what the issue might be:
* you've got katello-agent installed on the host and goferd is running;
does the UI indicate that it knows katello-agent is installed?
* if you look at the package list for the content host do you see the
outdated nginx
ng to figure out how this
> works without enabling the puppet service, which doesn't seem to be related.
>
> On Tue, 2017-05-30 at 20:08 -0400, Eric D Helms wrote:
>
> The service you are looking for is when you installed katello-agent. This
> package includes utilities that up
om it, send an
> email to foreman-users+unsubscr...@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.
>
--
Eri
;>
>>>> Upgrade:
>>>> https://theforeman.org/plugins/katello/3.4/upgrade/index.html
>>>>
>>>> See the changelog for detailed feature issues and bug fixes:
>>>> https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md
>>&
ansformation, rooted in
> grief and rage but pointed towards vision and dreams."
>
> - Patrisse Cullors, *Black Lives Matter founder*
>
> On 29 May 2017 at 14:32, Eric D Helms <ericdhe...@gmail.com> wrote:
>
>> All,
>>
>> We are happy to announce the
://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md
Bug reporting
=
If you come across a bug in your testing, please file it and note the
version of Katello or Foreman that you're using in the report.
http://projects.theforeman.org/projects/katello/issues/new
--
Eric D. Helms
Red
uild collective power, to achieve collective transformation, rooted in
> grief and rage but pointed towards vision and dreams."
>
> - Patrice Cullors, *Black Lives Matter founder*
>
> On 28 April 2017 at 06:04, Eric D Helms <ericdhe...@gmail.com> wrote:
>
>> In conjunc
and
they are working to resolve it. Again:
DO NOT REFRESH OR IMPORT YOUR MANIFEST until the GA release.
Once this issue has been resolved you can expect the GA to follow.
[1] http://projects.theforeman.org/issues/18971
--
Eric D. Helms
Red Hat Engineering
--
You received this message because
of Katello or Foreman that you're using in the report.
http://projects.theforeman.org/projects/katello/issues/new
--
Eric D. Helms
Red Hat Engineering
--
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this grou
>
>>
>>
> --
> 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+unsubscr...@googlegroups.com.
> To p
What errors?
On Mar 22, 2017 6:59 AM, "Duncan Innes" wrote:
> Should I be running
>
> foreman-installer --scenario katello --upgrade
>
> after my yum update when upgrading from 3.3 to 3.3.1?
>
> I'm getting errors during Upgrade Step: migrate_foreman
>
> D
>
> --
> You
You'll need to regenerate a certificate tarball for each proxy and deploy
it with the installer. This is due to the hostname change on the main
server and how the certificates are used to sync from the server to the
proxy.
On Mar 14, 2017 10:12 PM, "jpavel" wrote:
> I'm
Does the sync task itself fail? If so, what do you see on the errors tab of
the task? Is Pulp throwing an error?
Thanks
Eric
On Feb 16, 2017 10:07 PM, "Edson Manners" wrote:
Hate to bump the thread but I have the same issue. Katello 3.1.
The sync worked in this repo:
Could you please file a bug report with this information including your fix
or add it to an existing report so that we can look at getting this fixed
in the upcoming 3.3 release?
Thanks
Eric
On Feb 16, 2017 11:58 PM, "Lachlan Musicman" wrote:
GOT IT.
GADDAM.
Edited
What version of Katello are you running?
On Dec 8, 2016 5:47 AM, "yannig rousseau" wrote:
> Hi all,
>
> In case anyone is interested.
> The task which recalculate "installable errata" depending on installed
> package is :
> *Generate applicability
That is correct. The client repo is all you should need on clients.
On Dec 6, 2016 12:27 AM, "Lachlan Musicman" wrote:
> Hola,
>
> Investigating the Katello repos, I see there are 4 - pulp, client,
> candlepin and katello
>
> At the moment my understanding of what these are:
The unofficial 1.13 EL6 repository has been updated to include the Foreman
1.13.2 release. This also includes rubygem-sinatra and dependencies to fix
the broken foreman-proxy installs on EL6.
--
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University
--
You received
per our normal
support policy.
--
Eric D. Helms
Red Hat Engineering
--
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+unsubscr...@google
rom it, send an
> email to foreman-users+unsubscr...@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.
>
--
redirect you to the new location on theforeman.org for a time. So please
update your bookmarks as you are redirected.
[1] https://theforeman.org/plugins/katello/
Eric
--
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University
--
You received this message because you
--
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University
--
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-user
Foreman 1.13.1 and associated plugins have now been released into this
repository for EL6.
Eric
On Tue, Oct 18, 2016 at 2:27 AM, Ivan Necas <ine...@redhat.com> wrote:
> Eric D Helms <ericdhe...@gmail.com> writes:
>
> > All,
> >
> > Given that Foreman has off
.
For Katello 3.2 RC users, expect an EL6 Katello build to follow in the next
few days.
Thanks,
Eric
[1] https://github.com/theforeman/puppet-foreman_proxy/pull/293
--
Eric D. Helms
Red Hat Engineering
--
You received this message because you are subscribed to the Google Groups
"Foreman users&q
Can you try an upload with hammer? Do you see the same behavior?
On Aug 10, 2016 5:15 AM, "Edgars M." wrote:
> Hi
>
> I have the same issue. To workaround this I had to create local repo on
> Katello server with createrepo and then sync it in Katello with
>
ails from it, send an
> email to foreman-users+unsubscr...@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.
>
roup at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>
--
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University
--
You received this message because you are subscribed to the Google Groups
"
If you come across a bug in your testing, please file it and note the
>> version of Katello that you're using in the report and set the release
>> to 3.0.2.
>>
>>http://projects.theforeman.org/projects/katello/issues/new
>>
>>
>> --
>> Eric D. Helms
>
> thanks philippe
>
> --
> 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+unsubscr...@googlegroups.com.
> To
Does the host show as having that subscription in the UI?
On Jul 18, 2016 11:23 AM, "Peter Kirby"
wrote:
> I'm facing an issue where when I attach a subscription via
> "subscription-manger attach --pool xxx" is successfully
> attaches the subscription,
Today, Katello only supports el6 and el7 installations but with a variety
of clients.
On Jul 18, 2016 9:19 AM, "Duncan Innes" wrote:
> Sorry - for installation.
>
> Was just taking the Foreman installation OS options as examples here.
>
> Ideally I'd run Katello on a CentOS7
For installation purposes or client support?
On Jul 18, 2016 8:10 AM, "Duncan Innes" wrote:
> Hi,
>
> Is Katello 3.1 not going to support the same OS platforms as Foreman 1.12
> is doing?
>
> i.e. Fedora 24 for my purpose, but others may look to Debian & Ubuntu
>
> Cheers
>
>
t;>> [ERROR 2016-07-08 10:49:15 verbose] /Stage[main]/Foreman_proxy::
>>> Register/Foreman_smartproxy[katello.tld]: Proxy katello.tld cannot be
>>> registered (Could not load data from https://katello.tld
>>> [ INFO 2016-07-08 10:49:15 verbose] - is your server dow
stop receiving emails from it, send an
> email to foreman-users+unsubscr...@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/op
ed 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+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googl
gt; from /usr/share/gems/gems/kafo-0.7.4/lib/kafo/kafo_configure.rb:
> 150:in `run'
> from /usr/sbin/foreman-installer:12:in `'
>
> Is this a bug I should report on the issue tracker or did I screw up my
> setup? Any helpful advice is appreciated, thanks for taking the
Dylan,
You've hit an error that I spent the past two days debugging for another
user but have not been able to replicate locally. Couple of questions for
you:
1) do you have a backup of your 2.4 before upgrading?
2) If yes, would you be able to privately share backups of your database
with me
For the record, we don't test or guarantee inter-RC upgrades. If you are
upgrading from 2.4, prior to the last round of commits after RC8 your
upgrade could end up in a position where the installer data is wrong or
missing values. If you are able to upgrade from your 2.4 to 3.0 we highly
recommend
allation/capsule.html
>> <http://www.katello.org/docs/2.4/installation/capsule.html>
>>
>> Bug reporting
>> =
>> If you come across a bug in your testing, please file it and note the
>> version of Katello that you're using in the report and set the release
Groups
> "Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to foreman-users+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google
ug reporting
=
If you come across a bug in your testing, please file it and note the
version of Katello that you're using in the report and set the release
to 3.0.0.
http://projects.theforeman.org/projects/katello/issues/new
--
Eric D. Helms
Red Hat Engineering
Ph.D. Student - No
74 matches
Mail list logo