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 2124519 - Upgrade fails when no content is synced
Summary: Upgrade fails when no content is synced
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Satellite Maintain
Version: 6.11.2
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Evgeni Golov
QA Contact: Satellite QE Team
URL:
Whiteboard:
: 2121544 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-06 12:08 UTC by Radek Mynar
Modified: 2023-09-26 18:08 UTC (History)
11 users (show)

Fixed In Version: rubygem-foreman_maintain-1.1.5-1.el8sat
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-26 18:08:30 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 35506 0 Normal New Upgrade fails when no content is synced 2022-09-08 09:33:01 UTC
Red Hat Issue Tracker SAT-12795 0 None None None 2022-09-07 14:55:33 UTC

Description Radek Mynar 2022-09-06 12:08:18 UTC
Description of problem:
Upgrade tries to change ownership of /var/lib/pulp/media/artifact directory which does not exist until some content is synced. This causes the upgrade to fail.

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

How reproducible:
always

Steps to Reproduce:
1. Install Satellite 6.10
2. Don't sync any repositories
3. Attempt to upgrade to 6.11
 subscription-manager repos --enable rhel-7-server-satellite-maintenance-6.11-rpms
 satellite-maintain upgrade list-versions
 satellite-maintain upgrade check --target-version 6.11
 satellite-maintain upgrade run --target-version 6.11

Actual results:
Upgrade check reports no errors, but upgrade fails with following error:
 Fix Pulpcore artifact ownership to be pulp:pulp: 
 / # chown -hR pulp.pulp /var/lib/pulp/media/artifact                  [FAIL]    
 No such file or directory - /var/lib/pulp/media/artifact

Expected results:
Upgrade should be successful even if the directory does not exist. Maybe the step should be skipped or the directory created...

Additional info:
The upgrade step was introduced in bz2106501

Comment 1 Evgeni Golov 2022-09-08 09:33:00 UTC
Created redmine issue https://projects.theforeman.org/issues/35506 from this bug

Comment 2 Evgeni Golov 2022-09-08 09:47:15 UTC
Radek, can you try the patch in https://github.com/theforeman/foreman_maintain/pull/642?

Comment 3 Bryan Kearney 2022-09-08 12:04:56 UTC
Upstream bug assigned to egolov

Comment 4 Bryan Kearney 2022-09-08 12:04:58 UTC
Upstream bug assigned to egolov

Comment 5 Radek Mynar 2022-09-12 15:31:51 UTC
(In reply to Evgeni Golov from comment #2)
> Radek, can you try the patch in
> https://github.com/theforeman/foreman_maintain/pull/642?

Hi Evgeni,

I applied the patch and upgrade went successfully on a machine with no content synced.

Comment 6 juwatts 2022-09-13 15:20:36 UTC
*** Bug 2121544 has been marked as a duplicate of this bug. ***


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