Project

General

Profile

Actions
Copy link

Bug #5369

closed

Xen domU errors if xenstore tools aren't installed

Added by Florian Heigl over 10 years ago. Updated almost 3 years ago.

Status:
Rejected
Priority:
3
Assignee:
-
Category:
System integration
Target version:
6.1.19
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Infrequent - complex configurations | third party integrations
Effort required:
Small
Priority:
56
Name check:
Fix check:
Regression:

Description

this needs triage, it is probably a pure upstream cfengine issue? but i'm not sure :)

2014-08-07T23:58:45+0000 error: /default/addInformationsToInventory/vars: Proposed executable file '/bin/xenstore-read' doesn't exist
2014-08-07T23:58:45+0000 error: /default/addInformationsToInventory/vars: execresult '/bin/xenstore-read vm' is assumed to be executable but isn't
2014-08-07T23:58:45+0000 error: /default/addInformationsToInventory/vars/'VMRUDDERUUID'[0]: Proposed executable file '/bin/xenstore-read' doesn't exist
2014-08-07T23:58:45+0000 error: /default/addInformationsToInventory/vars/'VMRUDDERUUID'[0]: execresult '/bin/xenstore-read vm' is assumed to be executable but isn't
2014-08-07T23:58:45+0000 error: /default/addInformationsToInventory/vars/'VMRUDDERUUID'[0]: Proposed executable file '/bin/xenstore-read' doesn't exist
2014-08-07T23:58:45+0000 error: /default/addInformationsToInventory/vars/'VMRUDDERUUID'[0]: execresult '/bin/xenstore-read vm' is assumed to be executable but isn't
rlist.c:80: Programming Error: Rlist value contains type f instead of expected scalar

I think there is a tiny programming error as in the error message from rlist.c
most distros lack proper xen integration and will not install the xen tools on a xen domU.

Related issues 1 (0 open — 1 closed)

Related to Rudder - Bug #11798: Inventory error on xen VMRejectedActions
Actions
Copy link
 #1

Updated by Matthieu CERDA over 10 years ago

  • Description updated (diff)
  • Status changed from New to Discussion
  • Assignee set to Matthieu CERDA
  • Priority changed from N/A to 3
  • Target version set to 2.10.4

Hello Florian,

Normally, the xen-tools should be installed automatically if relevant, as seen in this inventory/1.0/fusionAgent.st bit:

  vars:
    SuSE.xen_dom0::
      "xen_tools_package" string => "xen-tools";
    SuSE.xen_domu_pv::
      "xen_tools_package" string => "xen-tools-domU";
(...)
  packages:
    xen::
      "${xen_tools_package}" 
        package_policy => "add",
        package_method => generic,
        classes        => cf2_if_else("xen_installed", "cant_install_xen"),
        comment        => "Installing xen package for extended data";

So, on SLES if a Xen DomU is detected, CFEngine would try to install xen-tools-domU using Zypper. Do you see any reason why this would fail on your host ? No usable package source maybe ?

About the programming error, I'm afraid we'll have to use the debug output of CFEngine ... but first, can you tell me if the cf-agent runs anyway or fails short (would be easier to diagnose if it just stops there) ?

Thanks in advance :)

Actions
Copy link
 #2

Updated by Florian Heigl over 10 years ago

1. I'll add a link to the SUSEStudio builds I'm testing with
2. Installation failed because missing sources, correct
3. As for the agent being OK - I'm not sure. I can answer that once I've dug in deeper. Right now I don't remember enough of cf*...
This is what I see as running:
rudders1:~ # ps -ef | grep cf
root 12373 12337 0 17:07 pts/0 00:00:00 grep cf
root 22113 1 0 05:01 ? 00:00:03 /var/rudder/cfengine-community/bin/cf-execd
What log would you need to tell more? /var/log/messages-ish?

4. Should I open a cfengine bug for it? I take it this really isn't rudder related?

Actions
Copy link
 #3

Updated by Nicolas PERRON over 10 years ago

  • Target version changed from 2.10.4 to 2.10.5
Actions
Copy link
 #4

