2020-09-09 07:54:00 |
Bogdan Dobrelya |
bug |
|
|
added bug |
2020-09-09 07:54:39 |
Bogdan Dobrelya |
description |
Since most of tripleo-ansible modules do 'import foobar', we should ensure that we have the correct yaml python packages installed. Some of them, like python3-dmidecode may be in base Centos8 images. But some may not, especially for custom deployed-servers provided by users for deployments.
Those packages must be tracked and ensured to be installed by tripleo, or at least documented as the modules get updated. |
Since most of tripleo-ansible modules do 'import foobar', we should ensure that we have the correct yaml python packages installed. Some of them, like python3-dmidecode may be in base Centos8 images. But some may not, especially for custom deployed-servers provided by users for deployments.
Those packages must be tracked and ensured to be installed by tripleo, or validated deploy-time, or at least documented as the modules get updated. |
|
2020-09-09 07:54:53 |
Bogdan Dobrelya |
tags |
|
tech-debt train-backport-potential ussuri-backport-potential |
|
2020-09-09 07:54:56 |
Bogdan Dobrelya |
tripleo: importance |
Undecided |
High |
|
2020-09-09 07:54:58 |
Bogdan Dobrelya |
tripleo: milestone |
|
victoria-3 |
|
2020-09-09 07:55:01 |
Bogdan Dobrelya |
tripleo: status |
New |
Triaged |
|
2020-09-09 07:55:46 |
Bogdan Dobrelya |
description |
Since most of tripleo-ansible modules do 'import foobar', we should ensure that we have the correct yaml python packages installed. Some of them, like python3-dmidecode may be in base Centos8 images. But some may not, especially for custom deployed-servers provided by users for deployments.
Those packages must be tracked and ensured to be installed by tripleo, or validated deploy-time, or at least documented as the modules get updated. |
Since most of tripleo-ansible modules do 'import foobar', we should ensure that we have the correct yaml python packages installed on target hosts. Some of them, like python3-dmidecode may be in base Centos8 images. But some may not, especially for custom deployed-servers provided by users for deployments.
Those packages must be tracked and ensured to be installed by tripleo, or validated deploy-time, or at least documented as the modules get updated. |
|
2020-09-09 07:55:55 |
Bogdan Dobrelya |
description |
Since most of tripleo-ansible modules do 'import foobar', we should ensure that we have the correct yaml python packages installed on target hosts. Some of them, like python3-dmidecode may be in base Centos8 images. But some may not, especially for custom deployed-servers provided by users for deployments.
Those packages must be tracked and ensured to be installed by tripleo, or validated deploy-time, or at least documented as the modules get updated. |
Since most of tripleo-ansible modules do 'import foobar', we should ensure/validate that we have the correct yaml python packages installed on target hosts. Some of them, like python3-dmidecode may be in base Centos8 images. But some may not, especially for custom deployed-servers provided by users for deployments.
Those packages must be tracked and ensured to be installed by tripleo, or validated deploy-time, or at least documented as the modules get updated. |
|
2020-09-09 07:56:14 |
Bogdan Dobrelya |
description |
Since most of tripleo-ansible modules do 'import foobar', we should ensure/validate that we have the correct yaml python packages installed on target hosts. Some of them, like python3-dmidecode may be in base Centos8 images. But some may not, especially for custom deployed-servers provided by users for deployments.
Those packages must be tracked and ensured to be installed by tripleo, or validated deploy-time, or at least documented as the modules get updated. |
Since most of tripleo-ansible modules do 'import foobar', we should ensure/validate that we have the correct python packages installed on target hosts. Some of them, like python3-dmidecode may be in base Centos8 images. But some may not, especially for custom deployed-servers provided by users for deployments.
Those packages must be tracked and ensured to be installed by tripleo, or validated deploy-time, or at least documented as the modules get updated. |
|
2020-09-09 08:07:29 |
Bogdan Dobrelya |
bug |
|
|
added subscriber Alex Schultz |
2020-09-09 08:21:32 |
Bogdan Dobrelya |
description |
Since most of tripleo-ansible modules do 'import foobar', we should ensure/validate that we have the correct python packages installed on target hosts. Some of them, like python3-dmidecode may be in base Centos8 images. But some may not, especially for custom deployed-servers provided by users for deployments.
Those packages must be tracked and ensured to be installed by tripleo, or validated deploy-time, or at least documented as the modules get updated. |
Since most of tripleo-ansible modules do 'import foobar', we should ensure/validate that we have the correct python packages installed on target hosts. Some of them, like python3-dmidecode may be in base Centos8 images. But some may not, especially for custom deployed-servers provided by users for deployments.
Those packages must be tracked and ensured to be installed by tripleo (preferred), or validated deploy-time (nah...), or at least documented as the modules get created or changed by devs.
That also applies to adding action plugins' deps for python-tripleoclient or tripleo-ansible perhaps |
|
2020-09-09 14:20:16 |
Alex Schultz |
tripleo: importance |
High |
Wishlist |
|
2020-10-19 13:26:26 |
Bogdan Dobrelya |
tripleo: importance |
Wishlist |
Medium |
|
2020-10-19 13:51:41 |
OpenStack Infra |
tripleo: status |
Triaged |
In Progress |
|
2020-10-19 13:51:41 |
OpenStack Infra |
tripleo: assignee |
|
Bogdan Dobrelya (bogdando) |
|
2020-11-03 11:54:45 |
Marios Andreou |
tripleo: milestone |
victoria-3 |
wallaby-1 |
|
2020-11-06 19:41:40 |
OpenStack Infra |
tripleo: status |
In Progress |
Fix Released |
|