Bug #29548
closed
Pulp 3 migration warning for file and docker even if they are disabled
Added by Ian Ballou over 4 years ago.
Updated almost 4 years ago.
Description
When the ::Katello::Pulp3::Migration service initializes, it checks if Katello is already using Pulp 3 for file or docker. However, that calculation doesn't take in account for the file or docker types being disabled. We need to check if file or docker exist anywhere in the smart proxy's supported_pulp_types.
Related issues
1 (1 open — 0 closed)
The user in the forums who saw this bug reported that he did indeed have file and docker enabled but still saw the bug. He said he had upgraded from Katello 3.14 to 3.15 RC2. This is surprising, so it should also be investigated.
- Target version set to Katello 3.16.1
- Triaged changed from No to Yes
For what it's worth with our Katello 3.15 installation we get this too. We've never used docker or file content types, but attempting the migration throws an error, which now shows as a permanently running/error task:
Actions::Pulp3::ContentMigration
Input:
{"services_checked"=>["pulp3"],
"smart_proxy_id"=>1,
"remote_user"=>"admin",
"remote_cp_user"=>"admin",
"current_request_id"=>nil,
"current_timezone"=>"UTC",
"current_user_id"=>1,
"current_organization_id"=>nil,
"current_location_id"=>nil}
Output:
{}
Exception:
Katello::Errors::Pulp3MigrationError: Pulp 3 migration cannot run. Types file, docker have already been migrated.
- Target version changed from Katello 3.16.1 to Katello 3.16.2
- Target version changed from Katello 3.16.2 to 1341
- Target version changed from 1341 to Katello 3.17.2
- Status changed from New to Rejected
- Target version changed from Katello 3.17.2 to Katello Recycle Bin
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by