Project

General

Profile

Bug #31288

Manifest refresh not happening

Added by Ranjit Chettiyar over 1 year ago. Updated over 1 year ago.

Status:
Rejected
Priority:
High
Assignee:
-
Category:
-
Target version:
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Hi All,

Manifest refresh is not happening. Tried to import the manifest manually but it didn't work. Please help.

Getting below error:

There was an issue with the backend service pulp: Not all necessary pulp workers running at https://host.example.com/pulp/api/v2.
There was an issue with the backend service pulp: Not all necessary pulp workers running at https://host.example.com.com/pulp/api/v2.

History

#1 Updated by Evgeni Golov over 1 year ago

  • Project changed from Foreman to Katello

#2 Updated by John Mitsch over 1 year ago

Hi Ranjit,

What version of Katello is this?

Can you try 'foreman-maintain service restart' and also provide the output of `curl https://host.example.com/pulp/api/v2/status/`? Thanks!

#3 Updated by John Mitsch over 1 year ago

  • Status changed from New to Need more information

#4 Updated by Ranjit Chettiyar over 1 year ago

I just did a few tests and got below result

hammer ping output

candlepin:
Status: ok
Server Response: Duration: 26ms
candlepin_auth:
Status: ok
Server Response: Duration: 26ms
pulp:
Status: FAIL
Server Response:
pulp_auth:
Status: FAIL
foreman_tasks:
Status: ok
Server Response: Duration: 7ms

Below I saw in About page under Administer
pulp FAIL Timed out reading data from server
pulp_auth FAIL Skipped pulp_auth check after failed pulp check

#5 Updated by Justin Sherrill over 1 year ago

  • Target version set to Katello Recycle Bin
  • Status changed from Need more information to Rejected

Hello!

This issue seems to be more of a support issue than a bug or defect. For more timely responses, please open up a forum post on our support forum: https://community.theforeman.org/c/support/10

I'm going to go ahead and close this now, but if it turns out this is a real bug, we can reopen this issue.

Thanks

Also available in: Atom PDF