Env description isn't required in the definition, but user sees warning message if it's absent
Bug #1418916 reported by
Anastasia Kuznetsova
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mistral |
Fix Released
|
Low
|
Hardik Parekh | ||
Liberty |
Fix Released
|
Low
|
Hardik Parekh |
Bug Description
Steps to reproduce:
1. Create file 'env.yaml' with environment definition without specifying environment description:
--
name: test_env
variables:
var: value
2. Create env with its definition:
mistral environment-create env.yaml
Observed result:
Warning message:
'Environment' object has no attribute 'description'
Expected result:
No warning message, just table with information about created env
summary: |
- Env description isn't required in the definition, but user see warning + Env description isn't required in the definition, but user sees warning message if its absent |
summary: |
Env description isn't required in the definition, but user sees warning - message if its absent + message if it's absent |
tags: | added: low-hanging-fruit |
Changed in mistral: | |
milestone: | none → kilo-3 |
no longer affects: | mistral/kilo |
Changed in mistral: | |
milestone: | 1.0.0 → none |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/228342
Review: https:/