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 800442 - Add capability to run user scripts from userdata in RHEL AMIs
Summary: Add capability to run user scripts from userdata in RHEL AMIs
Keywords:
Status: CLOSED DUPLICATE of bug 838659
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: cloud-init
Version: 6.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Joe Vlcek
QA Contact: mkovacik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-06 13:49 UTC by Chris Morgan
Modified: 2012-10-25 13:29 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-10-25 13:29:57 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Chris Morgan 2012-03-06 13:49:07 UTC
Request from Amazon:

We have a request from a customer to have RHEL AMI output the ssh fingerprints
to the console on boot.  This allows our customers to verify that the host they
are ssh'ing to is the same host that is in their account in the console.  We
also recommend this to customers in the EC2 User Guide:
http://docs.amazonwebservices.com/AWSEC2/latest/UserGuide/AccessingInstancesLinux.html

The customer would have setup a script to output these himself but the RHEL
amis don't currently have a mechanism to run user scripts from the userdata.

---------------------

Would like to target this for any future regions (add it to all AMIs) and for
existing regions, only add it to new versions of RHEL.

Comment 3 Suzanne Logcher 2012-05-18 20:52:22 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 4 Jay Greguske 2012-05-21 17:52:23 UTC
Note that integration of the cloud-init package may solve this.

Comment 5 RHEL Program Management 2012-07-10 06:59:33 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 6 RHEL Program Management 2012-07-11 01:47:40 UTC
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.

Comment 9 Joe Vlcek 2012-10-25 13:29:57 UTC
Note that integration of the cloud-init package will solve this.

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


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