validate reports problems then says 'all jobs seem to be valid'

Bug #1297746 reported by Zygmunt Krynicki on 2014-03-26
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Zygmunt Krynicki

Bug Description

This was demonstrated during the plainbox provider info session

After removing the ID field and running validate, some jobs could not be validated (printing a few warnings/errors) but then printed 'all jobs seem to be valid'

Related branches

Zygmunt Krynicki (zyga) wrote :

This only happens if we remove the 'id' field. This is because that field is validated separately at a lower level. Other fields are not validated when we load the provider (like the broken one here) and are only validated by ` validate`.

Zygmunt Krynicki (zyga) on 2014-03-26
Changed in checkbox:
status: Confirmed → Triaged
Zygmunt Krynicki (zyga) wrote :

I think that to fix this bug we need to:

1) Remove the requirement to have 'id' to instantiate a job definition (allowing broken definitions to exist as objects)
2) Reject invalid jobs / providers in typical operations (probably complaining loudly as we do now)
3) Allow validate to work as intended

Zygmunt Krynicki (zyga) on 2014-03-28
Changed in checkbox:
status: Triaged → In Progress
assignee: nobody → Zygmunt Krynicki (zkrynicki)
Zygmunt Krynicki (zyga) wrote :

I've added a merge proposal with the initial implementation. I'll polish it a little and we can finish this task.

Zygmunt Krynicki (zyga) on 2014-03-31
Changed in checkbox:
status: In Progress → Fix Committed
Zygmunt Krynicki (zyga) on 2014-03-31
Changed in checkbox:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers