Bug 1385767 - Remove the standard pulp unit storage path migration
Summary: Remove the standard pulp unit storage path migration
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Sanket Jagtap
URL:
Whiteboard:
Depends On: 1381702
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-17 16:15 UTC by Bryan Kearney
Modified: 2021-04-06 17:55 UTC (History)
19 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1381702
Environment:
Last Closed: 2018-02-21 16:54:17 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Pulp Redmine 2323 0 High CLOSED - WONTFIX Support skipping the standard storage path migration. 2016-10-28 14:31:10 UTC

Comment 1 pulp-infra@redhat.com 2016-10-28 14:31:11 UTC
The Pulp upstream bug status is at CLOSED - WONTFIX. Updating the external tracker on this bug.

Comment 2 pulp-infra@redhat.com 2016-10-28 14:31:15 UTC
The Pulp upstream bug priority is at High. Updating the external tracker on this bug.

Comment 3 Michael Hrivnak 2016-12-13 22:32:17 UTC
Brad, do you know what the purpose of this BZ is? Is it just to make sure the cherrypick happens again for 6.3? If so, can we move this to POST maybe, since there's no Pulp work to be done upstream? Or move it to a different component?

Comment 4 Michael Hrivnak 2016-12-19 20:15:31 UTC
Moving to Content Management component since the next steps on this are not for the Pulp team.

Comment 6 Sanket Jagtap 2017-12-13 08:55:52 UTC
This box is being upgraded from 6.2.z to 6.3.0 snap28
I still see the related migrations steps and no note saying skipping migration

Is this done differently for 6.3 upgrade? 

[sat] out: Beginning database migrations.
[sat] out: Applying pulp.server.db.migrations version 300
[sat] out: Migration to pulp.server.db.migrations version 300 complete.
[sat] out: Applying pulp.server.db.migrations version 301
[sat] out: Migration to pulp.server.db.migrations version 301 complete.
[sat] out: Applying pulp.server.db.migrations version 302
[sat] out: Migration to pulp.server.db.migrations version 302 complete.
[sat] out: Applying pulp.server.db.migrations version 303
[sat] out: Migration to pulp.server.db.migrations version 303 complete.
[sat] out: Applying pulp_docker.plugins.migrations version 300
[sat] out: Migration to pulp_docker.plugins.migrations version 300 complete.
[sat] out: Migration package pulp_puppet.plugins.migrations is up to date at version 5
[sat] out: Applying pulp_rpm.plugins.migrations version 300
[sat] out: Migration to pulp_rpm.plugins.migrations version 300 complete.
[sat] out: Applying pulp_rpm.plugins.migrations version 301
[sat] out: Migration to pulp_rpm.plugins.migrations version 301 complete.
[sat] out: Applying pulp_rpm.plugins.migrations version 302
[sat] out: Migration to pulp_rpm.plugins.migrations version 302 complete.
[sat] out: Applying pulp_rpm.plugins.migrations version 303
[sat] out: Migration to pulp_rpm.plugins.migrations version 303 complete.
[sat] out: Applying pulp_rpm.plugins.migrations version 304
[sat] out: Migration to pulp_rpm.plugins.migrations version 304 complete.
[sat] out: Applying pulp_rpm.plugins.migrations version 305
[sat] out: Migration to pulp_rpm.plugins.migrations version 305 complete.
[sat] out: Loading unit model: docker_blob = pulp_docker.plugins.models:Blob

Comment 8 Jeff Ortel 2018-01-12 21:27:57 UTC
Patrick, can you investigate whether the patch has been applied to 6.3?

Comment 12 Sanket Jagtap 2018-02-01 15:24:44 UTC
Build: Satellite 6.3.0 snap

Comment 13 Sanket Jagtap 2018-02-01 15:27:23 UTC
Build: Satellite 6.3.0 snap 33

I was able to test this by, emptying the mongodb and then running the upgrade.

LOG:

