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
"apply applicable erratas" task for these host and I can't get them to
resume nor cancel. I'm not sure how to clean this up since It's preventing
me from updating to katello 3.4.
errors in paused task:
404 Resource Not Found
and
host did not respond within 20 seconds. The task has been canceled. Is
katello-agent installed and goferd running on the Host?
the katello agent is installed on all managed host and the goferd agent is
running. I've even tried to restart the goferd agent without success.
I am not an expert on Katello by any stretch, but I have seen this before
and these are two methods I've used:
try running katello-tracer-upload from the affected hosts. If that
doesn't work,
rebooting the Foreman server does. You probably don't need to go that
far. Maybe just "systemctl restart foreman-tasks"
Cheers
L.
···
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 the issues with these host. Now I have
several paused “apply applicable erratas” task for these host and I can’t
get them to resume nor cancel. I’m not sure how to clean this up since
It’s preventing me from updating to katello 3.4.
errors in paused task:
404 Resource Not Found
and
host did not respond within 20 seconds. The task has been canceled. Is
katello-agent installed and goferd running on the Host?
the katello agent is installed on all managed host and the goferd agent is
running. I’ve even tried to restart the goferd agent without success.
Looking at one of my servers I'm not finding a katello-tracer-upload. I do
see a katell-package-uploader and katello-rhsm-cunsumer. "yum provides
*/katello-tracer-upload" reruns no results.
After rebooting the foreman server i still get a fail on the upgrade check
stating that 15 active task. The only thing I can find are these same
failed apply erratas task.
···
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 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 "apply applicable erratas" task for these host and I can't
>> get them to resume nor cancel. I'm not sure how to clean this up since
>> It's preventing me from updating to katello 3.4.
>>
>>
>> errors in paused task:
>>
>> 404 Resource Not Found
>>
>> and
>>
>> host did not respond within 20 seconds. The task has been canceled. Is
>> katello-agent installed and goferd running on the Host?
>>
>> the katello agent is installed on all managed host and the goferd agent
>> is running. I've even tried to restart the goferd agent without success.
>>
>
> I am not an expert on Katello by any stretch, but I have seen this before
> and these are two methods I've used:
> - try running katello-tracer-upload from the affected hosts. If that
> doesn't work,
> - rebooting the Foreman server does. You probably don't need to go that
> far. Maybe just "systemctl restart foreman-tasks"
>
> Cheers
> L.
>
>
>
My search shows that katello-tracer-upload comes from katello-agent-3.0.0-2
or katello-host-tools-3.0.2-1 (caveat: I am using the katello 3.4 repo) -
look for those packages?
cheers
L.
···
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 the issues with these host. Now I have
several paused “apply applicable erratas” task for these host and I can’t
get them to resume nor cancel. I’m not sure how to clean this up since
It’s preventing me from updating to katello 3.4.
errors in paused task:
404 Resource Not Found
and
host did not respond within 20 seconds. The task has been canceled. Is
katello-agent installed and goferd running on the Host?
the katello agent is installed on all managed host and the goferd agent
is running. I’ve even tried to restart the goferd agent without success.
I am not an expert on Katello by any stretch, but I have seen this before
and these are two methods I’ve used:
try running katello-tracer-upload from the affected hosts. If that
doesn’t work,
rebooting the Foreman server does. You probably don’t need to go that
far. Maybe just “systemctl restart foreman-tasks”
Looking at one of my servers I’m not finding a katello-tracer-upload. I
do see a katell-package-uploader and katello-rhsm-cunsumer. “yum provides
*/katello-tracer-upload” reruns no results.
After rebooting the foreman server i still get a fail on the upgrade check
stating that 15 active task. The only thing I can find are these same
failed apply erratas task.
"The antidote to apocalypticism is apocalyptic civics. Apocalyptic civics
is the insistence that we cannot ignore the truth, nor should we panic
about it. It is a shared consciousness that our institutions have failed
and our ecosystem is collapsing, yet we are still here — and we are
creative agents who can shape our destinies. Apocalyptic civics is the
conviction that the only way out is through, and the only way through is
together. "
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 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 "apply applicable erratas" task for these host and I can't
>> get them to resume nor cancel. I'm not sure how to clean this up since
>> It's preventing me from updating to katello 3.4.
>>>
>>>
>>>>
>>>> errors in paused task:
>>>>
>>>> 404 Resource Not Found
>>>>
>>>> and
>>>>
>>>> host did not respond within 20 seconds. The task has been canceled.
>>>> Is katello-agent installed and goferd running on the Host?
>>>>
>>>> the katello agent is installed on all managed host and the goferd agent
>>>> is running. I've even tried to restart the goferd agent without success.
>>>>
>>>
>>> I am not an expert on Katello by any stretch, but I have seen this
>>> before and these are two methods I've used:
>>> - try running katello-tracer-upload from the affected hosts. If that
>>> doesn't work,
>>> - rebooting the Foreman server does. You probably don't need to go that
>>> far. Maybe just "systemctl restart foreman-tasks"
>>>
>>>
>>> Looking at one of my servers I'm not finding a katello-tracer-upload. I
>> do see a katell-package-uploader and katello-rhsm-cunsumer. "yum provides
>> */katello-tracer-upload" reruns no results.
>>
>> After rebooting the foreman server i still get a fail on the upgrade
>> check stating that 15 active task. The only thing I can find are these
>> same failed apply erratas task.
>>
>>
>>
>
> My search shows that katello-tracer-upload comes from
> katello-agent-3.0.0-2 or katello-host-tools-3.0.2-1 (caveat: I am using the
> katello 3.4 repo) - look for those packages?
>
> cheers
> L.
>
>
> ------
> "The antidote to apocalypticism is *apocalyptic civics*. Apocalyptic
> civics is the insistence that we cannot ignore the truth, nor should we
> panic about it. It is a shared consciousness that our institutions have
> failed and our ecosystem is collapsing, yet we are still here — and we are
> creative agents who can shape our destinies. Apocalyptic civics is the
> conviction that the only way out is through, and the only way through is
> together. "
>
> *Greg Bloom* @greggish
> https://twitter.com/greggish/status/873177525903609857
>
You might have to modify the "STATES" parameter (running/paused). Running
the commands with "NOOP=true" does not actually do anything but shows you
how many tasks would be removed were you to remove said parameter.
Hope this helps.
Pascal
···
On Monday, October 30, 2017 at 8:04:09 PM UTC+1, Edward Clay wrote:
>
> 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 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 "apply applicable erratas" task for these host and I can't
>>> get them to resume nor cancel. I'm not sure how to clean this up since
>>> It's preventing me from updating to katello 3.4.
>>>>
>>>>
>>>>>
>>>>> errors in paused task:
>>>>>
>>>>> 404 Resource Not Found
>>>>>
>>>>> and
>>>>>
>>>>> host did not respond within 20 seconds. The task has been canceled.
>>>>> Is katello-agent installed and goferd running on the Host?
>>>>>
>>>>> the katello agent is installed on all managed host and the goferd
>>>>> agent is running. I've even tried to restart the goferd agent without
>>>>> success.
>>>>>
>>>>
>>>> I am not an expert on Katello by any stretch, but I have seen this
>>>> before and these are two methods I've used:
>>>> - try running katello-tracer-upload from the affected hosts. If that
>>>> doesn't work,
>>>> - rebooting the Foreman server does. You probably don't need to go
>>>> that far. Maybe just "systemctl restart foreman-tasks"
>>>>
>>>>
>>>> Looking at one of my servers I'm not finding a katello-tracer-upload.
>>> I do see a katell-package-uploader and katello-rhsm-cunsumer. "yum
>>> provides */katello-tracer-upload" reruns no results.
>>>
>>> After rebooting the foreman server i still get a fail on the upgrade
>>> check stating that 15 active task. The only thing I can find are these
>>> same failed apply erratas task.
>>>
>>>
>>>
>>
>> My search shows that katello-tracer-upload comes from
>> katello-agent-3.0.0-2 or katello-host-tools-3.0.2-1 (caveat: I am using the
>> katello 3.4 repo) - look for those packages?
>>
>> cheers
>> L.
>>
>>
>> ------
>> "The antidote to apocalypticism is *apocalyptic civics*. Apocalyptic
>> civics is the insistence that we cannot ignore the truth, nor should we
>> panic about it. It is a shared consciousness that our institutions have
>> failed and our ecosystem is collapsing, yet we are still here — and we are
>> creative agents who can shape our destinies. Apocalyptic civics is the
>> conviction that the only way out is through, and the only way through is
>> together. "
>>
>> *Greg Bloom* @greggish
>> https://twitter.com/greggish/status/873177525903609857
>>
>
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 October 2017 13:04:09 UTC-6, Edward Clay wrote:
>
> 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 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 "apply applicable erratas" task for these host and I can't
>>> get them to resume nor cancel. I'm not sure how to clean this up since
>>> It's preventing me from updating to katello 3.4.
>>>>
>>>>
>>>>>
>>>>> errors in paused task:
>>>>>
>>>>> 404 Resource Not Found
>>>>>
>>>>> and
>>>>>
>>>>> host did not respond within 20 seconds. The task has been canceled.
>>>>> Is katello-agent installed and goferd running on the Host?
>>>>>
>>>>> the katello agent is installed on all managed host and the goferd
>>>>> agent is running. I've even tried to restart the goferd agent without
>>>>> success.
>>>>>
>>>>
>>>> I am not an expert on Katello by any stretch, but I have seen this
>>>> before and these are two methods I've used:
>>>> - try running katello-tracer-upload from the affected hosts. If that
>>>> doesn't work,
>>>> - rebooting the Foreman server does. You probably don't need to go
>>>> that far. Maybe just "systemctl restart foreman-tasks"
>>>>
>>>>
>>>> Looking at one of my servers I'm not finding a katello-tracer-upload.
>>> I do see a katell-package-uploader and katello-rhsm-cunsumer. "yum
>>> provides */katello-tracer-upload" reruns no results.
>>>
>>> After rebooting the foreman server i still get a fail on the upgrade
>>> check stating that 15 active task. The only thing I can find are these
>>> same failed apply erratas task.
>>>
>>>
>>>
>>
>> My search shows that katello-tracer-upload comes from
>> katello-agent-3.0.0-2 or katello-host-tools-3.0.2-1 (caveat: I am using the
>> katello 3.4 repo) - look for those packages?
>>
>> cheers
>> L.
>>
>>
>> ------
>> "The antidote to apocalypticism is *apocalyptic civics*. Apocalyptic
>> civics is the insistence that we cannot ignore the truth, nor should we
>> panic about it. It is a shared consciousness that our institutions have
>> failed and our ecosystem is collapsing, yet we are still here — and we are
>> creative agents who can shape our destinies. Apocalyptic civics is the
>> conviction that the only way out is through, and the only way through is
>> together. "
>>
>> *Greg Bloom* @greggish
>> https://twitter.com/greggish/status/873177525903609857
>>
>
···
On Monday, 30 October 2017 14:13:24 UTC-6, pascalp wrote:
>
> 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-d3d4d00426cc"' STATES="running"
> NOOP=true
>
> You might have to modify the "STATES" parameter (running/paused). Running
> the commands with "NOOP=true" does not actually do anything but shows you
> how many tasks would be removed were you to remove said parameter.
>
> Hope this helps.
> Pascal
>
> On Monday, October 30, 2017 at 8:04:09 PM UTC+1, Edward Clay wrote:
>>
>> 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 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 "apply applicable erratas" task for these host and I can't
>>>> get them to resume nor cancel. I'm not sure how to clean this up since
>>>> It's preventing me from updating to katello 3.4.
>>>>>
>>>>>
>>>>>>
>>>>>> errors in paused task:
>>>>>>
>>>>>> 404 Resource Not Found
>>>>>>
>>>>>> and
>>>>>>
>>>>>> host did not respond within 20 seconds. The task has been canceled.
>>>>>> Is katello-agent installed and goferd running on the Host?
>>>>>>
>>>>>> the katello agent is installed on all managed host and the goferd
>>>>>> agent is running. I've even tried to restart the goferd agent without
>>>>>> success.
>>>>>>
>>>>>
>>>>> I am not an expert on Katello by any stretch, but I have seen this
>>>>> before and these are two methods I've used:
>>>>> - try running katello-tracer-upload from the affected hosts. If that
>>>>> doesn't work,
>>>>> - rebooting the Foreman server does. You probably don't need to go
>>>>> that far. Maybe just "systemctl restart foreman-tasks"
>>>>>
>>>>>
>>>>> Looking at one of my servers I'm not finding a katello-tracer-upload.
>>>> I do see a katell-package-uploader and katello-rhsm-cunsumer. "yum
>>>> provides */katello-tracer-upload" reruns no results.
>>>>
>>>> After rebooting the foreman server i still get a fail on the upgrade
>>>> check stating that 15 active task. The only thing I can find are these
>>>> same failed apply erratas task.
>>>>
>>>>
>>>>
>>>
>>> My search shows that katello-tracer-upload comes from
>>> katello-agent-3.0.0-2 or katello-host-tools-3.0.2-1 (caveat: I am using the
>>> katello 3.4 repo) - look for those packages?
>>>
>>> cheers
>>> L.
>>>
>>>
>>> ------
>>> "The antidote to apocalypticism is *apocalyptic civics*. Apocalyptic
>>> civics is the insistence that we cannot ignore the truth, nor should we
>>> panic about it. It is a shared consciousness that our institutions have
>>> failed and our ecosystem is collapsing, yet we are still here — and we are
>>> creative agents who can shape our destinies. Apocalyptic civics is the
>>> conviction that the only way out is through, and the only way through is
>>> together. "
>>>
>>> *Greg Bloom* @greggish
>>> https://twitter.com/greggish/status/873177525903609857
>>>
>>
