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.

Description of problem:
When specifying repositories to enable, but none to disable, a 'NoneType' python exception is thrown causing cloud-init to fail.

I've submitted this PR upstream as a fix:
https://github.com/cloud-init/cloud-init/pull/9

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


How reproducible:
Always


Steps to Reproduce:
1. Create a cloud-init user-data with the following rh_subscription module options

  rh_subscription:
    username: <username>
    password: <password>
    add-pool: [ <pool-id> ]
    enable-repo: [ 'rhel-7-server-extras-rpms' ]

2. Attempt to create a machine using cloud-init.

Actual results:
A 'NoneType' python exception is thrown when attempting to iterate on the disable-repo array (called "drepos" in the code), since the disable-repo option wasn't specified in the cloud-init user-data.

Expected results:
disable-repo is ignored and cloud-init rh_subscription module runs successfully.

Additional info:
A workaround is to add an empty array for the disable-repos options.

Upstream for cloud-init is at https://launchpad.net/cloud-init

I'm not sure if anybody is monitoring the github mirror. You'll probably want to open an issue and submit the patch there.

Thanks Ryan! I've submitted the PR to launchpad:

https://code.launchpad.net/~dmulford/cloud-init/+git/cloud-init/+merge/332030

Thanks. I will keep an eye on it and pull it in here once it is accepted.

I had to resubmit the upstream PR as requested by Scott Moser.

Here is the new URL:
https://code.launchpad.net/~dmulford/cloud-init/+git/cloud-init/+merge/333293

Thanks for the heads-up. I will keep an eye on that.

Hi Ryan,
I have added a comment on the PR.

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/RHEA-2018:0806