dos.py creates env despite of exception
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
In Progress
|
Medium
|
ElenaRossokhina | ||
Mitaka |
Won't Fix
|
Medium
|
ElenaRossokhina | ||
Newton |
In Progress
|
Medium
|
ElenaRossokhina |
Bug Description
dos.py creates a new env despite of exception that's related to invalid network pool.
Probably the same behavior can be observed in other similar cases.
This pollutes the env namespace and prevents from creating the new env with the same name with valid data after correction.
Steps to reproduce:
0. check if no 'foo' env via: dos.py list
1. dos.py create --iso-path <path to iso> --node-count 3 --vcpu 4 --ram 4096 --admin-vcpu 4 --admin-ram 4096 --net-pool <improper net pool> foo
2. check if exception occurs
3. check if 'foo' env is in 'dos.py list' output
Expected Behavior: env shouldn't be created and added to the namespace in case of exceptions during creation
Actual Behavior: env is created and added to the namespace
(fuel-devops-
Traceback (most recent call last):
File "/home/
main()
File "/home/
Shell(
File "/home/
self.
File "/home/
prefix=
ValueError: invalid literal for int() with base 10: '10.109.0.0/27'
(fuel-devops-
NAME
-------
fuelweb_
moo
(fuel-devops-
2.9.12
tags: | added: fuel-devops |
Changed in fuel: | |
assignee: | nobody → Fuel DevOps (fuel-devops) |
milestone: | none → 8.0-updates |
tags: | added: area-devops |
Changed in fuel: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
milestone: | 8.0-updates → 8.0 |
Changed in fuel: | |
assignee: | Fuel DevOps (fuel-devops) → Fuel QA Team (fuel-qa) |
description: | updated |
tags: |
added: area-qa removed: area-devops |
Changed in fuel: | |
assignee: | Fuel QA Team (fuel-qa) → ElenaRossokhina (esolomina) |
Fix proposed to branch: master /review. openstack. org/261274
Review: https:/