Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1176157 - Repository syncs should initiate capsule sync asynchronously
Summary: Repository syncs should initiate capsule sync asynchronously
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Foreman Proxy
Version: 6.0.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Justin Sherrill
QA Contact: Katello QA List
URL: http://projects.theforeman.org/issues...
Whiteboard:
: 1173133 (view as bug list)
Depends On: 1192500
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-19 15:06 UTC by Justin Sherrill
Modified: 2019-06-13 08:10 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-20 18:32:17 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
required lock is already taken by other running task (41.56 KB, text/plain)
2015-02-12 14:35 UTC, Sachin Ghai
no flags Details
status of pending task from dynflow (35.42 KB, image/png)
2015-02-12 14:37 UTC, Sachin Ghai
no flags Details
pulp task error in production.log of sat6 (14.55 KB, text/plain)
2015-02-12 14:39 UTC, Sachin Ghai
no flags Details
synced supplementary repo, its start time says: 5 minutes ago (51.40 KB, image/png)
2015-02-12 15:03 UTC, Sachin Ghai
no flags Details
rotating spinner on enabling redhat repo with type error in firebug (72.61 KB, image/png)
2015-02-13 04:37 UTC, Sachin Ghai
no flags Details
I tried enabling repo multiple times..but each time I got rotating spinner and here is dynflow tasks status (68.35 KB, image/png)
2015-02-13 04:39 UTC, Sachin Ghai
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:0247 0 normal SHIPPED_LIVE Red Hat Satellite 6 server bug fix update 2015-02-20 23:30:44 UTC

Internal Links: 1195887

Description Justin Sherrill 2014-12-19 15:06:53 UTC
Description of problem:

Currently in the sync dynflow action, after the repo sync in pulp is finished, we initiate a node metadata generation and sync as part of the sync task.  this means that if the capsule is not running the sync task will hang until the capsule comes back online. 

It should behave just like the content view publish/promote and initiate it as a 2nd entire action which is not dependent on the first.


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.  Install a capsule and associate it with library
2.  Shut down the capsule 
3.  Attempt to sync a repo

Actual results:
Sync hangs around 69%


Expected results:
Sync completes successfully


Additional info:

Comment 3 Justin Sherrill 2014-12-19 16:08:40 UTC
Created redmine issue http://projects.theforeman.org/issues/8770 from this bug

Comment 4 Mike McCune 2014-12-19 16:41:56 UTC
*** Bug 1173133 has been marked as a duplicate of this bug. ***

Comment 5 Bryan Kearney 2014-12-19 23:05:01 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/8770 has been closed
-------------
Justin Sherrill
Applied in changeset commit:katello|82cd0a41d1374fedd00550debb5b05da671663ef.

Comment 6 Pavel Moravec 2015-01-06 11:26:24 UTC
Is there a workaround available? I.e. will cancellint the task and syncing the same repo again work? (or will that fail in either case)?

Comment 10 Bryan Kearney 2015-02-05 21:05:09 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/8770 has been closed
-------------
Justin Sherrill
Applied in changeset commit:katello|82cd0a41d1374fedd00550debb5b05da671663ef.

Comment 14 Sachin Ghai 2015-02-12 14:35:22 UTC
Created attachment 990952 [details]
required lock is already taken by other running task

Comment 15 Sachin Ghai 2015-02-12 14:37:22 UTC
Created attachment 990953 [details]
status of pending task from dynflow

Comment 16 Sachin Ghai 2015-02-12 14:39:42 UTC
Created attachment 990954 [details]
pulp task error in production.log of sat6

Comment 18 Sachin Ghai 2015-02-12 14:45:34 UTC
But keep on getting these errors : I think sat6 is polling for capsule node?

Polling failed, attempt no. 1, retrying in 8
Pulp task error.  Refer to task for more details. (StandardError)
/opt/rh/ruby193/root/usr/share/gems/gems/katello-1.5.0/app/lib/actions/pulp/consumer/abstract_sync_node_task.rb:26:in `block in external_task='
/opt/rh/ruby193/root/usr/share/gems/gems/katello-1.5.0/app/lib/actions/pulp/consumer/abstract_sync_node_task.rb:24:in `each'
/

Comment 19 Sachin Ghai 2015-02-12 15:01:27 UTC
OK, I enabled another RedHat repo (Red Hat Enterprise Linux 7 Server - Supplementary RPMs x86_64 7Server) and synced it. It was synced properly on sat6 server. I think the fix is working as expected. But would be great if Justin can review if steps take to stop capsule are correct. Thanks

Comment 20 Sachin Ghai 2015-02-12 15:03:55 UTC
Created attachment 990959 [details]
synced supplementary repo, its start time says: 5 minutes ago

Comment 21 Justin Sherrill 2015-02-12 15:47:20 UTC
Sachin,

Yes, those steps seem fine.  (Or you could have just shut down katello-agent on the capsule).  You still should see a 'sync capsule' task that is probably stuck and not moving.

Comment 22 Sachin Ghai 2015-02-13 04:31:39 UTC
Thanks Justin, So I stopped goferd on capsule and tried to enable and sync redhat repo,  but now  when I enable the repo from 'Redhat repositories', the spinner keeps on rotating. No error in production.log but firebug raises this error:

--
25
TypeError: data is undefined
	

...a(this,str_data);data.w=w!==undefined?w:elem.width(),data.h=h!==undefined?h:elem...

--

Comment 23 Sachin Ghai 2015-02-13 04:37:09 UTC
Created attachment 991213 [details]
rotating spinner on enabling redhat repo  with type error in firebug

Comment 24 Sachin Ghai 2015-02-13 04:39:37 UTC
Created attachment 991214 [details]
I tried enabling repo multiple times..but each time I got rotating spinner and here is dynflow tasks status

Comment 26 jaudet 2015-02-18 17:45:32 UTC
Verified against a RHEL 6.6 system running Satellite-6.0.8 compose 3. As the risk of being redundant, here's the test procedure I used:

1. Go to Content > Red Hat Subscriptions and upload a manifest file.
2. Go to Content > Red Hat Repositories and enable a repository.
3. Go to Content > Sync Status and sync the just-enabled repository.
4. If not already done, attach a capsule. Make the capsule inoperable. You can do this in several ways. You could shut down the capsule system, or you can log in to the capsule system and stop the goferd service.
5. Go to Content > Sync Status and sync a repository that has been synced at least once before.
6. Go to Monitor > Tasks and verify that the sync task completes. A second task for generating node metadata should be in the running/pending state.

Verifying this bug is slightly complicated by the presence of BZ 1192500. If an attached capsule is inoperable, you cannot then enable a new repository or sync an already-enabled repository for the first time. That's a separate issue.

Comment 28 errata-xmlrpc 2015-02-20 18:32:17 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2015:0247


Note You need to log in before you can comment on or make changes to this bug.