Project

General

Profile

Bug #5369

Xen domU errors if xenstore tools aren't installed

Added by Florian Heigl over 4 years ago. Updated 25 days ago.

Status:
New
Priority:
3
Assignee:
-
Category:
System integration
Target version:
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Infrequent - complex configurations | third party integrations
Effort required:
Priority:
39

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

Related to Rudder - Bug #11798: Inventory error on xen VMRejected

History

#1 Updated by Matthieu CERDA over 4 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 :)

#2 Updated by Florian Heigl over 4 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?

#3 Updated by Nicolas PERRON over 4 years ago

  • Target version changed from 2.10.4 to 2.10.5

#4 Updated by Jonathan CLARKE over 4 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.

#5 Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 2.10.5 to 2.10.6

#6 Updated by Florian Heigl over 4 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.

#7 Updated by Florian Heigl over 4 years ago

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

#8 Updated by Florian Heigl over 4 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.

#9 Updated by Matthieu CERDA about 4 years ago

  • Target version changed from 2.10.6 to 2.10.7

#10 Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 2.10.7 to 2.10.8

#11 Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 2.10.8 to 2.10.9

#12 Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 2.10.9 to 2.10.10

#13 Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 2.10.10 to 2.10.11

#14 Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 2.10.11 to 2.10.12

#15 Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 2.10.12 to 2.10.13

#16 Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 2.10.13 to 2.10.14

#17 Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 2.10.14 to 2.10.15

#18 Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 2.10.15 to 2.10.16

#19 Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 2.10.16 to 2.10.17

#20 Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 2.10.17 to 2.10.18

#21 Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 2.10.18 to 2.10.19

#22 Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 2.10.19 to 2.10.20

#23 Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 2.10.20 to 277

#24 Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 277 to 2.11.18

#25 Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 2.11.18 to 2.11.19

#26 Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 2.11.19 to 2.11.20

#27 Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 2.11.20 to 2.11.21

#28 Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 2.11.21 to 2.11.22

#29 Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 2.11.22 to 2.11.23

#30 Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 2.11.23 to 2.11.24

#31 Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 2.11.24 to 308

#32 Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 308 to 3.1.14

#33 Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 3.1.14 to 3.1.15

#34 Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 3.1.15 to 3.1.16

#35 Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 3.1.16 to 3.1.17

#36 Updated by Benoît PECCATTE about 2 years ago

  • Assignee deleted (Matthieu CERDA)

#37 Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 3.1.17 to 3.1.18

#38 Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 3.1.18 to 3.1.19

#39 Updated by François ARMAND over 1 year 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

#40 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.19 to 3.1.20

#41 Updated by Jonathan CLARKE over 1 year ago

  • Status changed from Discussion to New

#42 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.20 to 3.1.21

#43 Updated by François ARMAND over 1 year ago

  • Priority changed from 0 to 21

#44 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.21 to 3.1.22

#45 Updated by Benoît PECCATTE over 1 year ago

  • Priority changed from 21 to 34

#46 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.22 to 3.1.23

#47 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.23 to 3.1.24

#48 Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 3.1.24 to 3.1.25
  • Priority changed from 34 to 35

#49 Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 3.1.25 to 387

#50 Updated by Vincent MEMBRÉ 12 months ago

  • Target version changed from 387 to 4.1.10

#51 Updated by Nicolas CHARLES 12 months ago

  • Related to Bug #11798: Inventory error on xen VM added

#52 Updated by Vincent MEMBRÉ 10 months ago

  • Target version changed from 4.1.10 to 4.1.11
  • Priority changed from 35 to 36

#53 Updated by Vincent MEMBRÉ 8 months ago

  • Target version changed from 4.1.11 to 4.1.12
  • Priority changed from 36 to 37

#54 Updated by Vincent MEMBRÉ 7 months ago

  • Target version changed from 4.1.12 to 4.1.13

#55 Updated by Vincent MEMBRÉ 5 months ago

  • Target version changed from 4.1.13 to 4.1.14

#56 Updated by Benoît PECCATTE 5 months ago

  • Target version changed from 4.1.14 to 4.1.15
  • Priority changed from 37 to 38

#57 Updated by Vincent MEMBRÉ 2 months ago

  • Target version changed from 4.1.15 to 4.1.16

#58 Updated by Vincent MEMBRÉ about 1 month ago

  • Target version changed from 4.1.16 to 4.1.17

#59 Updated by Vincent MEMBRÉ 25 days ago

  • Target version changed from 4.1.17 to 4.1.18
  • Priority changed from 38 to 39

Also available in: Atom PDF