Adapt logic for global.conf changes

[jschmid1]

Signed-off-by: Joshua Schmid jschmid@suse.de

• changed logic for dependency resolution
• global.conf changes now result in core service restart(flags) (mon, mgr, osd)

~Ignore whitespace and indentation fixes. [auto]~

suse_internal: bsc#1149400

---

Checklist: ~- [ ] Added unittests and or functional tests~ ~- [ ] Adapted documentation~

• [x] Referenced issues or internal bugtracker
• [ ] Ran integration tests successfully (trigger with "@susebot run teuthology" in a GitHub comment; see the wiki for more information)

[jschmid1]

note to self: split up commits in

• whitespace changes
• actual code changes

[jschmid1]

note to self: split up commits in

~> * whitespace changes~

• actual code changes

For now, let's stick to the actual code changes until we reached consensus on the style-guide

[jschmid1]

@susebot run teuthology

[susebot]

Commit edbb5ad2381332027aac7b9268bbd8c768fbd773 is NOT OK for suite deepsea:tier2. Check tests results in the Jenkins job: http://ci.ses.suse.de:8080/job/pr-deepsea/282/

[jschmid1]

Commit edbb5ad is NOT OK for suite deepsea:tier2. Check tests results in the Jenkins job: http://ci.ses.suse.de:8080/job/pr-deepsea/282/

the CI caught a bug in this patch, fixing

[jschmid1]

ready for a second round of reviews

[jschmid1]

@susebot run teuthology

[susebot]

Commit 320c1c954db48af8977cabbc1bc8380e9698718a is NOT OK for suite deepsea:tier2. Check tests results in the Jenkins job: http://ci.ses.suse.de:8080/job/pr-deepsea/283/

[jschmid1]

unrelated to this pr, but it seems we have a failure in stage.4.. re-running to verify

[jschmid1]

@susebot run teuthology

[susebot]

Commit 320c1c954db48af8977cabbc1bc8380e9698718a is NOT OK for suite deepsea:tier2. Check tests results in the Jenkins job: http://ci.ses.suse.de:8080/job/pr-deepsea/285/

[jschmid1]

@smithfarm It seems that the CI is currently not able to deploy nfs-ganesha. Did we update the build artifacts already?

[jschmid1]

@susebot run teuthology

[smithfarm]

@jschmid1 I don't see where the CI is unable to deploy nfs-ganesha. What I see is this:

• Stage 4 completes successfully
• ganesha smoke test fails with:

2019-09-16T14:00:38.503 INFO:teuthology.orchestra.run.target192168000079.stderr:scripts/ganesha_smoke_test.sh: line 225: /root/mnt/rgw/bucket1/hello.txt: No such file or directory

[susebot]

Commit 320c1c954db48af8977cabbc1bc8380e9698718a is NOT OK for suite deepsea:tier2. Check tests results in the Jenkins job: http://ci.ses.suse.de:8080/job/pr-deepsea/287/

[jschmid1]

The failure is weird though. All tests before and after were successful.. This branch is clearly not changing anything in the NFS-ganesha area.. re-triggering to be extra-extra-sure

[jschmid1]

@susebot run teuthology

[jschmid1]

apparently we have two nfs-ganesha tests:

1) with mds backend 2) with rgw backed

only 1) fails. Maybe the mds state fails while checking for changed files somehow? Why wouldn't the standard(non-ganesha) mds test fail?..

[susebot]

Commit 320c1c954db48af8977cabbc1bc8380e9698718a is NOT OK for suite deepsea:tier2. Check tests results in the Jenkins job: http://ci.ses.suse.de:8080/job/pr-deepsea/290/

[jschmid1]

I'm puzzled..

[susebot]

Commit 320c1c954db48af8977cabbc1bc8380e9698718a is NOT OK for suite deepsea:tier2. Check tests results in the Jenkins job: https://ceph-ci.suse.de/job/pr-deepsea/5/

[susebot]

Commit 320c1c954db48af8977cabbc1bc8380e9698718a is NOT OK for suite deepsea:tier2. Check tests results in the Jenkins job: https://ceph-ci.suse.de/job/pr-deepsea/1/

[jschmid1]

Closing.. Reopen if needed