Updated by Jonathan CLARKE over 10 years ago

This is Rudder-related. These are Rudder-specific promises. No need to open a CFEngine bug for this.

We should handle the case where the xen* tools are not available, to avoid trying to run them naively. This would be an easy fix.

Actions
Copy link
 #5

Updated by Vincent MEMBRÉ over 10 years ago

  • Target version changed from 2.10.5 to 2.10.6
Actions
Copy link
 #6

Updated by Florian Heigl over 10 years ago

The strange message (rlist.c:80: Programming Error: Rlist value contains type f instead of expected scalar)
seems to be gone in 2.11.2-2.

Actions
Copy link
 #7

Updated by Florian Heigl over 10 years ago

Just got info that the message is in fact still shown.
Also, this apparently causes a pretty long boot delay.

Actions
Copy link
 #8

Updated by Florian Heigl over 10 years ago

Ok this might be different issues.

  1. the rlist.c error - still occurs and should be reproducible simply by installing agent on sles and start of agent
  2. long timeout if policy server is set, but node is not accepted yet
  3. nagging issues if xenstore-ls / xenstore-read aren't installed

I'd love to see 1) disappear since this is embarrassing if people see the boot messages.

Actions
Copy link
 #9

Updated by Matthieu CERDA about 10 years ago

  • Target version changed from 2.10.6 to 2.10.7
Actions
Copy link
 #10

Updated by Vincent MEMBRÉ about 10 years ago

  • Target version changed from 2.10.7 to 2.10.8
Actions
Copy link
 #11

Updated by Vincent MEMBRÉ about 10 years ago

  • Target version changed from 2.10.8 to 2.10.9
Actions
Copy link
 #12

Updated by Vincent MEMBRÉ almost 10 years ago

  • Target version changed from 2.10.9 to 2.10.10
Actions
Copy link
 #13

Updated by Vincent MEMBRÉ almost 10 years ago

  • Target version changed from 2.10.10 to 2.10.11
Actions
Copy link
 #14

Updated by Vincent MEMBRÉ almost 10 years ago

  • Target version changed from 2.10.11 to 2.10.12
Actions
Copy link
 #15

Updated by Vincent MEMBRÉ almost 10 years ago

  • Target version changed from 2.10.12 to 2.10.13
Actions
Copy link
 #16

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.10.13 to 2.10.14
Actions
Copy link
 #17

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.10.14 to 2.10.15
Actions
Copy link
 #18

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.10.15 to 2.10.16
Actions
Copy link
 #19

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.10.16 to 2.10.17
Actions
Copy link
 #20

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 2.10.17 to 2.10.18
Actions
Copy link
 #21

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 2.10.18 to 2.10.19
Actions
Copy link
 #22

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 2.10.19 to 2.10.20
Actions
Copy link
 #23

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 2.10.20 to 277
Actions
Copy link
 #24

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 277 to 2.11.18
Actions
Copy link
 #25

Updated by Vincent MEMBRÉ almost 9 years ago

  • Target version changed from 2.11.18 to 2.11.19
Actions
Copy link
 #26

Updated by Vincent MEMBRÉ almost 9 years ago

  • Target version changed from 2.11.19 to 2.11.20
Actions
Copy link
 #27

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.20 to 2.11.21
Actions
Copy link
 #28

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.21 to 2.11.22
Actions
Copy link
 #29

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.22 to 2.11.23
Actions
Copy link
 #30

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.23 to 2.11.24
Actions
Copy link
 #31

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.24 to 308
Actions
Copy link
 #32

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 308 to 3.1.14
Actions
Copy link
 #33

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.14 to 3.1.15
Actions
Copy link
 #34

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.15 to 3.1.16
Actions
Copy link
 #35

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.16 to 3.1.17
Actions
Copy link
 #36

Updated by Benoît PECCATTE about 8 years ago

  • Assignee deleted (Matthieu CERDA)
Actions
Copy link
 #37

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.17 to 3.1.18
Actions
Copy link
 #38

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 3.1.18 to 3.1.19
Actions
Copy link
 #39

