Project

General

Profile

Feature #16196

Bug #15071: Make our server backup process more usable

Feature #16165: make puppet-lizard-manifests suitable for masterless puppet

fix puppet-sshd for masterless puppet

Added by groente 10 months ago. Updated 10 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Infrastructure
Target version:
-
Start date:
12/06/2018
Due date:
% Done:

100%

Spent time:
Feature Branch:
puppet-sshd
Type of work:
Sysadmin
Blueprint:
Starter:
Affected tool:

Description

Trying to apply tails::base masterless results in the following warnings:

Warning: You cannot collect exported resources without storeconfigs being set; the collection will be ignored at /etc/puppet/code/modules/sshd/manifests/client/base.pp:12:12
Warning: You cannot collect exported resources without storeconfigs being set; the export is ignored at /etc/puppet/code/modules/sshd/manifests/base.pp:40:5
Warning: You cannot collect exported resources without storeconfigs being set; the export is ignored at /etc/puppet/code/modules/sshd/manifests/base.pp:50:7
Warning: You cannot collect exported resources without storeconfigs being set; the export is ignored at /etc/puppet/code/modules/sshd/manifests/base.pp:59:5
Warning: You cannot collect exported resources without storeconfigs being set; the export is ignored at /etc/puppet/code/modules/sshd/manifests/base.pp:68:7


Related issues

Blocks Tails - Feature #13284: Core work: Sysadmin (Adapt our infrastructure) Confirmed 06/30/2017

History

#1 Updated by intrigeri 10 months ago

  • Blocks Feature #13284: Core work: Sysadmin (Adapt our infrastructure) added

#2 Updated by groente 10 months ago

  • Status changed from Confirmed to Resolved
  • Feature Branch set to puppet-sshd

fixed in commit 7d33d1bcede7467344a02457fa1f5f4eb683cf08

#3 Updated by intrigeri 10 months ago

  • Status changed from Resolved to In Progress
  • % Done changed from 0 to 50

If you don't mind, I'd rather keep this ticket opened until a MR is at least submitted upstream, on the grounds that this fix is good for our immediate problem but to call this task done, it should not make maintenance harder (which seems realistic in this case: so far we've managed to avoid diverging from upstream for this module and your changes seem acceptable for upstream at first glance :)

#4 Updated by groente 10 months ago

  • Status changed from In Progress to Resolved
  • Assignee deleted (groente)
  • Target version deleted (Tails_3.12)
  • % Done changed from 50 to 100

Also available in: Atom PDF