Bug 1372847 - Content sync problem, timeout, then unable to redeploy
Summary: Content sync problem, timeout, then unable to redeploy
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Quickstart Cloud Installer
Classification: Red Hat
Component: Installation - Satellite
Version: 1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: John Matthews
QA Contact: Sudhir Mallamprabhakara
Dan Macpherson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-02 22:07 UTC by Thom Carlin
Modified: 2016-09-05 18:08 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-05 18:08:22 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1372850 0 unspecified CLOSED Redeploy leads to "Product ID \"69\" has already been registered with this activation key" 2021-02-22 00:41:40 UTC

Internal Links: 1372850

Description Thom Carlin 2016-09-02 22:07:40 UTC
Description of problem:

Encountered a content sync problem while I was away.  When I came back after 2 hours, I clicked Redeploy on the Content Sync 

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

QCI-1.0-RHEL-7-20160901.5

How reproducible:

100% when these 2 things occur

Steps to Reproduce:
1. Install/configure QCI [RPM install in this case]
2. Deploy RHV
3. When Content Sync error occurs, wait about 2 hours
4. On Content Sync page, try to Redeploy

Actual results:

Nothing on screen - just blinks for a moment

Expected results:

Attempted redeployment

Additional info:

Workaround:
* Navigate to another part of Satellite: Hosts > All Hosts in my case
* Quickstart Cloud Installer > Deployments
* Select deployment
* Redeploy

Content sync error was:
An error occurred during the sync 
{"expected_size"=>1205972, "error_code"=>"size_mismatch", "actual_size"=>1024780, "unit_key"=>{"epoch"=>"0", "version"=>"3.10.0", 
"name"=>"perf", "release"=>"123.1.2.el7", "checksum"=>"7752be3e7d286718f69a831f7f2d4a60a66e4de4", "arch"=>"x86_64", "checksumtype"=>"sha1"}}

Problem seems to be in /var/log/foreman/production.log:
2016-09-02 17:58:09 [app] [I] Processing by Fusor::Api::V21::DeploymentsController#redeploy as JSON
2016-09-02 17:58:09 [app] [I]   Parameters: {"api_version"=>"v21", "id"=>"1", "deployment"=>{}}
2016-09-02 17:58:09 [app] [W] Can't verify CSRF token authenticity
2016-09-02 17:58:09 [app] [W] SSO failed
2016-09-02 17:58:09 [app] [I]   Rendered api/v2/errors/unauthorized.json.rabl within api/v2/layouts/error_layout (1.8ms)
2016-09-02 17:58:09 [app] [I] Completed 401 Unauthorized in 4ms (ActiveRecord: 0.3ms)

So navigating gets the new CSRF token?

Comment 1 Thom Carlin 2016-09-05 18:08:22 UTC
No reproducer yet in production so closing for now.  Please reopen if this reoccurs.


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