CNV-37480: "auto updates for RHEL VirtualMachines" is enabled by default but does not work #1741
Conversation
…ult but does not work Signed-off-by: Aviv Turgeman <aturgema@redhat.com>
|
@avivtur: This pull request references CNV-37480 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.16.0" version, but no target version was set. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: avivtur, metalice The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/cherry-pick release-4.15 |
|
@avivtur: new pull request created: #1743 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
📝 Description
On a fresh cluster, the switch to allow RHEL auto updates was on by default, even if the key and id are missing, that caused the mechanism to not get the default unless you toggle it off and back on.
Allowing to set the switch on just if both id and key values are not empty after applying them is solving the issue
🎥 Demo
Before:
no-auto-update-rhel-vms.mp4
After:
no-auto-update-rhel-vms-after.mp4