Bug 1226187

Summary: cloud-init package missing pyserial
Product: Red Hat Enterprise Linux 7 Reporter: Renich Bon Ciric <renich>
Component: cloud-initAssignee: Lars Kellogg-Stedman <lars>
Status: CLOSED ERRATA QA Contact: Martin Kočí <mkoci>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.2CC: huzhao, jherrman, mkoci
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: cloud-init-0.7.6-3.el7 Doc Type: Bug Fix
Doc Text:
The cloud-init package did not have a dependency on the pyserial package, which is required to support the SmartOS cloud data source. This update adds the missing dependency.
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-04-04 15:25:40 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Renich Bon Ciric 2015-05-29 07:37:19 UTC
Please, refer to this bug report: http://bugs.centos.org/view.php?id=8150.

At CloudSigma, we need pyserial to be part of the default installation; or, at least, available in the qcow2 image provided in http://cloud.centos.org/centos/7/images/CentOS-7-x86_64-GenericCloud.qcow2

This is blocking us from providing cloud-init functionality to our customers.

Comment 2 Renich Bon Ciric 2015-06-03 11:21:53 UTC
ping...

Anything?

Comment 3 Lars Kellogg-Stedman 2015-06-05 19:55:16 UTC
This seems like a reasonable request, and it looks like pyserial is already backed in RHEL.

Comment 4 Renich Bon Ciric 2015-06-08 02:12:07 UTC
(In reply to Lars Kellogg-Stedman from comment #3)
> This seems like a reasonable request, and it looks like pyserial is already
> backed in RHEL.

Ah, thanks! I hope you can include it. This will enable CloudSigma to provide this image cloud-init enabled.

Thanks.

Comment 13 errata-xmlrpc 2017-04-04 15:25:40 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://access.redhat.com/errata/RHBA-2017:0871