Project

General

Profile

Bug #7671

Propagate promises error when no nodes behind a relay

Added by Alexis MOUSSET almost 2 years ago. Updated 7 months ago.

Status:
Released
Priority:
N/A
Category:
Initial promises & sys tech
Target version:
Target version (plugin):
Severity:
User visibility:
Effort required:
Priority:
0

Description

When there are no nodes behind a relay, it produces an error:

2015-12-21T16:34:22+0000  verbose: /default/propagatePromises/methods/'any'/default/rudder_common_report/methods/'report'/default/rudder_common_report_index/reports/'@@DistributePolicy@@result_error@@f5ac864b-b01b-465c-a2a0-b6c024916ac0-DP@@f5ac864b-b01b-465c-a2a0-b6c024916ac0-distributePolicy@@1@@Propagate promises@@None@@2015-12-21 16:34:20+00:00..f5ac864b-b01b-465c-a2a0-b6c024916ac0@.Cannot propagate policy files'[0]: Comment 'Reporting for DistributePolicy message Cannot propagate policy files for index '

Happens at least on 3.1 (with Centos 7)


Subtasks

Bug #10267: Adapt parent ticket for branch 4.0ReleasedAlexis MOUSSET


Related issues

Related to Rudder - Bug #9881: Error in relay promises when there are no shared files Released

Associated revisions

Revision d25f5a7c
Added by Nicolas CHARLES 9 months ago

Fixes #7671: Propagate promises error when no nodes behind a relay

History

#1 Updated by Alexis MOUSSET almost 2 years ago

2015-12-21T16:34:21+0000  verbose: /default/propagatePromises/files/'/var/rudder/share/'[0]: .....................[.h.a.i.l.].................................
2015-12-21T16:34:21+0000  verbose: /default/propagatePromises/files/'/var/rudder/share/'[0]: Strong authentication of server 'server.rudder.local' connection confirmed
2015-12-21T16:34:21+0000  verbose: /default/propagatePromises/files/'/var/rudder/share/'[0]: Public key identity of host '192.168.43.2' is: MD5=c0e16f5da15ba203e237f2ad58e5f1e3
2015-12-21T16:34:22+0000  verbose: /default/propagatePromises/files/'/var/rudder/share/'[0]: Server returned error: Unspecified server refusal (see verbose server output)
2015-12-21T16:34:22+0000     info: /default/propagatePromises/files/'/var/rudder/share/'[0]: Can't stat file '/var/rudder/share/f5ac864b-b01b-465c-a2a0-b6c024916ac0/share' on '192.168.43.2' in files.copy_from promise
2015-12-21T16:34:22+0000  verbose: /default/propagatePromises/files/'/var/rudder/share/'[0]: Defining promise result class 'could_not_propagate_promise'

#2 Updated by Alexis MOUSSET almost 2 years ago

On the server:

2015-12-21T16:46:27+0000  verbose: 192.168.43.3> Requested file is a dead symbolic link (filename: /var/rudder/share/f5ac864b-b01b-465c-a2a0-b6c024916ac0/share)
2015-12-21T16:46:27+0000     info: 192.168.43.3> Couldn't stat (lstat: No such file or directory) filename: /var/rudder/share/f5ac864b-b01b-465c-a2a0-b6c024916ac0/share
2015-12-21T16:46:27+0000     info: 192.168.43.3> Access control in sync
2015-12-21T16:46:27+0000  verbose: 192.168.43.3> REFUSAL to (user=root,ip=192.168.43.3) of request: SYNCH 1450716387 STAT /var/rudder/share/f5ac864b-b01b-465c-a2a0-b6c024916ac0/share

And:

root@server:/home/vagrant# ls -ahl  /var/rudder/share/f5ac864b-b01b-465c-a2a0-b6c024916ac0
total 0
drwxrwx---. 3 root root 18 Dec 21 16:25 .
drwxrwx---. 3 root root 49 Dec 21 16:25 ..
drwxrwx---. 3 root root 31 Dec 21 16:25 rules

#3 Updated by Alexis MOUSSET almost 2 years ago

  • Description updated (diff)

#4 Updated by Alexis MOUSSET almost 2 years ago

  • Subject changed from Propagate promises error on relay fresh install to Propagate promises error when no nodes behind a relay

#5 Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 3.1.6 to 3.1.7

#6 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.7 to 3.1.8

#7 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.8 to 3.1.9

#8 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.9 to 3.1.10

#9 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.10 to 3.1.11

#10 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.11 to 3.1.12

#11 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.12 to 3.1.13

#12 Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 3.1.13 to 3.1.14

#13 Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 3.1.14 to 3.1.15

#14 Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 3.1.15 to 3.1.16

#15 Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 3.1.16 to 3.1.17

#16 Updated by Vincent MEMBRÉ 12 months ago

  • Target version changed from 3.1.17 to 3.1.18

#17 Updated by Alexis MOUSSET 11 months ago

  • Related to Bug #9881: Error in relay promises when there are no shared files added

#18 Updated by Vincent MEMBRÉ 9 months ago

  • Target version changed from 3.1.18 to 3.1.19

#19 Updated by Nicolas CHARLES 9 months ago

If there are no promises to propagate (no files there), no class is defined.
We assume in this case that if update was ok, then this is ok as well

Ok transfert class condition is

(rudder_ncf_hash_update_ok|(rudder_ncf_hash_update_repaired.rudder_ncf_common_updated_ok.rudder_ncf_local_updated_ok)).(rudder_promises_generated_ok|(rudder_promises_generated_repaired.config_ok)).!(rudder_promises_generated_repaired|rudder_promises_generated_error|rudder_t
ools_updated_error|rudder_tools_updated|rudder_tools_update_error|rudder_ncf_common_updated|rudder_ncf_common_update_error|rudder_ncf_local_updated|rudder_ncf_local_update_error|config|no_update|rudder_ncf_hash_update_error|rudder_ncf_has
h_update_repaired)

#20 Updated by Nicolas CHARLES 9 months ago

  • Status changed from New to In progress
  • Assignee set to Nicolas CHARLES

#21 Updated by Nicolas CHARLES 9 months ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to Alexis MOUSSET
  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/1119

#22 Updated by Nicolas CHARLES 9 months ago

actually, condition is

root_server|((rudder_ncf_hash_update_ok|(rudder_ncf_hash_update_repaired.rudder_ncf_common_updated_ok.rudder_ncf_local_updated_ok)).(rudder_promises_generated_ok|(rudder_promises_generated_repaired.config_ok)).!(rudder_promises_generated_error|rudder_tools_updated_error|rudder_tools_update_error|rudder_ncf_common_update_error|rudder_ncf_local_update_error|no_update|rudder_ncf_hash_update_error))

#23 Updated by Nicolas CHARLES 9 months ago

  • Status changed from Pending technical review to Pending release

#24 Updated by Vincent MEMBRÉ 7 months ago

  • Status changed from Pending release to Released
  • Priority set to 0

This bug has been fixed in Rudder 3.1.19, 4.0.4 and 4.1.1 which were released today.

Also available in: Atom PDF