[AURORA-1794] Scheduler fails to start if -enable_revocable_ram is toggled

• Type: Story
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.16.0
• Fix Version/s: 0.17.0
• Assignee: Stephan Erb
• Reporter: Stephan Erb
• Created: 13/Oct/16 08:15
• Updated: 01/Feb/17 07:54
• Resolved: 18/Oct/16 07:09

Description

The scheduler does not start if -enable_revocable_ram is set:

Exception in thread "main" java.lang.IllegalStateException: A value cannot be changed after it was read.
        at com.google.common.base.Preconditions.checkState(Preconditions.java:174)
        at org.apache.aurora.common.args.Arg.set(Arg.java:54)
        at org.apache.aurora.common.args.ArgumentInfo.setValue(ArgumentInfo.java:128)
        at org.apache.aurora.common.args.OptionInfo.load(OptionInfo.java:131)
        at org.apache.aurora.common.args.ArgScanner.process(ArgScanner.java:368)
        at org.apache.aurora.common.args.ArgScanner.parse(ArgScanner.java:200)
        at org.apache.aurora.common.args.ArgScanner.parse(ArgScanner.java:178)
        at org.apache.aurora.common.args.ArgScanner.parse(ArgScanner.java:155)
        at org.apache.aurora.scheduler.app.SchedulerMain.applyStaticArgumentValues(SchedulerMain.java:226)
        at org.apache.aurora.scheduler.app.SchedulerMain.main(SchedulerMain.java:197)

This is an unfortunate oversight at my end. When introducing the feature, I deferred the e2e test. It 'worked' in a manual test - at least that is what I believed. Probably, I had only added the flag to the config in the repo, but not to the one that was actually started in vagrant.