"radvd" daemon does not work by default in some containers
Bug #1844688 reported by
Rodolfo Alonso
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Rodolfo Alonso |
Bug Description
Since [1], the radvd daemon is spawned with parameter "-u username". This drops the root privileges and changes the user ID to "username".
In some deployments (e.g. TripleO), the "neutron" user does not have, inside the L3 agent container, the permissions to modify the host kernel interfaces (from journal.log):
wrz 13 13:08:15 controller-2 radvd[904324]: failed to set LinkMTU (1500) for qr-7befc0a3-04: Permission denied
wrz 13 13:08:15 controller-2 radvd[904324]: failed to set CurHopLimit (64) for qr-7befc0a3-04: Permission denied
This problem was found in Rocky.
[1] https:/
Changed in neutron: | |
assignee: | nobody → Rodolfo Alonso (rodolfo-alonso-hernandez) |
description: | updated |
tags: | added: ipv6 |
Changed in neutron: | |
importance: | Undecided → Medium |
To post a comment you must log in.
Fix proposed to branch: master /review. opendev. org/683207
Review: https:/