[Katello] Pulp repos sync on schedule but not showing in katello

Alan_Evans · March 31, 2017, 8:41pm

Hello,

I am using Katello 3.3/Foreman 1.14.2. I have a fresh install and I
created new Sync plan, product and repos with hammer. At first I didn't
think the jobs were running at all, but I read a thread here that got me
looking at things and I found that pulp is in fact syncing on schedule but
the results aren't appearing in the katello UI/Hammer CLI. I suspect there
is some kind of post sync job that has to happen that isn't. If I manually
sync them from the UI then the UI is updated.

Thoughts?

-Alan

John_Mitsch · April 4, 2017, 9:35pm

Alan,

I don't have much experience with Sync Plans, but I would expect they
would create syncing tasks in Katello. You can look at your pulp tasks
using pulp-admin, see if you see any activity corresponding to your sync
plans there.

yum install pulp-admin-client pulp-rpm-admin-extensions.noarch
pulp-rpm-handlers.noarch
pulpAdminPassword=$(grep ^default_password /etc/pulp/server.conf | cut -d'
' -f2)
pulp-admin -u admin -p $pulpAdminPassword tasks list

-John

John Mitsch
Red Hat Engineering
(860)-967-7285
irc: jomitsch

···

On Fri, Mar 31, 2017 at 4:41 PM, Alan Evans wrote:

Hello,

I am using Katello 3.3/Foreman 1.14.2. I have a fresh install and I
created new Sync plan, product and repos with hammer. At first I didn’t
think the jobs were running at all, but I read a thread here that got me
looking at things and I found that pulp is in fact syncing on schedule but
the results aren’t appearing in the katello UI/Hammer CLI. I suspect there
is some kind of post sync job that has to happen that isn’t. If I manually
sync them from the UI then the UI is updated.

Thoughts?

-Alan

–
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.

Anthony_Chevalet · August 3, 2017, 1:13pm

Hello,

Any news on this? Bug report?
I have the same behavior for ages (katello 3.0?), and it's still there with
foreman 1.15.2/Katello 3.4.3.

Thanks,
Anthony

···

Le vendredi 31 mars 2017 22:41:46 UTC+2, Alan Evans a écrit : > > Hello, > > I am using Katello 3.3/Foreman 1.14.2. I have a fresh install and I > created new Sync plan, product and repos with hammer. At first I didn't > think the jobs were running at all, but I read a thread here that got me > looking at things and I found that pulp is in fact syncing on schedule but > the results aren't appearing in the katello UI/Hammer CLI. I suspect there > is some kind of post sync job that has to happen that isn't. If I manually > sync them from the UI then the UI is updated. > > Thoughts? > > -Alan > > > > >

Alan_Evans · April 6, 2017, 10:12pm

Thanks John.

I've been poking around at this for a couple of days. I have looked at the
tasks and was going to share but didn't want to overwhelm anyone that tried
to help.

A plain 'tasks list' gives nothing.

$ sudo pulp-admin tasks list

···

+----------------------------------------------------------------------+ Tasks +----------------------------------------------------------------------+

No tasks found

tasks list --all, gives a lot, so I’ll pull out a few sections

$ sudo pulp-admin tasks list -a | grep -A5 My_Org-centos-centos-6-x86_64-os

Resources: My_Org-centos-centos-6-x86_64-os (repository)
State: Successful
Start Time: 2017-04-05T19:31:00Z
Finish Time: 2017-04-05T19:31:07Z
Task Id: dd6e6dac-5988-4cc3-be6c-95b223936f98

–
Resources: My_Org-centos-centos-6-x86_64-os (repository)
State: Successful
Start Time: 2017-04-05T19:31:07Z
Finish Time: 2017-04-05T19:31:07Z
Task Id: 2d9ec7cd-de30-44d7-a3b1-8a10e1aa7257

–
Resources: My_Org-centos-centos-6-x86_64-os (repository)
State: Successful
Start Time: 2017-04-06T19:36:55Z
Finish Time: 2017-04-06T19:37:02Z
Task Id: d8cb7dac-b13c-4420-83a3-432f1c06c635

–
Resources: My_Org-centos-centos-6-x86_64-os (repository)
State: Successful
Start Time: 2017-04-06T19:37:02Z
Finish Time: 2017-04-06T19:37:02Z
Task Id: 19543dbd-fe67-4442-b56e-c3b0d91d695a

$ TZ=UTC date
Thu Apr 6 21:18:46 UTC 2017

You can see that for the repo centos-6-os repo, pulp has synced and
published the repo for the last couple of days. But you can see that
Katello seems to think the last sync was almost a week ago.

$ hammer repository info --id 1
ID: 1
Name: CentOS 6 x86_64 OS
Label: centos-6-x86_64-os
Organization: My Org
Red Hat Repository: no
Content Type: yum
Checksum Type: sha256
Mirror on Sync: yes
URL: http://mirror.centos.org/centos/6/os/x86_64/
Publish Via HTTP: yes
Published At: http:
//katello.example.com/pulp/repos/My_Org/Library/custom/centos/centos-6-x86_64-os/
Relative Path: My_Org/Library/custom/centos/centos-6-x86_64-os
Download Policy: on_demand
Product:
ID: 1
Name: CentOS
GPG Key:
ID: 2
Name: RPM-GPG-KEY-CentOS-6
Sync:
Status: Success
Last Sync Date: 6 days
Created: 2017/03/31 00:26:52
Updated: 2017/03/31 20:47:13
Content Counts:
Packages: 6696
Package Groups: 214
Errata: 0

But get this, if I sync it from Katello it will update.

$ hammer repository synchronize --id 1
[…] [100
%]
No new packages.

$ hammer repository info --id 1
ID: 1
Name: CentOS 6 x86_64 OS
Label: centos-6-x86_64-os
Organization: My Org
Red Hat Repository: no
Content Type: yum
Checksum Type: sha256
Mirror on Sync: yes
URL: http://mirror.centos.org/centos/6/os/x86_64/
Publish Via HTTP: yes
Published At: http:
//katello.example.com/pulp/repos/My_Org/Library/custom/centos/centos-6-x86_64-os/
Relative Path: My_Org/Library/custom/centos/centos-6-x86_64-os
Download Policy: on_demand
Product:
ID: 1
Name: CentOS
GPG Key:
ID: 2
Name: RPM-GPG-KEY-CentOS-6
Sync:
Status: Success
Last Sync Date: 3 minutes
Created: 2017/03/31 00:26:52
Updated: 2017/03/31 20:47:13
Content Counts:
Packages: 6696
Package Groups: 214
Errata: 670

$ sudo pulp-admin tasks list -a | grep -A5 My_Org-centos-centos-6-x86_64-os

Resources: My_Org-centos-centos-6-x86_64-os (repository)
State: Successful
Start Time: 2017-04-06T21:26:15Z
Finish Time: 2017-04-06T21:26:22Z
Task Id: 1565fbd3-ea26-4e43-8551-40fb8e5b2850

–
Resources: My_Org-centos-centos-6-x86_64-os (repository)
State: Successful
Start Time: 2017-04-06T21:26:22Z
Finish Time: 2017-04-06T21:26:22Z
Task Id: 75beb6a0-0b3f-4b61-8eb9-a88dc27168e3

$ TZ=UTC date
Thu Apr 6 21:31:49 UTC 2017

Thank you,
-Alan

On Tuesday, April 4, 2017 at 3:36:14 PM UTC-6, John Mitsch wrote:

Alan,

I don’t have much experience with Sync Plans, but I would expect they
would create syncing tasks in Katello. You can look at your pulp tasks
using pulp-admin, see if you see any activity corresponding to your sync
plans there.

yum install pulp-admin-client pulp-rpm-admin-extensions.noarch
pulp-rpm-handlers.noarch
pulpAdminPassword=$(grep ^default_password /etc/pulp/server.conf | cut -d’
’ -f2)
pulp-admin -u admin -p $pulpAdminPassword tasks list

-John

John Mitsch
Red Hat Engineering
(860)-967-7285
irc: jomitsch

On Fri, Mar 31, 2017 at 4:41 PM, Alan Evans <alanw...@gmail.com > <javascript:>> wrote:

Hello,

I am using Katello 3.3/Foreman 1.14.2. I have a fresh install and I
created new Sync plan, product and repos with hammer. At first I didn’t
think the jobs were running at all, but I read a thread here that got me
looking at things and I found that pulp is in fact syncing on schedule but
the results aren’t appearing in the katello UI/Hammer CLI. I suspect there
is some kind of post sync job that has to happen that isn’t. If I manually
sync them from the UI then the UI is updated.

Thoughts?

-Alan

–
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...@googlegroups.com <javascript:>.
To post to this group, send email to forema...@googlegroups.com
<javascript:>.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

ehelms · August 3, 2017, 6:01pm

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 most obvious thing to check is if you see tasks that result from this
and if you see API hits to Katello for the sync notification URL. You can
find this in /etc/foreman/plugins/katello.yaml.

We need to figure out if Pulp is hitting Katello and the errors like there
or if Pulp is not configured to http notify.

···

On Aug 3, 2017 9:13 AM, "Anthony Chevalet" wrote:

Hello,

Any news on this? Bug report?
I have the same behavior for ages (katello 3.0?), and it’s still there
with foreman 1.15.2/Katello 3.4.3.

Thanks,
Anthony

Le vendredi 31 mars 2017 22:41:46 UTC+2, Alan Evans a écrit :

Hello,

I am using Katello 3.3/Foreman 1.14.2. I have a fresh install and I
created new Sync plan, product and repos with hammer. At first I didn’t
think the jobs were running at all, but I read a thread here that got me
looking at things and I found that pulp is in fact syncing on schedule but
the results aren’t appearing in the katello UI/Hammer CLI. I suspect there
is some kind of post sync job that has to happen that isn’t. If I manually
sync them from the UI then the UI is updated.

Thoughts?

-Alan

–
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.

Jason_B_Nance · April 6, 2017, 10:23pm

Hi Alan,

In the web UI have you created a sync plan (Content -> Sync Plans) and associated that sync plan with each of your products? And if so, are the results of those tasks successful (Monitor -> Tasks)?

Regards,

j

···

From: "Alan Evans" To: "Foreman Users" Sent: Thursday, April 6, 2017 5:12:54 PM Subject: Re: [foreman-users] [Katello] Pulp repos sync on schedule but not showing in katello

Thanks John.
I’ve been poking around at this for a couple of days. I have looked at the tasks and was going to share but didn’t want to overwhelm anyone that tried to help.

A plain ‘tasks list’ gives nothing.

$ sudo pulp - admin tasks list
±---------------------------------------------------------------------+
Tasks
±---------------------------------------------------------------------+

No tasks found

tasks list --all, gives a lot, so I’ll pull out a few sections

$ sudo pulp - admin tasks list - a | grep - A5 My_Org - centos - centos - 6 - x86_64 - os

Resources : My_Org - centos - centos - 6 - x86_64 - os ( repository )
State : Successful
Start Time : 2017 - 04 - 05T19 : 31 : 00Z
Finish Time : 2017 - 04 - 05T19 : 31 : 07Z
Task Id : dd6e6dac - 5988 - 4cc3 - be6c - 95b223936f98

–
Resources : My_Org - centos - centos - 6 - x86_64 - os ( repository )
State : Successful
Start Time : 2017 - 04 - 05T19 : 31 : 07Z
Finish Time : 2017 - 04 - 05T19 : 31 : 07Z
Task Id : 2d9ec7cd - de30 - 44d7 - a3b1 - 8a10e1aa7257

–
Resources : My_Org - centos - centos - 6 - x86_64 - os ( repository )
State : Successful
Start Time : 2017 - 04 - 06T19 : 36 : 55Z
Finish Time : 2017 - 04 - 06T19 : 37 : 02Z
Task Id : d8cb7dac - b13c - 4420 - 83a3 - 432f1c06c635

–
Resources : My_Org - centos - centos - 6 - x86_64 - os ( repository )
State : Successful
Start Time : 2017 - 04 - 06T19 : 37 : 02Z
Finish Time : 2017 - 04 - 06T19 : 37 : 02Z
Task Id : 19543dbd - fe67 - 4442 - b56e - c3b0d91d695a

$ TZ = UTC date
Thu Apr 6 21 : 18 : 46 UTC 2017

You can see that for the repo centos-6-os repo, pulp has synced and published the repo for the last couple of days. But you can see that Katello seems to think the last sync was almost a week ago.

$ hammer repository info – id 1
ID : 1
Name : CentOS 6 x86_64 OS
Label : centos - 6 - x86_64 - os
Organization : My Org
Red Hat Repository : no
Content Type : yum
Checksum Type : sha256
Mirror on Sync : yes
URL : http : //mirror.centos.org/centos/6/os/x86_64/
Publish Via HTTP : yes
Published At : http : //katello.example.com/pulp/repos/My_Org/Library/custom/centos/centos-6-x86_64-os/
Relative Path : My_Org / Library / custom / centos / centos - 6 - x86_64 - os
Download Policy : on_demand
Product :
ID : 1
Name : CentOS
GPG Key :
ID : 2
Name : RPM - GPG - KEY - CentOS - 6
Sync :
Status : Success
Last Sync Date : 6 days
Created : 2017 / 03 / 31 00 : 26 : 52
Updated : 2017 / 03 / 31 20 : 47 : 13
Content Counts :
Packages : 6696
Package Groups : 214
Errata : 0

But get this, if I sync it from Katello it will update.

$ hammer repository synchronize – id 1
[…] [ 100 %]
No new packages .

$ hammer repository info – id 1
ID : 1
Name : CentOS 6 x86_64 OS
Label : centos - 6 - x86_64 - os
Organization : My Org
Red Hat Repository : no
Content Type : yum
Checksum Type : sha256
Mirror on Sync : yes
URL : http : //mirror.centos.org/centos/6/os/x86_64/
Publish Via HTTP : yes
Published At : http : //katello.example.com/pulp/repos/My_Org/Library/custom/centos/centos-6-x86_64-os/
Relative Path : My_Org / Library / custom / centos / centos - 6 - x86_64 - os
Download Policy : on_demand
Product :
ID : 1
Name : CentOS
GPG Key :
ID : 2
Name : RPM - GPG - KEY - CentOS - 6
Sync :
Status : Success
Last Sync Date : 3 minutes
Created : 2017 / 03 / 31 00 : 26 : 52
Updated : 2017 / 03 / 31 20 : 47 : 13
Content Counts :
Packages : 6696
Package Groups : 214
Errata : 670

$ sudo pulp - admin tasks list - a | grep - A5 My_Org - centos - centos - 6 - x86_64 - os

Resources : My_Org - centos - centos - 6 - x86_64 - os ( repository )
State : Successful
Start Time : 2017 - 04 - 06T21 : 26 : 15Z
Finish Time : 2017 - 04 - 06T21 : 26 : 22Z
Task Id : 1565fbd3 - ea26 - 4e43 - 8551 - 40fb8e5b2850

–
Resources : My_Org - centos - centos - 6 - x86_64 - os ( repository )
State : Successful
Start Time : 2017 - 04 - 06T21 : 26 : 22Z
Finish Time : 2017 - 04 - 06T21 : 26 : 22Z
Task Id : 75beb6a0 - 0b3f - 4b61 - 8eb9 - a88dc27168e3

$ TZ = UTC date
Thu Apr 6 21 : 31 : 49 UTC 2017

Thank you,
-Alan

On Tuesday, April 4, 2017 at 3:36:14 PM UTC-6, John Mitsch wrote:

Alan,
I don’t have much experience with Sync Plans, but I would expect they would create syncing tasks in Katello. You can look at your pulp tasks using pulp-admin, see if you see any activity corresponding to your sync plans there.

yum install pulp-admin-client pulp-rpm-admin-extensions.noarch pulp-rpm-handlers.noarch
pulpAdminPassword=$(grep ^default_password /etc/pulp/server.conf | cut -d’ ’ -f2)
pulp-admin -u admin -p $pulpAdminPassword tasks list

-John

John Mitsch
Red Hat Engineering
(860)-967-7285
irc: jomitsch

On Fri, Mar 31, 2017 at 4:41 PM, Alan Evans < [ javascript-blocked: | alanw...@gmail.com ] > wrote:

BQ_BEGIN

Hello,
I am using Katello 3.3/Foreman 1.14.2. I have a fresh install and I created new Sync plan, product and repos with hammer. At first I didn’t think the jobs were running at all, but I read a thread here that got me looking at things and I found that pulp is in fact syncing on schedule but the results aren’t appearing in the katello UI/Hammer CLI. I suspect there is some kind of post sync job that has to happen that isn’t. If I manually sync them from the UI then the UI is updated.

Thoughts?

-Alan

–
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 [ javascript-blocked: | foreman-user...@googlegroups.com ] .
To post to this group, send email to [ javascript-blocked: | forema...@googlegroups.com ] .
Visit this group at [ https://groups.google.com/group/foreman-users | https://groups.google.com/group/foreman-users ] .
For more options, visit [ https://groups.google.com/d/optout | https://groups.google.com/d/optout ] .

BQ_END

–
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 [ mailto:foreman-users+unsubscribe@googlegroups.com | foreman-users+unsubscribe@googlegroups.com ] .
To post to this group, send email to [ mailto:foreman-users@googlegroups.com | foreman-users@googlegroups.com ] .
Visit this group at [ https://groups.google.com/group/foreman-users | https://groups.google.com/group/foreman-users ] .
For more options, visit [ https://groups.google.com/d/optout | https://groups.google.com/d/optout ] .

Anthony_Chevalet · August 4, 2017, 10:58am

Hi Eric,

When syncing on schedule, there is no task in Foreman. I can see the tasks
only for manual sync.

In both cases (on schedule or manual) the post sync occurs but seems to
fail:

Aug 4 10:45:16 p-infra-katello pulp[1045]: celery.worker.strategy:INFO:
Received task:
pulp.server.async.tasks._queue_reserved_task[86c84b8d-f592-49e0-901e-855267ffb428]
Aug 4 10:45:16 p-infra-katello pulp[1198]: celery.worker.job:INFO: Task
pulp.server.managers.repo.sync.sync[244bbfe1-b12a-4a5a-b757-3693d1b1d953]
succeeded in 15.983295023s: <pulp.server.async.tasks.TaskResult object at
0xd71dd10>
Aug 4 10:45:16 p-infra-katello pulp[1198]: celery.worker.strategy:INFO:
Received task:
pulp.server.managers.repo.publish.publish[1a6279a3-925e-4c45-9fc8-5117e9aa0bf7]
Aug 4 10:45:16 p-infra-katello pulp[1198]: celery.worker.strategy:INFO:
Received task:
pulp.server.async.tasks._release_resource[9df9a54e-b18c-4b31-9696-d9990481cc1f]
Aug 4 10:45:16 p-infra-katello celery[1198]: Exception in thread
Thread-184:
Aug 4 10:45:16 p-infra-katello celery[1198]: Traceback (most recent call
last):
Aug 4 10:45:16 p-infra-katello celery[1198]: File
"/usr/lib64/python2.7/threading.py", line 811, in __bootstrap_inner
Aug 4 10:45:16 p-infra-katello celery[1198]: self.run()
Aug 4 10:45:16 p-infra-katello celery[1198]: File
"/usr/lib64/python2.7/threading.py", line 764, in run
Aug 4 10:45:16 p-infra-katello celery[1198]: self.__target(*self.__args,
**self.__kwargs)
Aug 4 10:45:16 p-infra-katello celery[1198]: File
"/usr/lib/python2.7/site-packages/pulp/server/event/http.py", line 58, in
_send_post
Aug 4 10:45:16 p-infra-katello celery[1198]: response = post(url,
data=json_body, auth=auth, headers={'Content-Type': 'application/json'})
Aug 4 10:45:16 p-infra-katello celery[1198]: File
"/usr/lib/python2.7/site-packages/requests/api.py", line 112, in post
Aug 4 10:45:16 p-infra-katello celery[1198]: return request('post', url,
data=data, json=json, **kwargs)
Aug 4 10:45:16 p-infra-katello celery[1198]: File
"/usr/lib/python2.7/site-packages/requests/api.py", line 58, in request
Aug 4 10:45:16 p-infra-katello celery[1198]: return
session.request(method=method, url=url, **kwargs)
Aug 4 10:45:16 p-infra-katello celery[1198]: File
"/usr/lib/python2.7/site-packages/requests/sessions.py", line 502, in
request
Aug 4 10:45:16 p-infra-katello celery[1198]: resp = self.send(prep,
**send_kwargs)
Aug 4 10:45:16 p-infra-katello celery[1198]: File
"/usr/lib/python2.7/site-packages/requests/sessions.py", line 612, in send
Aug 4 10:45:16 p-infra-katello celery[1198]: r = adapter.send(request,
**kwargs)
Aug 4 10:45:16 p-infra-katello celery[1198]: File
"/usr/lib/python2.7/site-packages/requests/adapters.py", line 504, in send
Aug 4 10:45:16 p-infra-katello celery[1198]: raise ConnectionError(e,
request=request)
Aug 4 10:45:16 p-infra-katello celery[1198]: ConnectionError:
HTTPSConnectionPool(host='p-infra-katello.ks.net', port=443): Max retries
exceeded with url:
/katello/api/v2/repositories/sync_complete?token=Byitjkvw92TpyWBHS2cdmHvbwMneMktQ
(Caused by SSLError(SSLError(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.ks.net/katello/api/v2/repositories/sync_complete?token=Byitjkvw92TpyWBHS2cdmHvbwMneMktQ
Enter host password for user 'admin':
{"displayMessage":"undefined method []' for nil:NilClass","errors":["undefined method[]' for nil:NilClass"]}

···

2017-08-03 20:01 GMT+02:00 Eric D Helms :

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 most obvious thing to check is if you see tasks that result from this
and if you see API hits to Katello for the sync notification URL. You can
find this in /etc/foreman/plugins/katello.yaml.

We need to figure out if Pulp is hitting Katello and the errors like there
or if Pulp is not configured to http notify.

On Aug 3, 2017 9:13 AM, “Anthony Chevalet” anthony.chevalet@gmail.com > wrote:

Hello,

Any news on this? Bug report?
I have the same behavior for ages (katello 3.0?), and it’s still there
with foreman 1.15.2/Katello 3.4.3.

Thanks,
Anthony

Le vendredi 31 mars 2017 22:41:46 UTC+2, Alan Evans a écrit :

Hello,

I am using Katello 3.3/Foreman 1.14.2. I have a fresh install and I
created new Sync plan, product and repos with hammer. At first I didn’t
think the jobs were running at all, but I read a thread here that got me
looking at things and I found that pulp is in fact syncing on schedule but
the results aren’t appearing in the katello UI/Hammer CLI. I suspect there
is some kind of post sync job that has to happen that isn’t. If I manually
sync them from the UI then the UI is updated.

Thoughts?

-Alan

–
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 a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit https://groups.google.com/d/
topic/foreman-users/ZODFm2ektM0/unsubscribe.
To unsubscribe from this group and all its topics, 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.

Alan_Evans · April 6, 2017, 10:59pm

Yes,

Actually all of my components are created by script. I have been
extensively testing things out and playing w/
product/repo/content-view/activation-key setups to figure out what works
well.

echo "Create products…"
(
echo "sync-plan create --name "Daily" --interval daily --organization-id
$ORG_ID --sync-date "2017-01-01 02:00:00 UTC" --enabled true"
echo "product create --name "CentOS" --label "centos" --sync-plan Daily
–organization-id $ORG_ID"
echo "product create --name "EPEL" --label "epel" --sync-plan Daily
–organization-id $ORG_ID"
echo "product create --name "Puppet Labs" --label puppet-enterprise
–organization-id $ORG_ID"
echo "product create --name "Fedora Copr" --label copr --sync-plan Daily
–organization-id $ORG_ID"
echo "product create --name "Foreman" --label foreman --sync-plan Daily
–organization-id $ORG_ID"
echo "product create --name "Katello" --label katello --sync-plan Daily
–organization-id $ORG_ID"
echo exit
) | hammer shell

I have created a "New" sync plan via the UI and associated it with one of
my products.

$ hammer sync-plan list
—|-------|---------------------|----------|--------

ID	NAME	START DATE	INTERVAL	ENABLED
1	Daily	2017/01/01 20:26:00	daily	yes
2	New	2017/04/03 19:31:00	daily	yes
—	-------	---------------------	----------	--------

$ hammer product info --id 1
ID: 1
Name: CentOS
Label: centos
Description:
Sync State: Syncing Complete.
Sync Plan ID: 2
** OMITTED FOR BREVITY **

-Alan

···

On Thursday, April 6, 2017 at 4:23:52 PM UTC-6, Jason B. Nance wrote: > > Hi Alan, > > In the web UI have you created a sync plan (Content -> Sync Plans) and > associated that sync plan with each of your products? And if so, are the > results of those tasks successful (Monitor -> Tasks)? > > Regards, > > j > > > ------------------------------ > *From: *"Alan Evans" <alanw...@gmail.com > > *To: *"Foreman Users" <forema...@googlegroups.com > > *Sent: *Thursday, April 6, 2017 5:12:54 PM > *Subject: *Re: [foreman-users] [Katello] Pulp repos sync on schedule but > not showing in katello > > Thanks John. > I've been poking around at this for a couple of days. I have looked at > the tasks and was going to share but didn't want to overwhelm anyone that > tried to help. > > A plain 'tasks list' gives nothing. > > $ sudo pulp-admin tasks list > +----------------------------------------------------------------------+ > Tasks > +----------------------------------------------------------------------+ > > No tasks found > > > tasks list --all, gives a lot, so I'll pull out a few sections > > $ sudo pulp-admin tasks list -a | grep -A5 My_Org-centos-centos-6-x86_64- > os > -- > Resources: My_Org-centos-centos-6-x86_64-os (repository) > State: Successful > Start Time: 2017-04-05T19:31:00Z > Finish Time: 2017-04-05T19:31:07Z > Task Id: dd6e6dac-5988-4cc3-be6c-95b223936f98 > > -- > Resources: My_Org-centos-centos-6-x86_64-os (repository) > State: Successful > Start Time: 2017-04-05T19:31:07Z > Finish Time: 2017-04-05T19:31:07Z > Task Id: 2d9ec7cd-de30-44d7-a3b1-8a10e1aa7257 > > -- > Resources: My_Org-centos-centos-6-x86_64-os (repository) > State: Successful > Start Time: 2017-04-06T19:36:55Z > Finish Time: 2017-04-06T19:37:02Z > Task Id: d8cb7dac-b13c-4420-83a3-432f1c06c635 > > -- > Resources: My_Org-centos-centos-6-x86_64-os (repository) > State: Successful > Start Time: 2017-04-06T19:37:02Z > Finish Time: 2017-04-06T19:37:02Z > Task Id: 19543dbd-fe67-4442-b56e-c3b0d91d695a > > $ TZ=UTC date > Thu Apr 6 21:18:46 UTC 2017 > > You can see that for the repo centos-6-os repo, pulp has synced and > published the repo for the last couple of days. But you can see that > Katello seems to think the last sync was almost a week ago. > > $ hammer repository info --id 1 > ID: 1 > Name: CentOS 6 x86_64 OS > Label: centos-6-x86_64-os > Organization: My Org > Red Hat Repository: no > Content Type: yum > Checksum Type: sha256 > Mirror on Sync: yes > URL: http://mirror.centos.org/centos/6/os/x86_64/ > Publish Via HTTP: yes > Published At: http:// > katello.example.com/pulp/repos/My_Org/Library/custom/centos/centos-6-x86_64-os/ > Relative Path: My_Org/Library/custom/centos/centos-6-x86_64-os > Download Policy: on_demand > Product: > ID: 1 > Name: CentOS > GPG Key: > ID: 2 > Name: RPM-GPG-KEY-CentOS-6 > Sync: > Status: Success > Last Sync Date: 6 days > Created: 2017/03/31 00:26:52 > Updated: 2017/03/31 20:47:13 > Content Counts: > Packages: 6696 > Package Groups: 214 > Errata: 0 > > But get this, if I sync it from Katello it will update. > > $ hammer repository synchronize --id 1 > [.....................................................................] [ > 100%] > No new packages. > > $ hammer repository info --id 1 > ID: 1 > Name: CentOS 6 x86_64 OS > Label: centos-6-x86_64-os > Organization: My Org > Red Hat Repository: no > Content Type: yum > Checksum Type: sha256 > Mirror on Sync: yes > URL: http://mirror.centos.org/centos/6/os/x86_64/ > Publish Via HTTP: yes > Published At: http:// > katello.example.com/pulp/repos/My_Org/Library/custom/centos/centos-6-x86_64-os/ > Relative Path: My_Org/Library/custom/centos/centos-6-x86_64-os > Download Policy: on_demand > Product: > ID: 1 > Name: CentOS > GPG Key: > ID: 2 > Name: RPM-GPG-KEY-CentOS-6 > Sync: > Status: Success > Last Sync Date: 3 minutes > Created: 2017/03/31 00:26:52 > Updated: 2017/03/31 20:47:13 > Content Counts: > Packages: 6696 > Package Groups: 214 > Errata: 670 > > $ sudo pulp-admin tasks list -a | grep -A5 My_Org-centos-centos-6-x86_64- > os > -- > Resources: My_Org-centos-centos-6-x86_64-os (repository) > State: Successful > Start Time: 2017-04-06T21:26:15Z > Finish Time: 2017-04-06T21:26:22Z > Task Id: 1565fbd3-ea26-4e43-8551-40fb8e5b2850 > > -- > Resources: My_Org-centos-centos-6-x86_64-os (repository) > State: Successful > Start Time: 2017-04-06T21:26:22Z > Finish Time: 2017-04-06T21:26:22Z > Task Id: 75beb6a0-0b3f-4b61-8eb9-a88dc27168e3 > > $ TZ=UTC date > Thu Apr 6 21:31:49 UTC 2017 > > Thank you, > -Alan > > On Tuesday, April 4, 2017 at 3:36:14 PM UTC-6, John Mitsch wrote: >> >> Alan, >> I don't have much experience with Sync Plans, but I would expect they >> would create syncing tasks in Katello. You can look at your pulp tasks >> using pulp-admin, see if you see any activity corresponding to your sync >> plans there. >> >> yum install pulp-admin-client pulp-rpm-admin-extensions.noarch >> pulp-rpm-handlers.noarch >> pulpAdminPassword=$(grep ^default_password /etc/pulp/server.conf | cut >> -d' ' -f2) >> pulp-admin -u admin -p $pulpAdminPassword tasks list >> >> -John >> >> John Mitsch >> Red Hat Engineering >> (860)-967-7285 >> irc: jomitsch >> >> On Fri, Mar 31, 2017 at 4:41 PM, Alan Evans wrote: >> >>> Hello, >>> I am using Katello 3.3/Foreman 1.14.2. I have a fresh install and I >>> created new Sync plan, product and repos with hammer. At first I didn't >>> think the jobs were running at all, but I read a thread here that got me >>> looking at things and I found that pulp is in fact syncing on schedule but >>> the results aren't appearing in the katello UI/Hammer CLI. I suspect there >>> is some kind of post sync job that has to happen that isn't. If I manually >>> sync them from the UI then the UI is updated. >>> >>> Thoughts? >>> >>> -Alan >>> >>> >>> >>> >>> -- >>> 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...@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://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-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://groups.google.com/d/optout. >

Anthony_Chevalet · August 4, 2017, 1:11pm

ps: Initially it was working fine, I suspect it stopped working since I've
created a proxy content.

···

2017-08-04 12:58 GMT+02:00 Anthony Chevalet :

Hi Eric,

When syncing on schedule, there is no task in Foreman. I can see the tasks
only for manual sync.

In both cases (on schedule or manual) the post sync occurs but seems to
fail:

Aug 4 10:45:16 p-infra-katello pulp[1045]: celery.worker.strategy:INFO:
Received task: pulp.server.async.tasks._queue_reserved_task[86c84b8d-
f592-49e0-901e-855267ffb428]
Aug 4 10:45:16 p-infra-katello pulp[1198]: celery.worker.job:INFO: Task
pulp.server.managers.repo.sync.sync[244bbfe1-b12a-4a5a-b757-3693d1b1d953]
succeeded in 15.983295023s: <pulp.server.async.tasks.TaskResult object at
0xd71dd10>
Aug 4 10:45:16 p-infra-katello pulp[1198]: celery.worker.strategy:INFO:
Received task: pulp.server.managers.repo.publish.publish[1a6279a3-925e-
4c45-9fc8-5117e9aa0bf7]
Aug 4 10:45:16 p-infra-katello pulp[1198]: celery.worker.strategy:INFO:
Received task: pulp.server.async.tasks._release_resource[9df9a54e-
b18c-4b31-9696-d9990481cc1f]
Aug 4 10:45:16 p-infra-katello celery[1198]: Exception in thread
Thread-184:
Aug 4 10:45:16 p-infra-katello celery[1198]: Traceback (most recent call
last):
Aug 4 10:45:16 p-infra-katello celery[1198]: File “/usr/lib64/python2.7/threading.py”,
line 811, in __bootstrap_inner
Aug 4 10:45:16 p-infra-katello celery[1198]: self.run()
Aug 4 10:45:16 p-infra-katello celery[1198]: File “/usr/lib64/python2.7/threading.py”,
line 764, in run
Aug 4 10:45:16 p-infra-katello celery[1198]: self.__target(*self.__args,
**self.__kwargs)
Aug 4 10:45:16 p-infra-katello celery[1198]: File
"/usr/lib/python2.7/site-packages/pulp/server/event/http.py", line 58, in
_send_post
Aug 4 10:45:16 p-infra-katello celery[1198]: response = post(url,
data=json_body, auth=auth, headers={‘Content-Type’: ‘application/json’})
Aug 4 10:45:16 p-infra-katello celery[1198]: File
"/usr/lib/python2.7/site-packages/requests/api.py", line 112, in post
Aug 4 10:45:16 p-infra-katello celery[1198]: return request(‘post’, url,
data=data, json=json, **kwargs)
Aug 4 10:45:16 p-infra-katello celery[1198]: File
"/usr/lib/python2.7/site-packages/requests/api.py", line 58, in request
Aug 4 10:45:16 p-infra-katello celery[1198]: return
session.request(method=method, url=url, **kwargs)
Aug 4 10:45:16 p-infra-katello celery[1198]: File
"/usr/lib/python2.7/site-packages/requests/sessions.py", line 502, in
request
Aug 4 10:45:16 p-infra-katello celery[1198]: resp = self.send(prep,
**send_kwargs)
Aug 4 10:45:16 p-infra-katello celery[1198]: File
"/usr/lib/python2.7/site-packages/requests/sessions.py", line 612, in send
Aug 4 10:45:16 p-infra-katello celery[1198]: r = adapter.send(request,
**kwargs)
Aug 4 10:45:16 p-infra-katello celery[1198]: File
"/usr/lib/python2.7/site-packages/requests/adapters.py", line 504, in send
Aug 4 10:45:16 p-infra-katello celery[1198]: raise ConnectionError(e,
request=request)
Aug 4 10:45:16 p-infra-katello celery[1198]: ConnectionError:
HTTPSConnectionPool(host=‘p-infra-katello.ks.net’, port=443): Max retries
exceeded with url: /katello/api/v2/repositories/sync_complete?token=
Byitjkvw92TpyWBHS2cdmHvbwMneMktQ (Caused by SSLError(SSLError(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.ks.net/katello/api/v2/repositories/sync_complete?
token=Byitjkvw92TpyWBHS2cdmHvbwMneMktQ
Enter host password for user ‘admin’:
{“displayMessage”:“undefined method []' for nil:NilClass","errors":["undefined method[]’ for nil:NilClass”]}

2017-08-03 20:01 GMT+02:00 Eric D Helms eric.d.helms@gmail.com:

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 most obvious thing to check is if you see tasks that result from this
and if you see API hits to Katello for the sync notification URL. You can
find this in /etc/foreman/plugins/katello.yaml.

We need to figure out if Pulp is hitting Katello and the errors like
there or if Pulp is not configured to http notify.

On Aug 3, 2017 9:13 AM, “Anthony Chevalet” anthony.chevalet@gmail.com >> wrote:

Hello,

Any news on this? Bug report?
I have the same behavior for ages (katello 3.0?), and it’s still there
with foreman 1.15.2/Katello 3.4.3.

Thanks,
Anthony

Le vendredi 31 mars 2017 22:41:46 UTC+2, Alan Evans a écrit :

Hello,

I am using Katello 3.3/Foreman 1.14.2. I have a fresh install and I
created new Sync plan, product and repos with hammer. At first I didn’t
think the jobs were running at all, but I read a thread here that got me
looking at things and I found that pulp is in fact syncing on schedule but
the results aren’t appearing in the katello UI/Hammer CLI. I suspect there
is some kind of post sync job that has to happen that isn’t. If I manually
sync them from the UI then the UI is updated.

Thoughts?

-Alan

–
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 a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit https://groups.google.com/d/to
pic/foreman-users/ZODFm2ektM0/unsubscribe.
To unsubscribe from this group and all its topics, 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.

ehelms · August 4, 2017, 7:47pm

Couple of follow up questions to help us:

Are you using custom certificates?
What version of python-requests is on the box? Both from yum and pip's
perspective?

···

On Fri, Aug 4, 2017 at 9:11 AM, Anthony Chevalet wrote:

ps: Initially it was working fine, I suspect it stopped working since I’ve
created a proxy content.

2017-08-04 12:58 GMT+02:00 Anthony Chevalet anthony.chevalet@gmail.com:

Hi Eric,

When syncing on schedule, there is no task in Foreman. I can see the
tasks only for manual sync.

In both cases (on schedule or manual) the post sync occurs but seems to
fail:

Aug 4 10:45:16 p-infra-katello pulp[1045]: celery.worker.strategy:INFO:
Received task: pulp.server.async.tasks._queue
_reserved_task[86c84b8d-f592-49e0-901e-855267ffb428]
Aug 4 10:45:16 p-infra-katello pulp[1198]: celery.worker.job:INFO: Task
pulp.server.managers.repo.sync.sync[244bbfe1-b12a-4a5a-b757-3693d1b1d953]
succeeded in 15.983295023s: <pulp.server.async.tasks.TaskResult object
at 0xd71dd10>
Aug 4 10:45:16 p-infra-katello pulp[1198]: celery.worker.strategy:INFO:
Received task: pulp.server.managers.repo.publ
ish.publish[1a6279a3-925e-4c45-9fc8-5117e9aa0bf7]
Aug 4 10:45:16 p-infra-katello pulp[1198]: celery.worker.strategy:INFO:
Received task: pulp.server.async.tasks._release_resource[9df9a54e-b18c-
4b31-9696-d9990481cc1f]
Aug 4 10:45:16 p-infra-katello celery[1198]: Exception in thread
Thread-184:
Aug 4 10:45:16 p-infra-katello celery[1198]: Traceback (most recent call
last):
Aug 4 10:45:16 p-infra-katello celery[1198]: File
"/usr/lib64/python2.7/threading.py", line 811, in __bootstrap_inner
Aug 4 10:45:16 p-infra-katello celery[1198]: self.run()
Aug 4 10:45:16 p-infra-katello celery[1198]: File
"/usr/lib64/python2.7/threading.py", line 764, in run
Aug 4 10:45:16 p-infra-katello celery[1198]: self.__target(*self.__args,
**self.__kwargs)
Aug 4 10:45:16 p-infra-katello celery[1198]: File
"/usr/lib/python2.7/site-packages/pulp/server/event/http.py", line 58,
in _send_post
Aug 4 10:45:16 p-infra-katello celery[1198]: response = post(url,
data=json_body, auth=auth, headers={‘Content-Type’: ‘application/json’})
Aug 4 10:45:16 p-infra-katello celery[1198]: File
"/usr/lib/python2.7/site-packages/requests/api.py", line 112, in post
Aug 4 10:45:16 p-infra-katello celery[1198]: return request(‘post’, url,
data=data, json=json, **kwargs)
Aug 4 10:45:16 p-infra-katello celery[1198]: File
"/usr/lib/python2.7/site-packages/requests/api.py", line 58, in request
Aug 4 10:45:16 p-infra-katello celery[1198]: return
session.request(method=method, url=url, **kwargs)
Aug 4 10:45:16 p-infra-katello celery[1198]: File
"/usr/lib/python2.7/site-packages/requests/sessions.py", line 502, in
request
Aug 4 10:45:16 p-infra-katello celery[1198]: resp = self.send(prep,
**send_kwargs)
Aug 4 10:45:16 p-infra-katello celery[1198]: File
"/usr/lib/python2.7/site-packages/requests/sessions.py", line 612, in
send
Aug 4 10:45:16 p-infra-katello celery[1198]: r = adapter.send(request,
**kwargs)
Aug 4 10:45:16 p-infra-katello celery[1198]: File
"/usr/lib/python2.7/site-packages/requests/adapters.py", line 504, in
send
Aug 4 10:45:16 p-infra-katello celery[1198]: raise ConnectionError(e,
request=request)
Aug 4 10:45:16 p-infra-katello celery[1198]: ConnectionError:
HTTPSConnectionPool(host=‘p-infra-katello.ks.net’, port=443): Max
retries exceeded with url: /katello/api/v2/repositories/s
ync_complete?token=Byitjkvw92TpyWBHS2cdmHvbwMneMktQ (Caused by
SSLError(SSLError(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.ks.net/katello/api/v2/repositories/
sync_complete?token=Byitjkvw92TpyWBHS2cdmHvbwMneMktQ
Enter host password for user ‘admin’:
{“displayMessage”:“undefined method []' for nil:NilClass","errors":["undefined method[]’ for nil:NilClass”]}

2017-08-03 20:01 GMT+02:00 Eric D Helms eric.d.helms@gmail.com:

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 most obvious thing to check is if you see tasks that result from
this and if you see API hits to Katello for the sync notification URL. You
can find this in /etc/foreman/plugins/katello.yaml.

We need to figure out if Pulp is hitting Katello and the errors like
there or if Pulp is not configured to http notify.

On Aug 3, 2017 9:13 AM, “Anthony Chevalet” anthony.chevalet@gmail.com >>> wrote:

Hello,

Any news on this? Bug report?
I have the same behavior for ages (katello 3.0?), and it’s still there
with foreman 1.15.2/Katello 3.4.3.

Thanks,
Anthony

Le vendredi 31 mars 2017 22:41:46 UTC+2, Alan Evans a écrit :

Hello,

I am using Katello 3.3/Foreman 1.14.2. I have a fresh install and I
created new Sync plan, product and repos with hammer. At first I didn’t
think the jobs were running at all, but I read a thread here that got me
looking at things and I found that pulp is in fact syncing on schedule but
the results aren’t appearing in the katello UI/Hammer CLI. I suspect there
is some kind of post sync job that has to happen that isn’t. If I manually
sync them from the UI then the UI is updated.

Thoughts?

-Alan

–
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 a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit https://groups.google.com/d/to
pic/foreman-users/ZODFm2ektM0/unsubscribe.
To unsubscribe from this group and all its topics, 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.

–
Eric D. Helms
Red Hat Engineering

Anthony_Chevalet · August 6, 2017, 12:01pm

No, default certificates generated by foreman-installer
yum: python-requests-2.6.0-1.el7_1.noarch - pip: requests (2.18.2)

···

2017-08-04 21:47 GMT+02:00 Eric D Helms :

Couple of follow up questions to help us:

Are you using custom certificates?

What version of python-requests is on the box? Both from yum and pip’s
perspective?

On Fri, Aug 4, 2017 at 9:11 AM, Anthony Chevalet < > anthony.chevalet@gmail.com> wrote:

ps: Initially it was working fine, I suspect it stopped working since
I’ve created a proxy content.

2017-08-04 12:58 GMT+02:00 Anthony Chevalet anthony.chevalet@gmail.com:

Hi Eric,

When syncing on schedule, there is no task in Foreman. I can see the
tasks only for manual sync.

In both cases (on schedule or manual) the post sync occurs but seems to
fail:

Aug 4 10:45:16 p-infra-katello pulp[1045]: celery.worker.strategy:INFO:
Received task: pulp.server.async.tasks._queue
_reserved_task[86c84b8d-f592-49e0-901e-855267ffb428]
Aug 4 10:45:16 p-infra-katello pulp[1198]: celery.worker.job:INFO: Task
pulp.server.managers.repo.sync.sync[244bbfe1-b12a-4a5a-b757-3693d1b1d953]
succeeded in 15.983295023s: <pulp.server.async.tasks.TaskResult object
at 0xd71dd10>
Aug 4 10:45:16 p-infra-katello pulp[1198]: celery.worker.strategy:INFO:
Received task: pulp.server.managers.repo.publ
ish.publish[1a6279a3-925e-4c45-9fc8-5117e9aa0bf7]
Aug 4 10:45:16 p-infra-katello pulp[1198]: celery.worker.strategy:INFO:
Received task: pulp.server.async.tasks._relea
se_resource[9df9a54e-b18c-4b31-9696-d9990481cc1f]
Aug 4 10:45:16 p-infra-katello celery[1198]: Exception in thread
Thread-184:
Aug 4 10:45:16 p-infra-katello celery[1198]: Traceback (most recent
call last):
Aug 4 10:45:16 p-infra-katello celery[1198]: File
"/usr/lib64/python2.7/threading.py", line 811, in __bootstrap_inner
Aug 4 10:45:16 p-infra-katello celery[1198]: self.run()
Aug 4 10:45:16 p-infra-katello celery[1198]: File
"/usr/lib64/python2.7/threading.py", line 764, in run
Aug 4 10:45:16 p-infra-katello celery[1198]:
self.__target(*self.__args, **self.__kwargs)
Aug 4 10:45:16 p-infra-katello celery[1198]: File
"/usr/lib/python2.7/site-packages/pulp/server/event/http.py", line 58,
in _send_post
Aug 4 10:45:16 p-infra-katello celery[1198]: response = post(url,
data=json_body, auth=auth, headers={‘Content-Type’: ‘application/json’})
Aug 4 10:45:16 p-infra-katello celery[1198]: File
"/usr/lib/python2.7/site-packages/requests/api.py", line 112, in post
Aug 4 10:45:16 p-infra-katello celery[1198]: return request(‘post’,
url, data=data, json=json, **kwargs)
Aug 4 10:45:16 p-infra-katello celery[1198]: File
"/usr/lib/python2.7/site-packages/requests/api.py", line 58, in request
Aug 4 10:45:16 p-infra-katello celery[1198]: return
session.request(method=method, url=url, **kwargs)
Aug 4 10:45:16 p-infra-katello celery[1198]: File
"/usr/lib/python2.7/site-packages/requests/sessions.py", line 502, in
request
Aug 4 10:45:16 p-infra-katello celery[1198]: resp = self.send(prep,
**send_kwargs)
Aug 4 10:45:16 p-infra-katello celery[1198]: File
"/usr/lib/python2.7/site-packages/requests/sessions.py", line 612, in
send
Aug 4 10:45:16 p-infra-katello celery[1198]: r = adapter.send(request,
**kwargs)
Aug 4 10:45:16 p-infra-katello celery[1198]: File
"/usr/lib/python2.7/site-packages/requests/adapters.py", line 504, in
send
Aug 4 10:45:16 p-infra-katello celery[1198]: raise ConnectionError(e,
request=request)
Aug 4 10:45:16 p-infra-katello celery[1198]: ConnectionError:
HTTPSConnectionPool(host=‘p-infra-katello.ks.net’, port=443): Max
retries exceeded with url: /katello/api/v2/repositories/s
ync_complete?token=Byitjkvw92TpyWBHS2cdmHvbwMneMktQ (Caused by
SSLError(SSLError(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.ks.net/katello/api/v2/repositories/s
ync_complete?token=Byitjkvw92TpyWBHS2cdmHvbwMneMktQ
Enter host password for user ‘admin’:
{“displayMessage”:“undefined method []' for nil:NilClass","errors":["undefined method[]’ for nil:NilClass”]}

2017-08-03 20:01 GMT+02:00 Eric D Helms eric.d.helms@gmail.com:

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 most obvious thing to check is if you see tasks that result from
this and if you see API hits to Katello for the sync notification URL. You
can find this in /etc/foreman/plugins/katello.yaml.

We need to figure out if Pulp is hitting Katello and the errors like
there or if Pulp is not configured to http notify.

On Aug 3, 2017 9:13 AM, “Anthony Chevalet” anthony.chevalet@gmail.com >>>> wrote:

Hello,

Any news on this? Bug report?
I have the same behavior for ages (katello 3.0?), and it’s still there
with foreman 1.15.2/Katello 3.4.3.

Thanks,
Anthony

Le vendredi 31 mars 2017 22:41:46 UTC+2, Alan Evans a écrit :

Hello,

I am using Katello 3.3/Foreman 1.14.2. I have a fresh install and I
created new Sync plan, product and repos with hammer. At first I didn’t
think the jobs were running at all, but I read a thread here that got me
looking at things and I found that pulp is in fact syncing on schedule but
the results aren’t appearing in the katello UI/Hammer CLI. I suspect there
is some kind of post sync job that has to happen that isn’t. If I manually
sync them from the UI then the UI is updated.

Thoughts?

-Alan

–
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 a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit https://groups.google.com/d/to
pic/foreman-users/ZODFm2ektM0/unsubscribe.
To unsubscribe from this group and all its topics, 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.

–
Eric D. Helms
Red Hat Engineering

–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit https://groups.google.com/d/
topic/foreman-users/ZODFm2ektM0/unsubscribe.
To unsubscribe from this group and all its topics, 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.

Anthony_Chevalet · August 16, 2017, 9:17pm

Hi, should I open a bug for this one? Thanks

···

2017-08-06 14:01 GMT+02:00 Anthony Chevalet :

No, default certificates generated by foreman-installer

yum: python-requests-2.6.0-1.el7_1.noarch - pip: requests (2.18.2)

2017-08-04 21:47 GMT+02:00 Eric D Helms ericdhelms@gmail.com:

Couple of follow up questions to help us:

Are you using custom certificates?

What version of python-requests is on the box? Both from yum and
pip’s perspective?

On Fri, Aug 4, 2017 at 9:11 AM, Anthony Chevalet < >> anthony.chevalet@gmail.com> wrote:

ps: Initially it was working fine, I suspect it stopped working since
I’ve created a proxy content.

2017-08-04 12:58 GMT+02:00 Anthony Chevalet anthony.chevalet@gmail.com
:

Hi Eric,

When syncing on schedule, there is no task in Foreman. I can see the
tasks only for manual sync.

In both cases (on schedule or manual) the post sync occurs but seems to
fail:

Aug 4 10:45:16 p-infra-katello pulp[1045]:
celery.worker.strategy:INFO: Received task: pulp.server.async.tasks._queue
_reserved_task[86c84b8d-f592-49e0-901e-855267ffb428]
Aug 4 10:45:16 p-infra-katello pulp[1198]: celery.worker.job:INFO:
Task pulp.server.managers.repo.sync.sync[244bbfe1-b12a-4a5a-b757-3693d1b1d953]
succeeded in 15.983295023s: <pulp.server.async.tasks.TaskResult object
at 0xd71dd10>
Aug 4 10:45:16 p-infra-katello pulp[1198]:
celery.worker.strategy:INFO: Received task: pulp.server.managers.repo.publ
ish.publish[1a6279a3-925e-4c45-9fc8-5117e9aa0bf7]
Aug 4 10:45:16 p-infra-katello pulp[1198]:
celery.worker.strategy:INFO: Received task: pulp.server.async.tasks._relea
se_resource[9df9a54e-b18c-4b31-9696-d9990481cc1f]
Aug 4 10:45:16 p-infra-katello celery[1198]: Exception in thread
Thread-184:
Aug 4 10:45:16 p-infra-katello celery[1198]: Traceback (most recent
call last):
Aug 4 10:45:16 p-infra-katello celery[1198]: File
"/usr/lib64/python2.7/threading.py", line 811, in __bootstrap_inner
Aug 4 10:45:16 p-infra-katello celery[1198]: self.run()
Aug 4 10:45:16 p-infra-katello celery[1198]: File
"/usr/lib64/python2.7/threading.py", line 764, in run
Aug 4 10:45:16 p-infra-katello celery[1198]:
self.__target(*self.__args, **self.__kwargs)
Aug 4 10:45:16 p-infra-katello celery[1198]: File
"/usr/lib/python2.7/site-packages/pulp/server/event/http.py", line 58,
in _send_post
Aug 4 10:45:16 p-infra-katello celery[1198]: response = post(url,
data=json_body, auth=auth, headers={‘Content-Type’: ‘application/json’})
Aug 4 10:45:16 p-infra-katello celery[1198]: File
"/usr/lib/python2.7/site-packages/requests/api.py", line 112, in post
Aug 4 10:45:16 p-infra-katello celery[1198]: return request(‘post’,
url, data=data, json=json, **kwargs)
Aug 4 10:45:16 p-infra-katello celery[1198]: File
"/usr/lib/python2.7/site-packages/requests/api.py", line 58, in request
Aug 4 10:45:16 p-infra-katello celery[1198]: return
session.request(method=method, url=url, **kwargs)
Aug 4 10:45:16 p-infra-katello celery[1198]: File
"/usr/lib/python2.7/site-packages/requests/sessions.py", line 502, in
request
Aug 4 10:45:16 p-infra-katello celery[1198]: resp = self.send(prep,
**send_kwargs)
Aug 4 10:45:16 p-infra-katello celery[1198]: File
"/usr/lib/python2.7/site-packages/requests/sessions.py", line 612, in
send
Aug 4 10:45:16 p-infra-katello celery[1198]: r = adapter.send(request,
**kwargs)
Aug 4 10:45:16 p-infra-katello celery[1198]: File
"/usr/lib/python2.7/site-packages/requests/adapters.py", line 504, in
send
Aug 4 10:45:16 p-infra-katello celery[1198]: raise ConnectionError(e,
request=request)
Aug 4 10:45:16 p-infra-katello celery[1198]: ConnectionError:
HTTPSConnectionPool(host=‘p-infra-katello.ks.net’, port=443): Max
retries exceeded with url: /katello/api/v2/repositories/s
ync_complete?token=Byitjkvw92TpyWBHS2cdmHvbwMneMktQ (Caused by
SSLError(SSLError(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.ks.net/katello/api/v2/repositories/s
ync_complete?token=Byitjkvw92TpyWBHS2cdmHvbwMneMktQ
Enter host password for user ‘admin’:
{“displayMessage”:“undefined method []' for nil:NilClass","errors":["undefined method[]’ for nil:NilClass”]}

2017-08-03 20:01 GMT+02:00 Eric D Helms eric.d.helms@gmail.com:

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 most obvious thing to check is if you see tasks that result from
this and if you see API hits to Katello for the sync notification URL. You
can find this in /etc/foreman/plugins/katello.yaml.

We need to figure out if Pulp is hitting Katello and the errors like
there or if Pulp is not configured to http notify.

On Aug 3, 2017 9:13 AM, “Anthony Chevalet” anthony.chevalet@gmail.com >>>>> wrote:

Hello,

Any news on this? Bug report?
I have the same behavior for ages (katello 3.0?), and it’s still
there with foreman 1.15.2/Katello 3.4.3.

Thanks,
Anthony

Le vendredi 31 mars 2017 22:41:46 UTC+2, Alan Evans a écrit :

Hello,

I am using Katello 3.3/Foreman 1.14.2. I have a fresh install and I
created new Sync plan, product and repos with hammer. At first I didn’t
think the jobs were running at all, but I read a thread here that got me
looking at things and I found that pulp is in fact syncing on schedule but
the results aren’t appearing in the katello UI/Hammer CLI. I suspect there
is some kind of post sync job that has to happen that isn’t. If I manually
sync them from the UI then the UI is updated.

Thoughts?

-Alan

–
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 a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit https://groups.google.com/d/to
pic/foreman-users/ZODFm2ektM0/unsubscribe.
To unsubscribe from this group and all its topics, 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.

–
Eric D. Helms
Red Hat Engineering

–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit https://groups.google.com/d/to
pic/foreman-users/ZODFm2ektM0/unsubscribe.
To unsubscribe from this group and all its topics, 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.