mongosh versions 2.2.0 appears to have changed the verbosity of logging.
We are attempting to extract version information from the output, but
looking at it manually shows no such output.
$ mongosh zaqar --eval 'db.dropDatabase();'
{ ok: 1, dropped: 'zaqar' }
Downgrading the package to the last release before 2.2.0, 2.1.5, reveals
what we had been expecting:
$ sudo apt install mongodb-mongosh=2.1.5
$ mongosh zaqar --eval 'db.dropDatabase();'
Current Mongosh Log ID: 65fd88a57854a39dcce03169
Connecting to: mongodb://127.0.0.1:27017/zaqar?directConnection=true&serverSelectionTimeoutMS=2000&appName=mongosh+2.1.5
Using MongoDB: 7.0.7
Using Mongosh: 2.1.5
For mongosh info see: https://docs.mongodb.com/mongodb-shell/
To help improve our products, anonymous usage data is collected and sent to MongoDB periodically (https://www.mongodb.com/legal/privacy-policy).
You can opt-out by running the disableTelemetry() command.
------
The server generated these startup warnings when booting
<snip>
------
{ ok: 1, dropped: 'zaqar' }
We *could* increase the verbosity again using the '--verbosity' flag,
but rather than relying on arbitrary logging output, we could just use
the 'db.version()' function to pull our server version. Use that
instead.
Change-Id: I1faa317ebfa9927a4d576bd4da72872fab160560
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Since there is no official repo of MongoDB
for Centos-Stream-9 or Rhel-9, we will build
the repo by script.
Change-Id: I1f20eb22d6e922d12e0d88aae5bf47c032db3cb3
The devstack install on ubuntu jammy (22.04) fails to check the
signature for the bionic-security repo and exits, as seen in
https://github.com/gophercloud/gophercloud/issues/2701.
This commit adds the required key.
Change-Id: Ifab19c36fbca1813dae35d65750deed4fd81b91c
This reverts commit 5a7636786e.
Reason for revert: We do not handle href links properly and this breaks other services depending on Zaqar.
Change-Id: I5fb0f2f25c280dd69cfb99d9f9b320df552462dc
Instead of manually downloading the package and having to keep
that url up-to-date. This patch switches to just using the bionic
security repo as a source.
Change-Id: I81383955aea253769b02df682e9712233da77c26
Simplify the version check to make it less error prone, use the right
version of the 22.04 repository from mongodb.org (jammy vs focal) and
stop trying to install libssl package that no longer exists on the
repository.
Change-Id: I49d32e555e6a0df15c0e059e8c4152a969ab3975
After this change, Zaqar-wsgi will not be forced to port 8888 by
devstack. Use apache proxy now and the endpoint will be like:
http://IP/messaging by default.
Change-Id: I413cd24a9ef70a8bbada46d63d5dfdff09366b3e
For fixing the issue that mongodb in not in ubuntu 22.04 release, we need
to give a work-around way to install mongodb successfully in 22.04.
Change-Id: I5bb488f33d1c24298bb96e2702d2c98415db6cf4
This is an automatically generated patch to ensure unit testing
is in place for all the of the tested runtimes for antelope. Also,
updating the template name to generic one.
See also the PTI in governance [1].
[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html
Change-Id: I29fcb9afa016b1321b0b4c0118a8d7ffbc00b02e
As per the community goal of migrating the policy file
the format from JSON to YAML[1], we need to do two things:
1. Change the default value of '[oslo_policy] policy_file''
config option from 'policy.json' to 'policy.yaml' with
upgrade checks.
2. Deprecate the JSON formatted policy file on the project side
via warning in doc and releasenotes.
Also replace policy.json to policy.yaml ref from doc and tests.
[1]https://governance.openstack.org/tc/goals/selected/wallaby/migrate-policy-format-from-json-to-yaml.html
Change-Id: I595b8c7cad7bb02486c8f0dd29fdc40789fc8e50
They are not used anymore, they are tasks are covered by native
Zuul functionalities and job definitions.
Change-Id: If8b0675194aea60ed2b38620425636bf0d436466
The upgrade pre/post script have been removed, because they are empty.
This change includes a few fixes for the grenade plugin:
- make sure to install mongo-tools when running grenade tests,
as they use mongodump which is part of that package.
- use sudo also when saving the redis dump file for the target
logs, as it already happens when the dump for the base logs
is copied.
The jobs have been ported separately from the tempest and rally
jobs because they can't be backported to all the older stable branches
like them (right now, only up to train).
Change-Id: I73c4c4dee994f13b7411a17f0c5d95ca9c84bd30
As part of Train community goal 'Support IPv6-Only Deployments and Testing'[1],
we need to define the integration job which deploy services
on IPv6 and perform testing to make sure service listen and communicate
over IPv6 properly.
Zaqar has legacy zuul jobs so base zuulv3 IPv6 job 'devstack-ipv6' and
'devstack-tempest-ipv6' cannot be used and we have to copy the whole
run.yaml to set the IPv6 setting and run the IPv6 verification
script via post_test_hook.
This commit adds the new job 'zaqar-tempest-swift-ipv6'
run on gate and set the required IPv6 setting'.
Change-Id: I9aece13783a061c4214157c3f7cfc9cc9f2a3f96
Story: #2005477
Task: #35941
In Queens, we support the old way to use pool_group and the
new way without it in Flavor both. In Stein, we will remove
the pool_group totally and only keep the new way in Flavor
and Pool.
The patch remove the pool group totally
Change-Id: I64fa5fde35f9b9f2e8aa4977eb2c253ffc6aee99
Implements: bp remove-pool-group-totally
This defaults to 0 anyway, and is being removed as the devstack
excercises are being removed. see https://review.openstack.org/#/c/581377/
Change-Id: I3b8db07fd20a706d191b4d1c58911286bff17f09
Option auth_uri from group keystone_authtoken is deprecated[1].
Use option www_authenticate_uri from group keystone_authtoken.
[1]https://review.openstack.org/#/c/508522/
Change-Id: Ieff5b69018e3824074b5a528a7b9d2a00dd7fb2e
TEMPEST_SERVICES global variable is not supported
by devstack since long back.
- I380dd20e5ed716a0bdf92aa02c3730359b8136e4
- I9c24705e494689f09a885eb0a640efd50db33fcf
Service availability of tempest known services will be
set by devstack with local check.
- I02be777bf93143d946ccbb8e9eff637bfd1928d4
This commit removes the unused TEMPEST_SERVICES setting
Related-Bug: #1743688
Change-Id: Iee8b10716efc6d48e97a3bcf3dafcc722239b2e3
This patch update the policy file generator guide.
And remove the realted action in devstack as well.
Change-Id: I7bd6aabe1d05245a1203380863c0444f6ea021f6
bp: policy-and-docs-in-code
The plugin has been split into its own repository[1] in accordance with
Queens Goal "Split Tempest Plugins into Separate Repos/Projects[2]".
This patch removes the local copy as well as the setuptools entry point.
We can also now remove the autodoc_tree_excludes pbr option since
there's no more plugin to exclude and it defaults to [setup.py].
[1] http://git.openstack.org/cgit/openstack/zaqar-tempest-plugin
[2] https://governance.openstack.org/tc/goals/queens/split-tempest-plugins.html
Implements: blueprint zaqar-tempest-plugin
Change-Id: Ia52d7f0a18e4b55260dc994f0802a96109280e24
The grenade gate sometimes fails with
"keystone did not start". this patch fix it
in grenade log, there are log as follows:
curl -g -k --noproxy '*' -s -o /dev/null -w '%{http_code}'
http://172.99.67.72:5000/v3/
wait_for_keystone:69 : die 69 'keystone did not start'
actually, KEYSTONE_AUTH_URI should be http://172.99.67.72/identity/v3
instead of
http://172.99.67.72:5000/v3/ which leads to keystone failure
Change-Id: I116e46ed30f6ce0fbc7b9207cc4f519438df8bc2
Use $API_WORKERS as process count and add other
wsgi options like thunderlock (recommended
to prevent thundering herd on accept).
Change-Id: I70fdc09edf524ba3733d03013d4bb296e8b2954b
This reverts commit 4a1a6b3766. It didn't
improve the situation, and at least it's failing early.
Conflicts:
devstack/plugin.sh
Change-Id: Idf16037e6a3bbc7f915e12827348eda663721d5e
By default, CORS middleware can allow requests from any origin. So it's not
necessary to use the 'enabled' option.
Closes-bug: #1677049
Co-Authored-By: wangxiyuan<wangxiyuan@huawei.com>
Change-Id: Id80e17466400937bba9fbb4aa2a2b65de9d62252
Add the new middleware CORS for Zaqar
It only supports for WSGI.
Websocket doesn't need this feature.
Change-Id: Ifc6d2d1c5dde5152cab6e3aa2f3cf9f207481267
Implements: blueprint support-cors
Table creation must happen outside of API requests. This changes the
devstack plugin to create the tables properly.
Change-Id: I57c4fba06dc6725ea977477b777e4ffd6856adde
The standard name for the WSGI callable is application, let's use that.
We'll keep app for compatiblity purposes.
Change-Id: I2138ef05b985dcfeba108c8a5441206b2c4ae1a7
The gate sometimes fails with "Zaqar did not start" without any way to
know what's going on. Let's remove that check and let usage of Zaqar
fails with proper error later on.
Change-Id: I04692763eb15a849541eb1903bb0fad6c16435db
KEYSTONE_CATALOG_BACKEND variable is removed from devstack[1], use
KEYSTONE_IDENTITY_BACKEND instead.
[1] https://review.openstack.org/#/c/391380
Change-Id: Id9b34af0ea1faecaeaea8a1d41a0e4b866b688af
Closes-Bug: #1644090
It's related to devstack bug bug: 1540328, where devstack install
'test-requirements' but should not do it for zaqar-ui project as
it installs Horizon from url. Remove following two 'mv' commands
when mentioned bug is fixed.
Change-Id: Ib4d0abe3b083d996556f615943d3b1185c9f882a
Takashi Kajinami
OpenStack Release Bot