Project

General

Profile

Actions

Bug #12258

closed

Agent 4.3.0.rc1 misses xen_tools_package and suffering follows

Added by Janos Mattyasovszky over 6 years ago. Updated over 6 years ago.

Status:
Rejected
Priority:
N/A
Category:
System techniques
Target version:
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Priority:
94
Name check:
Fix check:
Regression:

Description

M| State         Technique                 Component                 Key                Message
E| compliant     Common                    ncf Initialization                           Configuration library initialization was correct
E| compliant     Common                    Security parameters                          The internal environment security is acceptable
E| compliant     Common                    Red Button                                   Red Button is not in effect, continuing as normal...
E| n/a           Common                    Process checking                             Rudder agent proccesses check is done by the rudder-agent cron job
E| compliant     Common                    CRON Daemon                                  Cron daemon status was correct
E| error         Inventory                 inventory                                    Could not install Xen utils on Xen system
E| error         Inventory                 inventory                                    Generated inventory has been detected as invalid
E| compliant     Common                    Binaries update                              The agent binaries in /var/rudder/cfengine-community/bin are up to date

All from vanilla 4.1.0.rc1 agent on sles12sp2 being accepted on a same-versioned root server (no relays).

The system is a PV Guest.

# xen-detect
Running in PV context on Xen V4.7.

Here are some relevant lines from running it in verbose mode

 verbose: Unable to detect environment from cf-monitord
 verbose: This appears to be a SUSE system.
 verbose: Looking for SUSE enterprise info in 'SUSE Linux Enterprise Server 12 (x86_64)'
 verbose: Discovered SUSE version SuSE_12
 verbose: This appears to be a xen hv system.
...
rudder  verbose: C: discovered hard class xen
rudder  verbose: C: discovered hard class xen_domu_hv
...

But in the bundle agent fusionAgent you don't handle this case:

    SuSE.xen_dom0::
      "xen_tools_package" string => "xen-tools";
    SuSE.xen_domu_pv::
      "xen_tools_package" string => "xen-tools-domU";
    debian::
      "xen_tools_package" string => "xenstore-utils";
    !debian.!SuSE::
      "xen_tools_package" string => "xen";

Please add xen_domu_hv to that line with "SuSE.xen_domu_pv"

Actions #1

Updated by François ARMAND over 6 years ago

  • Translation missing: en.field_tag_list set to Blocking 4.3

I'm marking it blocking 4.3 until we know if it's something that should be corrected elsewhere too.

Actions #2

Updated by François ARMAND over 6 years ago

  • Assignee set to Nicolas CHARLES
  • Target version set to 4.3.0~rc2
Actions #3

Updated by Nicolas CHARLES over 6 years ago

  • Status changed from New to Rejected

We don't use this code anymore - all related xen code as been purged right after 4.3 rc1 (as well as tools) in #8922

Actions #4

Updated by François ARMAND over 6 years ago

@Janos Matya: could you confirm that 4.3-rc2 or latter works as expected in Xen-based plateform?

Actions

Also available in: Atom PDF