Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
oVirt would like to be able to boot the cloud image as-is and use cloud-init to set up the vm. Instead of using a metadata service, oVirt uses an attached config disk; however, the current cloud-init version won't discover attached config disks on systems with 2.6 kernels. (blkid needs some prodding to scan /dev/srX)
Note that this is dependent upon a pending cloud-init fix at:
https://code.launchpad.net/~gpadgett/cloud-init/dev-sr-fix
Version-Release number of selected component (if applicable):
rhel-server-x86_64-kvm-6.4_20130130.0-4.qcow2
How reproducible:
Always
Steps to Reproduce:
1. Boot image using ovirt with attached cloud-init config cd
2.
3.
Actual results:
Config disk not discovered
Expected results:
Disk found, processed by cloud-init
Additional info:
(In reply to Mike Burns from comment #2)
> Is this needed in 6.4.z as well? or just 6.5?
I believe (unless we backport this change to the 0.7.1 cloud-init package, which I'd rather not do) this should be addressed as part of bug #968246 which aims to update to a 0.7.2 based package for EL 6.5.
I believe the boto version change (which changes the interfaces to AWS v4 signature format by default) discussed under #968246 and #968247 will prevent us from doing a 6.4.z release of this change?
If this is only going into a cloud-init that is available starting in 6.5, then it's TestOnly from guest-images perspective.
If it's going to get backported or handled somehow in 6.4.z, then please let me know.
(In reply to Mike Burns from comment #2)
> Is this needed in 6.4.z as well? or just 6.5?
6.5 is good enough, but how soon can we get an image to work with as we need to integrate and test with it in the coming month or so?
(In reply to Itamar Heim from comment #5)
> (In reply to Mike Burns from comment #2)
> > Is this needed in 6.4.z as well? or just 6.5?
>
> 6.5 is good enough, but how soon can we get an image to work with as we need
> to integrate and test with it in the coming month or so?
That depends on getting the new cloud-init packaged and built. I've set that bug to be required by pre-dev-freeze and set the Layered Products to RHEV and OpenStack.
Hello,
I only did the same as in any previous compose which is to use build from rhui-2-ec2-rhel-6-candidate.
This was initial configuration for appliance images and I just kept using that.
$ brew latest-pkg RHEL-6.5-RC-1-set cloud-init --quiet
cloud-init-0.7.1-2.el6 RHEL-6.5-RC-1-set apevec
$ brew latest-pkg rhui-2-ec2-rhel-6-candidate cloud-init --quiet
cloud-init-0.7.1-2.el6 rhui-2-ec2-rhel-6-candidate apevec
If you want to use some separate tag for yourself then I have nothing against it. But then you'll have to guarantee me that it gets into standardized tag that I'm using for the compose.
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.
http://rhn.redhat.com/errata/RHBA-2013-1735.html