Loading...

XML

Word

Printable

Type: Bug
Resolution: Not a Bug
Priority: Minor
Fix Version/s: None
Affects Version/s: 4.18
Component/s: Machine Config Operator
Labels:
None

Activity Type:
Quality / Stability / Reliability
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Story Points:
2
Severity:
Low
Regression:
None

Target Backport Versions:
None
Target Version:
None
Release Blocker:
None
Sprint:
MCO Sprint 265
sprint_count:
1

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

Release Note Status:
None
Release Note Type:
None
Release Note Text:
None

Escape Reason:
None
Escape Impact:
None
Corrective Measures:
None
SDLC stage when should've been found:
None

Description of problem:

    When extensions are applied, and then they are manually removed from the nodes no action is taken by MCO. There is no message to the user, no alert, no degradation and the extensions are not re-installed.

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

    4.18

How reproducible:

    Always

Steps to Reproduce:

    1. Install extensions
    2. Manually remove a installed extension rpm from a node

$ rpm-ostree reset
$ reboot

    3. Wait for the node to be rebooted

Actual results:

    The extensions have been removed from a node and this node is not configured as expected. Nevertheless, no action is taken.

Expected results:

    The admin should be informed that a node is not correctly configured, or the extensions should be re-installed.

Additional info:

is related to

MCO-1954 Investigate what improvements can be made to the config drift monitor

To Do

Assignee:: Isabella Janssen

Reporter:: Sergio Regidor de la Rosa

Need Info From:: None

Contributors:: None

QA Contact:: Sergio Regidor de la Rosa

Doc Contact:: None

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2024/10/31 4:58 PM

Updated:: 2025/10/29 8:10 PM

Resolved:: 2025/01/23 3:37 PM