Upgrade Step: migrate_pulp...
grep -qe '7.[[:digit:]]' /etc/redhat-release finished successfully!
sed -i -e 's?/var/run/mongodb/mongodb.pid?/var/run/mongodb/mongod.pid?g' /etc/mongod.conf finished successfully!
26573
pgrep mongod finished successfully!
Attempting to connect to localhost:27017
Attempting to connect to localhost:27017
Write concern for Mongo connection: {}
Loading content types.
Loading type descriptors []
Parsing type descriptors
Validating type descriptor syntactic integrity
Validating type descriptor semantic integrity
Loading unit model: erratum = pulp_rpm.plugins.db.models:Errata
Loading unit model: distribution = pulp_rpm.plugins.db.models:Distribution
Loading unit model: srpm = pulp_rpm.plugins.db.models:SRPM
Loading unit model: package_group = pulp_rpm.plugins.db.models:PackageGroup
Loading unit model: package_category = pulp_rpm.plugins.db.models:PackageCategory
Loading unit model: iso = pulp_rpm.plugins.db.models:ISO
Loading unit model: package_environment = pulp_rpm.plugins.db.models:PackageEnvironment
Loading unit model: drpm = pulp_rpm.plugins.db.models:DRPM
Loading unit model: package_langpacks = pulp_rpm.plugins.db.models:PackageLangpacks
Loading unit model: rpm = pulp_rpm.plugins.db.models:RPM
Loading unit model: yum_repo_metadata_file = pulp_rpm.plugins.db.models:YumMetadataFile
Loading unit model: docker_blob = pulp_docker.plugins.models:Blob
Loading unit model: docker_manifest = pulp_docker.plugins.models:Manifest
Loading unit model: docker_image = pulp_docker.plugins.models:Image
Loading unit model: docker_tag = pulp_docker.plugins.models:Tag
Loading unit model: puppet_module = pulp_puppet.plugins.db.models:Module
Loading unit model: ostree = pulp_ostree.plugins.db.model:Branch
Loading auxiliary model: erratum_pkglists = pulp_rpm.plugins.db.models:ErratumPkglist
Updating the database with types []
Updating the database with types [puppet_module, docker_tag, ostree, package_langpacks, erratum, docker_blob, docker_manifest, yum_repo_metadata_file, package_group, package_category, iso, package_environment, drpm, distribution, rpm, srpm, docker_image]
Content types loaded.
Ensuring the admin role and user are in place.
ensure admin
Admin role and user are in place.
Beginning database migrations.
Migration package pulp.server.db.migrations fast-forwarded to version 303
Applying pulp_docker.plugins.migrations version 1
Migration to pulp_docker.plugins.migrations version 1 complete.
Applying pulp_docker.plugins.migrations version 2
****************************************************************************************
* NOTE: This migration may take a long time depending on the size of your Pulp content *
****************************************************************************************
Standard storage path migration skipped.
Migration to pulp_docker.plugins.migrations version 2 complete.
Applying pulp_docker.plugins.migrations version 300
Migration to pulp_docker.plugins.migrations version 300 complete.
Applying pulp_puppet.plugins.migrations version 1
Migrated puppet modules to include checksum
Migration to pulp_puppet.plugins.migrations version 1 complete.
Applying pulp_puppet.plugins.migrations version 2
Migration to pulp_puppet.plugins.migrations version 2 complete.
Applying pulp_puppet.plugins.migrations version 3
Migration to pulp_puppet.plugins.migrations version 3 complete.
Applying pulp_puppet.plugins.migrations version 4
****************************************************************************************
* NOTE: This migration may take a long time depending on the size of your Pulp content *
****************************************************************************************
Standard storage path migration skipped.
Migration to pulp_puppet.plugins.migrations version 4 complete.
Applying pulp_puppet.plugins.migrations version 5
***Note. You may want to re-publish the list of repos found in /var/lib/pulp/0005_puppet_module_name_change.txt.
   This migration fixed an issue with modules installation related to wrong puppet_module name.
Migration to pulp_puppet.plugins.migrations version 5 complete.
Migration package pulp_rpm.plugins.migrations fast-forwarded to version 305

Comment 14 Satellite Program 2018-02-21 16:54: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/RHSA-2018:0336


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