RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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 1330716 - preupg-content-creator traceback: no preup_creator.ui_helper
Summary: preupg-content-creator traceback: no preup_creator.ui_helper
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: preupgrade-assistant
Version: 6.8
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Petr Hracek
QA Contact: Tereza Cerna
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-26 19:01 UTC by Alois Mahdal
Modified: 2016-05-11 08:27 UTC (History)
7 users (show)

Fixed In Version: preupgrade-assistant-2.1.6-4.el6
Doc Type: No Doc Update
Doc Text:
I don't thing, this needs to be documented. We introduce preupg-content-creator in this release and we moved some code which causes this traceback.
Clone Of:
Environment:
Last Closed: 2016-05-11 08:27:08 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1022 0 normal SHIPPED_LIVE preupgrade-assistant bug fix and enhancement update 2016-05-11 12:23:56 UTC

Description Alois Mahdal 2016-04-26 19:01:30 UTC
Description of problem
======================

preupg-content-creator fails with traceback


Version-Release number of selected component
============================================

preupgrade-assistant-2.1.6-2.el6


How reproducible
================

Always


Steps to Reproduce
==================

    $ preupg-content-creator


Actual results
==============

    Traceback (most recent call last):
      File "/usr/bin/preupg-content-creator", line 8, in <module>
        from preup.creator.application import Application
      File "/usr/lib/python2.6/site-packages/preup/creator/application.py", line 7, in <module>
        from preup_creator.ui_helper import UIHelper
    ImportError: No module named preup_creator.ui_helper


Expected results
================

Something sane, e.g. usage hint

Comment 1 Alois Mahdal 2016-04-26 19:06:57 UTC
We need content creator to create custom modules for testing (test suite bug 1289977); testing against real contents is unscalable at least.

Comment 4 Petr Hracek 2016-04-27 12:50:03 UTC
This is fixed by upstream commit https://github.com/phracek/preupgrade-assistant/commit/b4ae55488c7de2650fcdec1ea16f28c020b4c280

Comment 7 errata-xmlrpc 2016-05-11 08:27:08 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://rhn.redhat.com/errata/RHBA-2016-1022.html


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