DistributedCloud using deprecated oslo messaging fields
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| StarlingX |
Low
|
Bart Wensley |
Bug Description
Brief Description
-----------------
DistributedCloud is using an oslo_messaging call from pike. (5.30.6)
The method signature was deprecated in stein, and removed in rocky.
Therefore when we move to a newer oslo_messaging, this code will need to be updated.
Severity
--------
Minor
Steps to Reproduce
------------------
None. Future coding issue
Expected Behavior
------------------
N/A. Future coding issue
Actual Behavior
----------------
N/A. Future coding issue
Reproducibility
---------------
N/A. Future coding issue
System Configuration
-------
Distributed Cloud'
Branch/Pull Time/Commit
-------
Master Branch. Any time before Feb 27, 2020.
Last Pass
---------
N/A. Future coding issue
Timestamp/Logs
--------------
N/A. Future coding issue
Test Activity
-------------
Developer Testing
Workaround
----------
N/A. Future coding issue
Ghada Khalil (gkhalil) wrote : | #1 |
Changed in starlingx: | |
importance: | Undecided → Low |
status: | New → Triaged |
tags: | added: stx.distcloud |
Changed in starlingx: | |
assignee: | nobody → Al Bailey (albailey1974) |
Reviewed: https:/
Committed: https:/
Submitter: Zuul
Branch: master
commit 501fa35af2780d5
Author: Al Bailey <email address hidden>
Date: Tue Jan 21 17:04:56 2020 -0600
Update pylint for distributedcloud
The pylint that was specified as an upper constraint was not
as strict as the newer versions.
- Fixed or suppressed any new error codes being reported.
Suppressed error codes should be fixed by additional reviews.
- added a zuul target for pylint
- Added dcdbsync to the folders being processed by pylint.
- Removed the env:UPPER_
does not override the upper constraints with an newer version.
- Needed to add greenlet to the extension-
runtime introspection of that component is not possible.
- oslo-messaging get_transport deprecated 'aliases' in pike, and
removed it in rocky. The packaged version in STX is 5.30.6
which still supports aliases. This requires us to explicitly
run tox with the version that we ship (pre-stein). This is
controlled by a local upper-constrain
Related-Bug: 1865054
- Paste file handling reports a pylint issue which has been suppressed
Related-Bug: 1865085
Story: 2004515
Task: 38882
Change-Id: Ie7c8c2adab1eeb
Signed-off-by: Al Bailey <email address hidden>
Related fix proposed to branch: f/centos8
Review: https:/
Reviewed: https:/
Committed: https:/
Submitter: Zuul
Branch: f/centos8
commit 25c9d6ed3861f2d
Author: albailey <email address hidden>
Date: Wed Mar 25 15:43:32 2020 -0500
Removing ddt from unit tests
This cleanup should assist in transitioning to
stestr and fixtures, as well as py3 support.
The ddt data is primarily unused, only subcloud, route
and endpoints were being loaded.
The information in the data files was out of date,
and not necessarily matching the current product model.
Story: 2004515
Task: 39160
Change-Id: Iddd7ed4664b0d5
Signed-off-by: albailey <email address hidden>
commit 7f3827f24d2fb3c
Author: Tao Liu <email address hidden>
Date: Thu Mar 12 09:46:29 2020 -0400
Keystone token and resource caching
Add the following misc. changes to dcorch and dcmanager components:
- Cache the master resource in dcorch audit
- Consolidate the openstack drivers to common module, combine the
dcmanager and dcorch sysinv client. (Note: the sdk driver that
used by nova, neutron and cinder will be cleaned as part of
story 2006588).
- Update the common sdk driver:
. in order to avoid creating new keystone client multiple times
. to add a option for caching region clients, in addition to the
keystone client
. finally, to randomize the token early renewal duration
- Change subcloud audit manager, patch audit manager,
and sw update manager to:
utilize the sdk driver which caches the keystone client and token
Test cases:
1. Manage/unmanage subclouds
2. Platform resources sync and audit
3. Verify the keystone token is cached until the token is
expired
4. Add/delete subclouds
5. Managed subcloud goes offline/online (power off/on)
6. Managed subcloud goes offline/online (delete/add a static route)
7. Apply a patch to all subclouds via patch Orchestration
Story: 2007267
Task: 38865
Change-Id: I75e0cf66a797a6
Signed-off-by: Tao Liu <email address hidden>
commit 3a1bf60caddfa2e
Author: Jessica Castelino <email address hidden>
Date: Wed Mar 11 16:23:21 2020 -0400
Cleanup subcloud details when subcloud add fails
Failure during add subcloud prevents subcloud from being added again
with the same name as the subcloud details are not cleaned up
properly. Fixes have been added for proper cleanup of dcorch database
tables, ansible subcloud inventory files, keystone endpoints, keystone
region, and addn_hosts_dc file when failure is encountered.
Test cases:
1. Add subcloud
2. Add subcloud with "--deploy-playbook"
3. Delete subcloud
4. Raise explicit exception in dcorch/
5. Raise explicit exception in dcmanager/
Change-Id: Iedf172c3e9c3c4
...
tags: | added: in-f-centos8 |
Bart Wensley (bartwensley) wrote : | #5 |
This was addressed by the following commit:
https:/
Changed in starlingx: | |
assignee: | Al Bailey (albailey1974) → Bart Wensley (bartwensley) |
status: | Triaged → Fix Released |
low priority / not gating for now -- needs to be handled when stx updates oslo_messaging