Why engine-cleanup is removing all the configuration files when it's asked to remove a single component

Solution Verified - Updated -

Issue

  • engine-cleanup was executed to remove only WebSocket proxy.
          Do you want to remove all components? (Yes, No) [Yes]: No
          Do you want to remove Core files? (Yes, No) [No]: 
          Do you want to remove PKI keys? (Yes, No) [No]: 
          Do you want to remove ovirt-provider-ovn configuration files? (Yes, No) [No]: 
          Do you want to remove Apache SSL configuration? (Yes, No) [No]: 
          Do you want to remove PKI configuration? (Yes, No) [No]: 
          Do you want to remove VMConsole Helper PKI keys? (Yes, No) [No]: 
          Do you want to remove Versionlock Plugin Configuration? (Yes, No) [No]: 
          Do you want to remove YUM version locking configuration? (Yes, No) [No]: 
          Do you want to remove DWH files? (Yes, No) [No]: 
          Do you want to remove VMConsole PKI Proxy keys? (Yes, No) [No]: 
          Do you want to remove the engine? (Yes, No) [No]: 
          Do you want to remove DWH DB content? All data will be lost (Yes, No) [No]: 
          Do you want to remove the Image I/O Proxy? (Yes, No) [No]: 
          Do you want to remove the WebSocket proxy? (Yes, No) [No]: Yes
  • Answer No was provided for the removal of core, PKI,OVN etc. However, these options were ignored by the engine-cleanup and it removed all the files listed in uninstall.conf.

Environment

  • Red Hat Virtualization 4.3.

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content