Skip to content

tc error when using Loss and Delay with ControlNet #21

@mattiekat

Description

@mattiekat

I am consistently getting the error RTNETLINK answers: File exists when I attempt to use a ControlNet incident with both Delay and Loss. Furthermore, after this configuration is used, the error continues to happen even for ControlNet incidents which have only one or the other and have been tested to work on their own otherwise.

The following configuration consistently yields this problem.

{
 "Tasks": [{
   "Type": "ControlNet",
   "Timeout": "30s",
   "Delay": "100ms",
   "Loss": "30%"
 }],

 "Selector": {
	"Deployment": {
		"Name": "cf"
	},
	"Group": {
		"Name": "diego-cell"
	}
 }
}

The full error reported is:

Task execution: Shelling out to tc to add packet loss: Running command: 'tc qdisc add dev silk-vtep root netem loss 30% 75%', stdout: '', stderr: 'RTNETLINK answers: File exists
': exit status 2

When using ping -f -c 500 <DIEGO-CELL-IP> I find that it does introduce some latency which does not seem to go away but it does not introduce any packet loss.

This issue does not occur if the incidents are separated as such:

{
 "Tasks": [{
   "Type": "ControlNet",
   "Timeout": "30s",
   "Delay": "100ms"
 },{
   "Type": "ControlNet",
   "Timeout": "30s",
   "Loss": "30%"
 }],

 "Selector": {
	"Deployment": {
		"Name": "cf"
	},
	"Group": {
		"Name": "diego-cell"
	}
 }
}

The error also occurs if Loss and LossCorrelation are specified without Delay.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions