I did an update from Katello 3.4 -> 3.5 yesterday and ran into what looks
like it might be a packaging issue.
The original symptom was that remote execution was broken. It took me a
little while but then I realized that I still had the 1.15 remote execution
packages installed instead of the
I had reasonable success using this one-liner fix from the pulp team when I
was stuck on 3.4.0.
https://github.com/pulp/pulp/pull/3047/
I had to force recalc errata applicability for some hosts to get them to
show applicable packages after applying this fix, but once that was done,
this kept
Is it possible we have a regression on this issue? I know it was fixed back
in September 2016 but I ran into what looks like the same issue with
Katello 3.4.4 today.
I pulled in a new version of Puppet stdlib a week or two ago when I
published a new version of some Content Views.
Today, I
I reported this issue also. Unfortunately - the fix didn't make it into
Katello 3.4.3 but it looks like it should be in 3.4.4 when it releases.
http://projects.theforeman.org/issues/19959
--
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To
FYI - I opened an issue last week about this.
http://projects.theforeman.org/issues/20088
On Tuesday, June 27, 2017 at 5:40:00 PM UTC-4, Eric Helms wrote:
>
> I'll look into this discrepancy. This is likely due to the migration we
> had to make and rebuild our RPM build server. Stay tuned.
I was applying patches to a system yesterday and ran into a problem.
The yum transaction (initiated from Katello as part of a host_collection
update operation) failed with a "too many open files" type error.
Transaction ID : 22
Begin time : Sun Apr 23 06:58:51 2017
Begin rpmdb:
Thank you. Both the workaround and the PR are working great for me.
On Friday, January 27, 2017 at 8:02:51 AM UTC-5, Daniel Lobato wrote:
>
> On 01/26, Tony Coffman wrote:
> > I'm testing Katello 3.3 RC1 and attempting to integrate foreman_ansible,
> > dynamic inventory, and
I'm testing Katello 3.3 RC1 and attempting to integrate foreman_ansible,
dynamic inventory, and the ansible proxy into my test scenario.
I've imported my ansible roles and assigned parameters in Foreman and from
the command line all is well.
I've run into a roadblock when I try to run the
198GB - about 20 content views. 2.4 -> 3.0 upgrade ran in just under 4
hours.
--
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
