AllowedValue constraints incorrectly handles null value

Bug #1655645 reported by Peter Razumovsky
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Heat
Invalid
Medium
Unassigned

Bug Description

Let our template will be next:

heat_template_version: newton

resources:
  rs:
    type: OS::Heat::RandomString
    properties:
      sequence: null

sequence property has no default value, so it will be equals to "".

If I try to create stack, I get next error:

ERROR: Property error: : resources.rs.properties.sequence: : "" is not an allowed value [lettersdigits, letters, lowercase, uppercase, digits, hexdigits, octdigits].

That's incorrect at the point of user, because I specify null property, there's no "" value - such error confuses. Need to fix such behaviour.

Changed in heat:
status: New → Invalid
assignee: Peter Razumovsky (prazumovsky) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.