Bug 1349862 - enabling an ostree repository causes error on manifest refresh actions
Summary: enabling an ostree repository causes error on manifest refresh actions
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-24 12:02 UTC by Tom McKay
Modified: 2019-04-01 20:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-24 18:25:01 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 15516 0 None None None 2016-06-24 12:02:36 UTC

Description Tom McKay 2016-06-24 12:02:34 UTC
Since the ostree repos are not available on the cdn yet, enabling them in the OSTree tab of the Red Hat Repositories page will (properly) show an error. However, some part of them has been partially created in pulp which causes error when user attempts to refresh manifest.

In glue/pulp/repo.rb the lazy_accessor :importers will error on manifest refresh.

The OSTree repo will show up as enabled in the UI but errors when trying to disable it.

My suggestion would be to make sure that the initial enable is fully rolled back on an error.

Comment 1 Tom McKay 2016-06-24 12:02:42 UTC
Created from redmine issue http://projects.theforeman.org/issues/15516

Comment 3 Partha Aji 2016-06-24 18:21:50 UTC
I consider this a development environment issue and not a sat production issue, because Satellite customers will not get into this state. Basically without the --katello-enable-ostree=true customers will not be able to see OSTree repos that can be enabled.
Its not the case in the dev environment and hence Tom hit that. Going to remove the flags out and mark it a non blocker. This should be addressed upstream only.


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