Project

Profile

Help

Issue #2032

closed

pulp sets reboot_suggested to True for all errata when syncing from published repo

Added by cduryee almost 8 years ago. Updated about 5 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
High
Assignee:
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
2.8.6
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Easy Fix, Pulp 2
Sprint:
Sprint 4
Quarter:

Description

If you have a Pulp server that syncs down a repo, then another Pulp server that syncs from the first Pulp, the second server will have "reboot_suggested = True" for all of its errata.

To repro:

  • sync RHEL 7
  • publish
  • on another pulp server server, sync RHEL 7 from the first Pulp's publish location

result: all errata on second server will have "reboot_suggested = True"

add'l info: It looks like not all errata (from non-Pulp sources) have "reboot_suggested" set, and it is only set at all if it's True. However, Pulp treats this as a boolean, so it becomes False upon the first sync/publish. The tricky part is that Pulp's importer then treats the existance of this flag as meaning True, even if it's false. The following snippet from the yum code illustrates:

            elif child.tag == 'reboot_suggested':
                self._md['reboot_suggested'] = True

Pulp follows this same convention, but it means if you sync/publish from one Pulp to another, everything ends up being marked as reboot suggested.


Related issues

Related to Packaging - Task #2083: Issues common to 2.9.1 and 2.8 streamCLOSED - NOTABUGsemyers

Actions

Also available in: Atom PDF