Bug 2099566 - Cloudinit should be replaced by cloud-init in all places
Summary: Cloudinit should be replaced by cloud-init in all places
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: User Experience
Version: 4.11.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.12.0
Assignee: Ugo Palatucci
QA Contact: Guohua Ouyang
URL:
Whiteboard:
Depends On:
Blocks: 2101485
TreeView+ depends on / blocked
 
Reported: 2022-06-21 09:07 UTC by Guohua Ouyang
Modified: 2022-09-14 19:36 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2101485 (view as bug list)
Environment:
Last Closed: 2022-09-14 19:36:10 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
cloudinit (144.94 KB, image/png)
2022-06-21 09:07 UTC, Guohua Ouyang
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github kubevirt-ui kubevirt-plugin pull 654 0 None open Bug 2099566: Cloudinit -> Cloud-init 2022-06-21 13:00:34 UTC
Github kubevirt-ui kubevirt-plugin pull 667 0 None open Bug 2099566: Cloud-init -> cloud-init text fix 2022-06-23 13:00:54 UTC
Red Hat Product Errata RHSA-2022:6526 0 None None None 2022-09-14 19:36:18 UTC

Description Guohua Ouyang 2022-06-21 09:07:29 UTC
Created attachment 1891534 [details]
cloudinit

Description of problem:
We can see the word "Cloudinit"/"cloudinit" on the UI, while checking the community doc: https://cloudinit.readthedocs.io/en/latest/index.html
They only use cloud-init/Cloud-init, I think we should use cloud-init/Cloud-init in all places as well.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Guohua Ouyang 2022-06-23 01:10:38 UTC
it should be "cloud-init" if the word does not start the sentence, now it looks like:

"You can use Cloud-init for post installation configuration of the guest operating system.
The guest OS needs to have the Cloud-init service running."

Comment 2 Ugo Palatucci 2022-06-23 13:11:15 UTC
@gouyang do you want to backport the last pr to 4.11? https://github.com/kubevirt-ui/kubevirt-plugin/pull/667

Comment 3 Ugo Palatucci 2022-06-23 13:11:46 UTC
@gouyang do you want to backport the last pr to 4.11? https://github.com/kubevirt-ui/kubevirt-plugin/pull/667

Comment 4 Leon Kladnitsky 2022-06-26 08:11:13 UTC
Verified on v4.11.0-66

Comment 6 Guohua Ouyang 2022-06-26 23:13:25 UTC
(In reply to Ugo Palatucci from comment #3)
> @gouyang do you want to backport the last pr to 4.11?
> https://github.com/kubevirt-ui/kubevirt-plugin/pull/667

@Kobi, what's the policy of backporting kubevert-ui PR to 4.11? If there is no constraints, then I want to backport this fix to 4.11.

Comment 7 Guohua Ouyang 2022-06-26 23:15:01 UTC
(In reply to Leon Kladnitsky from comment #4)
> Verified on v4.11.0-66

@Leon, could you add the steps about how you verified the bug? Did you read through the bug before you verify it?

Comment 8 Leon Kladnitsky 2022-06-27 06:15:48 UTC
Verified by mistake, moving back to ON_QA

Comment 9 Ugo Palatucci 2022-06-27 13:36:03 UTC
@gouyang We are backporting it! https://github.com/kubevirt-ui/kubevirt-plugin/pull/675

Comment 10 Yaacov Zamir 2022-06-27 15:18:37 UTC
merged upstream, moving to ON_QA
https://github.com/kubevirt-ui/kubevirt-plugin/pull/654

backport BZ: https://bugzilla.redhat.com/show_bug.cgi?id=2101485

Comment 11 Guohua Ouyang 2022-07-27 04:02:20 UTC
verified on v4.12.0-88

Comment 13 errata-xmlrpc 2022-09-14 19:36:10 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 (Important: OpenShift Virtualization 4.11.0 Images security and bug fix update), 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/RHSA-2022:6526


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