MAAS does not setup rsyslog on deployed nodes with curtin

Bug #1478107 reported by Blake Rouse
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MAAS
Invalid
Wishlist
Unassigned

Bug Description

MAAS needs to pass configuration to each deployed node so that they will send all syslog messages back to MAAS.

I believe this should be able to be turned on and off, the rsyslog server address should be configurable, or allow option to send rsyslog back to region controller.

The cloud-init configuration is documented here in this cloud-init bug: https://bugs.launchpad.net/cloud-init/+bug/1478103

Changed in maas:
importance: High → Wishlist
Changed in maas:
milestone: 1.9.0 → 2.0.0
Changed in maas:
milestone: 2.0.0 → 2.1.0
Changed in maas:
milestone: 2.1.0 → 2.1.1
Changed in maas:
milestone: 2.1.1 → 2.1.2
Changed in maas:
milestone: 2.1.2 → 2.1.3
Changed in maas:
milestone: 2.1.3 → next
Revision history for this message
Adam Collard (adam-collard) wrote :

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team

Changed in maas:
status: Triaged → Invalid
Changed in maas:
milestone: next → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.