Comment 9 for bug 1302388

Ok so here it goes:

The resource job is not started because it's not present in the whitelist.

The gui does some rather confusing filtering. If you think like me, from plainbox POV, you see a set of jobs and you flag the ones you want to run (in some order), that gives you the *desired* job list. You pass that to plainbox's SelectJobs and get the run_list. You follow that and you're in happy land.

This is not what happens here:

First the ideal view is broken by generated jobs. To see all jobs you need to run some jobs. The GUI does the conservative bit by running *all* local jobs. This gives it the full job awareness.

Next comes the job selection view. As you probably recall the list of jobs displayed in the view where one can select which jobs are to be executed is not the full list of know jobs. That list is filtered by the whitelists selected in the whitelist selection screen (I haven't investigated that part yet). So we can now see our resource jobs because plainbox knows they are required OR because they were on the whitelist.

Now this is the critical piece. After making the selection, PrepareJobs() discards anything that we selected that is not in the whitelist.