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:

required by 968246, will require an update to python-boto >= 2.6.0 for cloud-init update to 0.7.2, probably due to:

https://bugs.launchpad.net/cloud-init/+bug/1068801

Note there was a major change between 2.5.x and 2.6.x where boto now uses AWS v4 signatures by default (with no config option to revert to v2 signatures), which is fine for connections to AWS, but we need to ensure other boto users (e.g openstack APIs like nova ec2 API) won't be broken by this (openstack-heat has been updated to handle v4 signatures already upstream)

Does this mean that python-boto will be moving from EPEL to RHEL for 6.5?

(In reply to Orion Poplawski from comment #10)
> Does this mean that python-boto will be moving from EPEL to RHEL for 6.5?

python-boto is already in RHEL (rhel-x86_64-server-rh-common-6 channel)

Ah, okay - that's why it is still in EPEL6.

*** This bug has been marked as a duplicate of bug 999080 ***