This did the trick.
# foreman-rake foreman_tasks:cleanup
TASK_SEARCH='label="Actions::Katello::Host::Erratum::ApplicableErrataInstall"'
STATES="paused"
Thanks for the insight.
On Monday, 30 October 2017 14:13:24 UTC-6, pascalp wrote:
>
> You could try to either stop the tasks by label - exampl
Does anyone know of a katello-tracer-upload equivalent command for centos
6.x? I've tried katello-package-upload -f but it doesn't seem to have the
same affect as katello-trace-upload. Also it seems odd that the 3.4
agent/client would be so different between OS versions.
On Monday, 30 Octobe
You could try to either stop the tasks by label - example:
sudo foreman-rake foreman_tasks:cleanup
TASK_SEARCH='label="Actions::Katello::Repository::Sync"' STATES="running"
NOOP=true
or by id - example:
sudo foreman-rake foreman_tasks:cleanup
TASK_SEARCH='id="aa929825-4fc6-4138-9b12-d3d4d0042
Looking at this futher, it looks like the katello-tracer-uploader is
available for COS7 but I'm not finding it for CentOS 6.x.
On Wednesday, 25 October 2017 15:25:47 UTC-6, Lachlan Musicman wrote:
>
> On 26 October 2017 at 04:39, Edward Clay > wrote:
>
>> I have some host that I attempted to app
On 26 October 2017 at 04:39, Edward Clay wrote:
> I have some host that I attempted to apply applicable erratas to in a
> large group of host. During that task some host failed and others
> completed. I can't remember why they failed but I was able to manually
> update the systems once I fixed
On Tuesday, 17 October 2017 16:48:37 UTC-6, Lachlan Musicman wrote:
>
> On 18 October 2017 at 09:20, Edward Clay > wrote:
>
>> I have some host that I attempted to apply applicable erratas to in a
>> large group of host. During that task some host failed and others
>> completed. I can't reme
On 18 October 2017 at 09:20, Edward Clay wrote:
> I have some host that I attempted to apply applicable erratas to in a
> large group of host. During that task some host failed and others
> completed. I can't remember why they failed but I was able to manually
> update the systems once I fixed
I have some host that I attempted to apply applicable erratas to in a large
group of host. During that task some host failed and others completed. I
can't remember why they failed but I was able to manually update the
systems once I fixed the issues with these host. Now I have several paused
Devin,
This is a recently found issue with a change in the remote execution plugin
version in the 1.15 plugin repository. A fix has been proposed already and
will be included in 3.4.1. Since this was an upgrade you likely already had
the templates seeded. However, this means the rest of the upgrad
I upgraded today from 3.3 to 3.4 version of Katello. It appears that the
upgrade worked cause I am able to log into Katello and from what I can tell
everything is working, however it died at the Upgrade Step of "db_seed",
not sure if this is expected, or if I need to worry about it? I did
snaps
Edward,
The katello-agent is actually running as 'goferd' on the system. When you
install this service gets started which triggers initial uploads for
package profiles and enabled repositories. Subsequent actions on the host
will re-trigger these events (e.g. yum update will re-trigger package
upl
Thanks Eric for the quick response. is there some service that runs on
the system or is it called by something? Just trying 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
The service you are looking for is when you installed katello-agent. This
package includes utilities that upload the hosts package profile and
enabled repositories to Katello which allow errata to be calculated.
Eric
On Tue, May 30, 2017 at 6:46 PM, Edward Clay
wrote:
> Can anyone tell me what
Can anyone tell me what software/agent/code is used to to inform
katello/foreman that a system is either up to date or needs patches (aka
erratas that apply to host) and what executes it? From what I've come up
with thus far, I perform the following task on a host and then everything
is good.
Hello Team,
Im trying to setup katello 3.3 on CentOS 7, While running the final setup.
foreman-installer --scenario katello --foreman-admin-username admin
--foreman-admin-password admin
Im getting the errror like below.
/Stage[main]/Qpid::Service/Service[qpidd]/ensure: change from stopped t
In a previous thread I brought up naming/organizing. I thought I had all
this worked out but now my design and activation keys aren't working as
expected.
1. I don't see that there is any scenario where using multiple keys works
1. Only one content-view is ever selected subscription-mana
we have the same issue running out of memory while searching for specific
hosts in foreman 1.14.2.
Am Donnerstag, 2. März 2017 09:34:57 UTC+1 schrieb Cristian Falcas:
>
> The machine has 32 GB.
>
> We run here tomcat (candlepin), puppetdb, foreman and postgresql db.
>
> On Thu, Mar 2, 2017 at 12:
The machine has 32 GB.
We run here tomcat (candlepin), puppetdb, foreman and postgresql db.
On Thu, Mar 2, 2017 at 12:24 AM, John Mitsch wrote:
> Cristian,
>
> how much memory do you have on the machine you are running katello/foreman
> on?
>
> -John
>
> John Mitsch
> Red Hat Engineering
> (860
Cristian,
how much memory do you have on the machine you are running katello/foreman
on?
-John
John Mitsch
Red Hat Engineering
(860)-967-7285
irc: jomitsch
On Wed, Mar 1, 2017 at 7:02 AM, Cristian Falcas
wrote:
> Hi,
>
> I'm trying to see the hosts in Error state from the Dashboard.
>
> When
7;,
changes => 'set enabled 0',
onlyif => 'match name size > 0',
}
augeas { 'yum-repo-disable-centos-fasttrack':
context => '/files/etc/yum.repos.d/CentOS-fasttrack.repo/fasttrack',
changes => 'set enabled 0',
onlyif => '
ms['kt_activation_keys'] %>"
>
> <% unless @host.operatingsystem.atomic? %>
> echo "Installing Katello Agent"
> yum -t -y -e 0 install katello-agent
> chkconfig goferd on
> <% end %>
> <% end %>
>
>
>
&g
tion_keys'] %>"
<% unless @host.operatingsystem.atomic? %>
echo "Installing Katello Agent"
yum -t -y -e 0 install katello-agent
chkconfig goferd on
<% end %>
<% end %>
From: "Duncan Innes"
To: "Foreman Users"
Sent: Wednesday, March
I've taken the rather extreme option of deleting the "CentOS-*.repo" files
from /etc/yum.repos.d/ at the start of the %post section. Bit harsh, but
it proved the theory was sound. I can now perform successful builds with
no external access.
This can't be the 'right' way to do it though. Is t
Do you do that during kickstart or once booted? I think at the point of
trying to install subscription-manager, my hosts only have the external
repos configured, so there's no way to satisfy the install internally.
I've edited the Katello Kickstart Default template to include
subscription-mana
Hi,
I'm trying to see the hosts in Error state from the Dashboard.
When I click the Error from Host Configuration Chart, the new page never
loads (the same happens with Active hosts).
This is the url that it's executed is:
https://puppet.company.net/hosts?utf8=%E2%9C%93&search=last_report+%3E+%
I don't know if there's an automagic way to do it, but I use ansible to
change all files in /etc/yum.repos.d/ except "redhat.repo". In each file
change any enabled =1 to enabled = 0.
cheers
L.
--
The most dangerous phrase in the language is, "We've always done it this
way."
- Grace Hopper
O
Hi,
I've built a new Katello 3.3 system and loaded it up with CentOS 7, EPEL,
and Katello Client 3.3 channels. The various repositories have been
synched (although lazy sync). Content View, Activation Key etc created.
When I build a new system, however, the installation of
subscription-manage
We are happy to announce the release of Katello 3.3 (Baltic Porter).
A list of the changes in Katello 3.3 is in our release notes:
https://theforeman.org/plugins/katello/3.3/release_notes/release_notes.html
One known issue is a breakage in upgrades from puppet 3 to puppet 4
(http://projects.th
Thank you. Expectantly waiting for production release. :)
Dne pondělí 30. ledna 2017 22:06:35 UTC+1 jsherril napsal(a):
>
> We are happy to announce the second release candidate for Katello 3.3 (Baltic
> Porter).
>
> Your help is appreciated to ensure our GA release is solid, by either
> installi
Thanks for the info.
I should check this out soon.
2017년 1월 31일 화요일 오전 6시 6분 35초 UTC+9, jsherril 님의 말:
>
> We are happy to announce the second release candidate for Katello 3.3 (Baltic
> Porter).
>
> Your help is appreciated to ensure our GA release is solid, by either
> installing a new instanc
We are happy to announce the second release candidate for Katello 3.3
(Baltic Porter).
Your help is appreciated to ensure our GA release is solid, by either
installing a new instance or upgrading a test server.
A list of the changes in Katello 3.3 is in our release notes:
https://theforeman.org
On 01/11/2017 10:14 AM, Justin Sherrill wrote:
We are happy to announce the first release candidate for Katello 3.3
(Baltic Porter).
Your help is appreciated to ensure our GA release is solid, by either
installing a new instance or upgrading a test server.
A list of the changes in Katello 3.3
We are happy to announce the first release candidate for Katello 3.3
(Baltic Porter).
Your help is appreciated to ensure our GA release is solid, by either
installing a new instance or upgrading a test server.
A list of the changes in Katello 3.3 is in our release notes:
https://theforeman.org/
33 matches
Mail list logo
