Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Zaza tests on openstack need python-openstackclient #154

Closed
sudeephb opened this issue Jan 4, 2024 · 10 comments
Closed

Zaza tests on openstack need python-openstackclient #154

sudeephb opened this issue Jan 4, 2024 · 10 comments
Labels
Fix Released Undecided
Milestone
21.07

Comments

@sudeephb
Copy link
Contributor

sudeephb commented Jan 4, 2024 •
edited
Loading

Since b46f13ef113e690493364dabc87821699626d8e6 in zaza, if running tests on an OpenStack cloud provider, each bundle test concludes with a cleanup routine that needs the python-openstackclient package in requirements.txt for the tox environment, plus the OS_ environment vars exported/passed through such that the Openstack client actually works. If these are not set, the test fails on the first bundle cleanup and does not continue to the remaining bundles.

Imported from Launchpad using lp2gh.

  • date created: 2021-04-21T02:17:20Z

  • owner: xavpaice

  • assignee: None

  • the launchpad url
@sudeephb
Copy link
Contributor Author

sudeephb commented Jan 4, 2024

(by xavpaice)
Resolution:

Add to requirements.txt:

python-openstackclient

Add to tox.ini under passenv =:

OS_REGION_NAME
OS_AUTH_VERSION
OS_AUTH_URL
OS_PROJECT_DOMAIN_NAME
OS_USERNAME
OS_PASSWORD
OS_PROJECT_ID
OS_USER_DOMAIN_NAME
OS_PROJECT_NAME
OS_IDENTITY_API_VERSION

Prior to running any test: source a valid novarc.

@sudeephb
Copy link
Contributor Author

sudeephb commented Jan 4, 2024

(by rgildein)
Should this be resolved in zaza? There is bug in zaza 1, and I think
it make much more sense to update it there instead of each charm.

@sudeephb
Copy link
Contributor Author

sudeephb commented Jan 4, 2024

(by rgildein)
This was fixed by Xav in https://code.launchpad.net/~xavpaice/charm-duplicity/+git/charm-duplicity/+merge/401661.

@sudeephb
Copy link
Contributor Author

sudeephb commented Jan 4, 2024

(by rgildein)
This was fixed by this commit https://git.launchpad.net/charm-fstab-config/commit/src/tests/functional/requirements.txt?id=8e787e7a8b72ce113f6e97eab7f5cf2177729229

@sudeephb
Copy link
Contributor Author

sudeephb commented Jan 4, 2024

(by rgildein)
released in 22.04

1 similar comment
@sudeephb
Copy link
Contributor Author

sudeephb commented Jan 4, 2024

(by rgildein)
released in 22.04

@sudeephb
Copy link
Contributor Author

sudeephb commented Jan 4, 2024

(by rgildein)
released in 22.08

@sudeephb
Copy link
Contributor Author

sudeephb commented Jan 4, 2024

(by rgildein)
This was fixed and released in 23.01

@sudeephb
Copy link
Contributor Author

sudeephb commented Jan 4, 2024

(by eric-chen)
This charm is no longer being actively maintained. Please use ceph-dashboard charm that uses the built-in Ceph Dashboard.
https://opendev.org/openstack/charm-ceph-dashboard

1 similar comment
@sudeephb
Copy link
Contributor Author

sudeephb commented Jan 4, 2024

(by eric-chen)
This charm is no longer being actively maintained. Please use ceph-dashboard charm that uses the built-in Ceph Dashboard.
https://opendev.org/openstack/charm-ceph-dashboard

@sudeephb sudeephb added this to the 21.07 milestone Jan 4, 2024
@sudeephb sudeephb closed this as completed Jan 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Fix Released Undecided
Projects
None yet
Milestone
21.07
Development

No branches or pull requests
1 participant
@sudeephb