Updated by François ARMAND over 7 years ago

  • Severity set to Major - prevents use of part of Rudder | no simple workaround
  • User visibility set to Infrequent - complex configurations | third party integrations
  • Priority set to 0
Actions
Copy link
 #40

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.19 to 3.1.20
Actions
Copy link
 #41

Updated by Jonathan CLARKE over 7 years ago

  • Status changed from Discussion to New
Actions
Copy link
 #42

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.20 to 3.1.21
Actions
Copy link
 #43

Updated by François ARMAND over 7 years ago

  • Priority changed from 0 to 21
Actions
Copy link
 #44

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.21 to 3.1.22
Actions
Copy link
 #45

Updated by Benoît PECCATTE over 7 years ago

  • Priority changed from 21 to 34
Actions
Copy link
 #46

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.22 to 3.1.23
Actions
Copy link
 #47

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.23 to 3.1.24
Actions
Copy link
 #48

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 3.1.24 to 3.1.25
  • Priority changed from 34 to 35
Actions
Copy link
 #49

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 3.1.25 to 387
Actions
Copy link
 #50

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 387 to 4.1.10
Actions
Copy link
 #51

Updated by Nicolas CHARLES about 7 years ago

  • Related to Bug #11798: Inventory error on xen VM added
Actions
Copy link
 #52

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 4.1.10 to 4.1.11
  • Priority changed from 35 to 36
Actions
Copy link
 #53

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.1.11 to 4.1.12
  • Priority changed from 36 to 37
Actions
Copy link
 #54

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.1.12 to 4.1.13
Actions
Copy link
 #55

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.1.13 to 4.1.14
Actions
Copy link
 #56

Updated by Benoît PECCATTE over 6 years ago

  • Target version changed from 4.1.14 to 4.1.15
  • Priority changed from 37 to 38
Actions
Copy link
 #57

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 4.1.15 to 4.1.16
Actions
Copy link
 #58

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 4.1.16 to 4.1.17
Actions
Copy link
 #59

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 4.1.17 to 4.1.18
  • Priority changed from 38 to 39
Actions
Copy link
 #60

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 4.1.18 to 4.1.19
Actions
Copy link
 #61

Updated by Alexis Mousset almost 6 years ago

  • Target version changed from 4.1.19 to 4.1.20
Actions
Copy link
 #62

Updated by Alexis Mousset over 5 years ago

  • Target version changed from 4.1.20 to 588
  • Priority changed from 39 to 41
Actions
Copy link
 #63

Updated by Alexis Mousset over 5 years ago

  • Target version changed from 588 to 5.0.13
Actions
Copy link
 #64

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 5.0.13 to 5.0.14
Actions
Copy link
 #65

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 5.0.14 to 5.0.15
Actions
Copy link
 #66

Updated by Benoît PECCATTE about 5 years ago

  • Effort required set to Small
  • Priority changed from 41 to 56
Actions
Copy link
 #67

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 5.0.15 to 5.0.16
Actions
Copy link
 #68

Updated by Alexis Mousset almost 5 years ago

  • Target version changed from 5.0.16 to 5.0.17
Actions
Copy link
 #69

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.17 to 5.0.18
Actions
Copy link
 #70

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.18 to 5.0.19
Actions
Copy link
 #71

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.19 to 5.0.20
Actions
Copy link
 #72

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 5.0.20 to 797
Actions
Copy link
 #73

Updated by Benoît PECCATTE over 3 years ago

  • Target version changed from 797 to 6.1.14
Actions
Copy link
 #74

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.1.14 to 6.1.15
Actions
Copy link
 #75

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.1.15 to 6.1.16
Actions
Copy link
 #76

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.1.16 to 6.1.17
Actions
Copy link
 #77

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 6.1.17 to 6.1.18
Actions
Copy link
 #78

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 6.1.18 to 6.1.19
Actions
Copy link
 #79

Updated by François ARMAND almost 3 years ago

  • Status changed from New to Rejected

I'm closing that one, since - as far as we know - we don't had new occurence of that problem. So maybe nobody has that config case anymore, or it was corrected upstream.

Actions
Copy link

Also available in: Atom PDF