Bug 1228141
| Summary: | [hosted-engine][text] generate cloud-init image in HE setup is not clear | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-hosted-engine-setup | Reporter: | Jiri Belka <jbelka> |
| Component: | General | Assignee: | Lev Veyde <lveyde> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Nikolai Sednev <nsednev> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | --- | CC: | bugs, gklein, lsurette, rbalakri, sbonazzo, srevivo, ykaul, ylavi |
| Target Milestone: | ovirt-3.6.5 | Keywords: | StringChange, Triaged |
| Target Release: | 1.3.5.0 | Flags: | nsednev:
needinfo-
rule-engine: ovirt-3.6.z+ ylavi: planning_ack+ sbonazzo: devel_ack+ mavital: testing_ack+ |
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-04-21 14:38:30 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Integration | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1321997 | ||
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release. In oVirt testing is done on single release by default. Therefore I'm removing the 4.0 flag. If you think this bug must be tested in 4.0 as well, please re-add the flag. Please note we might not have testing resources to handle the 4.0 clone. Used latest rhevm-appliance 20160323.1-1.el7ev and following components:
qemu-kvm-rhev-2.3.0-31.el7_2.10.x86_64
ovirt-vmconsole-1.0.0-1.el7ev.noarch
vdsm-4.17.25-0.el7ev.noarch
ovirt-hosted-engine-ha-1.3.5.2-1.el7ev.noarch
ovirt-hosted-engine-setup-1.3.5.0-1.el7ev.noarch
sanlock-3.2.4-2.el7_2.x86_64
libvirt-client-1.2.17-13.el7_2.4.x86_64
ovirt-vmconsole-host-1.0.0-1.el7ev.noarch
ovirt-host-deploy-1.4.1-1.el7ev.noarch
mom-0.5.2-1.el7ev.noarch
ovirt-setup-lib-1.0.1-1.el7ev.noarch
Linux alma03.qa.lab.tlv.redhat.com 3.10.0-327.13.1.el7.x86_64 #1 SMP Mon Feb 29 13:22:02 EST 2016 x86_64 x86_64 x86_64 GNU/Linux
Red Hat Enterprise Linux Server release 7.2 (Maipo)
I still see this sentence: - "Would you like to generate on-fly a cloud-init ISO image (of no-cloud type)". Please see it in context as appears bellow:
"[ INFO ] Detecting available oVirt engine appliances
The following appliance have been found on your system:
[1] - The RHEV-M Appliance image (OVA) - 20160323.1-1.el7ev
[2] - Directly select an OVA file
Please select an appliance (1, 2) [1]:
[ INFO ] Verifying its sha1sum
[ INFO ] Checking OVF archive content (could take a few minutes depending on archive size)
[ INFO ] Checking OVF XML content (could take a few minutes depending on archive size)
[WARNING] OVF does not contain a valid image description, using default.
Would you like to use cloud-init to customize the appliance on the first boot (Yes, No)[Yes]?
Would you like to generate on-fly a cloud-init ISO image (of no-cloud type)
or do you have an existing one (Generate, Existing)[Generate]? "
Can you confirm that ovirt-hosted-engine-setup-1.3.5.0-1.el7ev.noarch contains the fix?
After a short discussion with Lev, I've found that this bug is actually fixed, as previously customer was getting the: "Would you like to generate on-fly a cloud-init no-cloud ISO image"; so it was fixed to: "Would you like to generate on-fly a cloud-init ISO image (of no-cloud type)", which is totally fine and works as expected now. Available cloud-init types described here: http://cloudinit.readthedocs.org/en/latest/topics/datasources.html#no-cloud . |
Description of problem: for a person who doesn't know that 'no-cloud' is cloud-init term this sentence looks odd. ~~~ Would you like to generate on-fly a cloud-init no-cloud ISO image or do you have an existing one (Generate, Existing)[Generate]? ~~~ i suppose we could drop 'no-cloud', i suppose nobody would care how it is called (the method) in cloud-init and having there 'ISO image' describes what is "input" media for cloud-init configuration. Version-Release number of selected component (if applicable): ovirt-hosted-engine-setup-1.3.0-0.0.master.20150518075146.gitdd9741f.el7.noarch How reproducible: 100% Steps to Reproduce: 1. hosted-engine --deploy 2. use 'disk' as source (you need ovirt-engine-appliance)[1] 3. Actual results: 'no-cloud' is not well known term and cause "omg what's that..." Expected results: have sentence clear and simple enough for average person Additional info: [1] http://jenkins.ovirt.org/job/ovirt-appliance-engine_master_create-rpms-el7-noarch_merged/lastSuccessfulBuild/