[MESOS-6874] Agent silently ignores FS isolation when protobuf is malformed - ASF JIRA

XML

Word

Printable

JSON

Details

Type: Bug
Status: Resolved
Priority: Minor
Resolution: Fixed
Affects Version/s: 1.1.0
Fix Version/s: 1.8.0
Component/s: containerization
Labels:
- foundations
- newbie

Sprint:
Mesos Foundations RI12 Sp 42
Story Points:
5

Description

cc vinodkone

I accidentally set my Mesos ContainerInfo to include a DockerInfo instead of a MesosInfo:

executorInfoBuilder.setContainer(
                     Protos.ContainerInfo.newBuilder()
                     .setType(Protos.ContainerInfo.Type.MESOS)
                     .setDocker(Protos.ContainerInfo.DockerInfo.newBuilder()
                         .setImage(podSpec.getContainer().get().getImageName()))

I would have expected a validation error before or during containerization, but instead, the agent silently decided to ignore filesystem isolation altogether, and launch my executor on the host filesystem.

Attachments

Issue Links

causes

MESOS-9740 Invalid protobuf unions in ExecutorInfo::ContainerInfo will prevent agents from reregistering with 1.8+ masters

Resolved

links to

GitHub Pull Request #326

Activity

People

Assignee:: Andrei Sekretenko

Reporter:: Michael Gummelt

Shepherd:: Benno Evers

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Dates

Created:: 06/Jan/17 20:08

Updated:: 24/Apr/19 04:04

Resolved:: 19/Mar/19 18:39

Time Tracking

Estimated:

Not Specified

Remaining:

Logged:

40m