Update compute driver name for Ironic#1
Open
heidsoft wants to merge 7099 commits into
Open
Conversation
67fd81a to
1147300
Compare
9a6ae34 to
7a0fa4f
Compare
This variable overrides the `ENABLED_SERVICES` global variable only for the `configure_tempest()` function from `lib/tempest`. If the `SERVICES_FOR_TEMPEST` variable is not defined then `ENABLED_SERVICES` is used as it had used it before. This is useful for cases where Tempest is executed from a remote node. Change-Id: Ic62e48f2f1eb861ec64f51e03353868076cbcc04
Initially, this patch ensured that the custom configuration and readiness checks were applied after every restart of the OVN North services. However, after removing the call that triggered the restarting of the OVN/OVS services in [1], this patch now serves as a refactor, separating the readiness checks and custom configuration into a dedicated function. [1] https://review.opendev.org/c/openstack/devstack/+/937606 Related-bug: #2091614 Related-bug: #2091019 Change-Id: Icba271292830204da94aa3353e93d52088d82eec
Use a raw string to avoid SyntaxWarnings being issued by this script. Change-Id: I81557158013aa36fe27235c461486dfbc37c9f27
We also remove an out-of-date note from the called method. Change-Id: I7cc9fd6a568246342395388c31ae0a0918a2c79a Signed-off-by: Stephen Finucane <stephenfin@redhat.com> Depends-on: https://review.opendev.org/c/openstack/glance/+/932701
Change-Id: Ic2239e12306226943c645b7c439d5636f8c3df0e
In the patch [1] lib/neutron module was removed completely but it left call to the non existing currently function 'start_neutron_api' when the neutron-api service is enabled. Devstack should start neutron in the same way in case when q-svc or neutron-api service is enabled and this patch is removing that leftover call to the 'start_neutron_api' function and make it behave the same way for both service names. Additionally this patch adds service "neutron-api" to be checked when initial networks are going to be created. It is like that as just one of the services "q-svc" or "neutron-api" is enough to create those initial networks. [1] https://review.opendev.org/c/openstack/devstack/+/865014 Related-bug: #2096912 Change-Id: I1287af6a31f60b4e522f0ce3ea525e3336ffd8ba
Linux Bridge agent support was removed in the Neutron master branch in [0], let's remove any code here now as well since it will just fail. [0] https://review.opendev.org/c/openstack/neutron/+/927216 Change-Id: Idffa6579000322acfeb860189fb83a317d56bb4e
This change mirrors change Ie02734bb598d27560cf5d674c9e1d9b8dca3801f which ensure that its posible to enable vnc for vms on compute nodes without deploying the vnc proxy. In this change two new flags are added NOVA_SPICE_ENABLED and NOVA_SERIAL_ENABLED to enable configuration of the relevent console create_nova_conf is also modifed to include the db url if the console proxies are deployed on a host. As spice supprot is nolonger avaible in qemu as packged by ubuntu 24.04 and centos 9 a devstack-two-node-debian-bookworm to allow testing with spice in a multinode job. Change-Id: Ie944e518122f2b0059f28acbf68fb7ad0a560ca4
The "logger" mechanism is a testing class that is still calling monkey_patch. This mechanism driver is not relevant nor neccessary for the ML2/OVN CI jobs. Change-Id: I539b202ca81f62f4ae26b5275fd6b245d2066fe7
It may be required to troubleshoot performance related bugs during tests exection, to have ability to inspect environment processes and theirs status during test run this patch installs atop by default if not explicitly disabled. Related-Bug: #2095224 Change-Id: Iedbd61f3ce3cd2255ea5f2a7a93ba2f39ad28ff2
Swift rsync and replication services are up and running, however they fail to replicate any data if needed and if used with more than one replica. This patch removes a deprecated option setting[1] and replaces it with the required setting to use the correct rsync module suffix. Additionally it removes an outdated subdirectory suffix in the rsyncd configuration that has been removed as well[2]. Closes-Bug: #2100272 [1] https://opendev.org/openstack/swift/commit/675145ef4a131d548cc1122689732b9b65e5def4 [2] https://opendev.org/openstack/devstack/commit/0e58d22897457831b9dbf02d66a2f29d43803597 Change-Id: I5283405d00883a4dd11b7c001b1bba3776e576b8
We've LUKSv1 and LUKSv2 tests[1] in tempest that requires the ``extend_attached_encrypted_volume`` option to be True but currently there is no way to set it in devstack. This patch adds the parameter ``TEMPEST_EXTEND_ATTACHED_ENCRYPTED_VOLUME`` to enable the tests. [1] https://github.com/openstack/tempest/blob/cb03598a65f47c51406fc86c9c1503fe42424848/tempest/api/volume/admin/test_encrypted_volumes_extend.py Change-Id: Id3a3483629794ac38cb314812eeff84b677f35cd
If you specify a username, you also need to specify a domain that the user exists in. Failure to do so results in the following error: Expecting to find domain in user. The server could not comply with the request since it is either malformed or otherwise incorrect. The client is assumed to be in error. (HTTP 400)␏ This was mostly being masked for us in python-openstackclient by this little helper in osc-lib [1], but we can't rely on that for openstacksdk (and shouldn't really rely on it elsewhere either). We also deprecate the '--os-identity-api-version' and '--os-volume-api-version' options and will remove them shortly: both services only have v3 APIs nowadays. [1] https://github.com/openstack/osc-lib/blob/3.2.0/osc_lib/cli/client_config.py#L136-L147 Change-Id: I5537b0a7d58efb8a325ed61bad358f677f7a3cdf Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
We have not needed these in years. Change-Id: I4d76a7d3a8513ce5a927d533b34fb609e5dacdfa Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
There is only one volume API and one identity API, and their collective number is 3. Change-Id: Ie269817c5bb0eddd8cfcf279a46cffe4a56377b2 Signed-off-by: Stephen Finucane <stephenfin@redhat.com> Depends-on: https://review.opendev.org/c/openstack/openstacksdk/+/942898
After installation DevStack icons are not displayed. Change-Id: I1bedf97e4d2b7f13b4a0c5b98e29ac53cf502e96 Closes-Bug: #2093844
The race may happen and atop can't start due to missing logs directory. This patch pre-creates directory before starting atop process. Closes-Bug: #2100871 Change-Id: I89e3100dc86d60266913b5c5776db65e8882847c
It was deprecated in favor of the cpu_models option. Change-Id: I2cbbbf95f132b3279a24f120a7d0d756ba550542 Signed-off-by: Takashi Kajinami <kajinamit@oss.nttdata.com>
Since c0f6cb5 devstack enable debian 12 backports in bookworm. As a consequence we need to explicitly install the qemu-system-modules-spice package to keep supporting spice in qemu. The same is true for debian 13 as well. Related-Bug: #2121941 Signed-off-by: Balazs Gibizer <gibi@redhat.com> Change-Id: I05df50bb6dcf263eb387daaaf277cae1c80438b9
DevStack registers Keystone limits for image_count_total and image_count_uploading as a fixed value of 100, while GLANCE_LIMIT_IMAGE_SIZE_TOTAL is already overridable via localrc. If any Zuul jobs tries to set GLANCE_LIMIT_IMAGE_COUNT_TOTAL and GLANCE_LIMIT_IMAGE_COUNT_UPLOADING in devstack_localrc for workloads that create more than 100 images, those variables gets ignored. Add GLANCE_LIMIT_IMAGE_COUNT_TOTAL and GLANCE_LIMIT_IMAGE_COUNT_UPLOADING with the same default (100) and use them in configure_glance_quotas(). Behavior is unchanged for jobs that do not set these variables. Change-Id: Ib2f5e8287f11566179309e941d9d296869249daf Signed-off-by: PranaliD <pdeore@redhat.com>
When the ovn-bgp extension is enabled, the OVN BGP agent needs to know which OVS bridge is used for interconnecting the BGP fabric with the OVN overlay. Set the neutron-bgp-interconnect-bridge external-id on Open_vSwitch to OVS_PHYSICAL_BRIDGE, alongside the existing neutron-bgp-peer-bridges setting. Assisted-By: Claude Opus 4.6 Change-Id: Ibcfffbfcdd873e4c971fd293e351e0eb9cea72ac Signed-off-by: Eduardo Olivares <eolivare@redhat.com>
There is no need to limit clients which protocol versions to use on the provider bridges. Change-Id: I6217523193d4fa8b6bd633474d700c0f27922404 Signed-off-by: Jakub Libosvar <libosvar@redhat.com>
The noble OVN source job inherits from a removed parent job. That leaves .zuul.yaml with a reference to an undefined job and causes Zuul configuration parsing to fail when changes to the file are validated. The OVN source variant inherits directly from tempest-full-py3 and sets the noble nodeset, timeout, and swap size on the job itself. This keeps the job definition self-contained without restoring a separate platform job for the current default distro. Change-Id: I922825794c84f8cb8ef2d0ed4439e83f896d19dc Signed-off-by: Sean Mooney <work@seanmooney.info>
Tempest is installed in venv-tempest virtual environment so that it always uses the correct upper constraints, etc. On the other hand 'tempest verify-config' is called via 'venv' virtualenv, which does not exist, so tox creates it, using upper constraints from master branch (defined in [venv]deps in tox), which can cause pip install failures if there are any conflicting upper constraint on master branch and the set up requirements. To fix this, the same venv-tempest virtual environment should be used, that was set up previously in the script. Change-Id: Ifb542d6f7d937a8a2020d97c10534467dbdf0051 Signed-off-by: Elod Illes <elod.illes@est.tech>
The user was removed when support for glance-search was removed by commit 020586f . Change-Id: Ic08390933ff7a77789a534bc0e3af751f94312cc Signed-off-by: Takashi Kajinami <kajinamit@oss.nttdata.com>
Depends-On: https://review.opendev.org/c/openstack/devstack-plugin-ceph/+/951810 Change-Id: If366cd10f7858b4238c8ebfad16c129a4cb61a6a Signed-off-by: Rajat Dhasmana <rajatdhasmana@gmail.com>
This patch adds support to configure cinder replication with ceph by executing the following steps: 1. Setting replication_device config in cinder.conf 2. Setting the replication_enabled="<is> True" in ceph volume type Change-Id: Idaee83d051d496e3f9e411c19c0ea7a51bbd76bf Signed-off-by: Rajat Dhasmana <rajatdhasmana@gmail.com>
oslo_policy[enforce_scope] config option was added for the temporary transition to SRBAC and was deprecated. - https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/M72AY5ABQFXQ7XHLVEGHLBBK4XFQGVFK/ To remove it from oslo.policy, we need to remove setting of it from devstack which makes scope enforcement enabled always without providing a way to disable it. oslo_policy[enforce_new_defaults] is still there and will be used to enable/disable the new defaults (until old defaults are not removed). Needed-By: https://review.opendev.org/c/openstack/oslo.policy/+/986475 Change-Id: Ib5afc734b711dd8fa22c6c91b5083888973b2815 Signed-off-by: Ghanshyam Maan <gmaan.os14@gmail.com>
Ubuntu 26.04 (resolute) is the next Ubuntu LTS target for DevStack platform coverage. Add it to the supported distro list and define a non-voting resolute platform job so it can be exercised in check and periodic queues. Resolute uses sudo-rs, which does not support requiretty, and exposes some optional kernel tunables differently. Detect sudo-rs before writing sudoers options, make optional sysfs and sysctl tuning best-effort, and use the C locale for OVN extension sorting to keep setup portable. Disable the noVNC proxy in the resolute platform job until Nova's Python 3.14 noVNC compatibility fix is available. Depends-On: https://review.opendev.org/c/openstack/keystone/+/992782 Assisted-By: pi gpt-5.5 Change-Id: I48518a67f06e2e875bb2fc2034e1517a7e0164b0 Signed-off-by: Sean Mooney <work@seanmooney.info>
Nova has fixed Python 3.14 noVNC incompatibility, so the resolute platform job can exercise the default noVNC deployment again Depends-On: https://review.opendev.org/c/openstack/nova/+/987815 Change-Id: I5892db8e51fc01793a50d904dcd132312f30b4d3 Signed-off-by: Sean Mooney <work@seanmooney.info>
Configure the resolute platform job to run n-novnc-cell1 with OS_NOVA_DISABLE_EVENTLET_PATCHING=true. This keeps noVNC enabled with explicit threaded-mode coverage in advance of nova's default change. Change-Id: I314c001ab01767c1fb281a853135c5d13f653189 Signed-off-by: Sean Mooney <work@seanmooney.info>
The value of `KEYSTONE_ENFORCE_SCOPE` has been changed to `True` by default. This envrionment variable is used to set the values of `enforce_new_defaults` in the `[oslo_policy]` section of the keysonte configuration file. The default value for both oslo.policy options was changed to `True` in the Dalmatian (2024.2) cycle release. [1] But devstack continued to override this value by defaulting to `False`. With this change, keystone will use the same default as newer releases of oslo.policy. [1] https://docs.openstack.org/releasenotes/oslo.policy/2024.2.html Signed-off-by: Douglas Mendizábal <dmendiza@redhat.com> Change-Id: I7edce1519db4fcb38f37082ddf1aa06d440c983b Signed-off-by: Ghanshyam Maan <gmaan.os14@gmail.com>
The argparse help string contains "fe80::1%eth0" where "%e" is interpreted as a printf-style format specifier. Python 3.14 added eager validation of help strings at add_argument() time (cpython commit eb2d268ac7), causing the script to crash with "ValueError: badly formed help string" before it even parses the address. This potentially breaks all IPv6 Zuul jobs on Resolute nodes. Escape "%" as "%%" per the argparse documentation. Closes-Bug: #2158736 Change-Id: Ieda0388548d5964ec9dbc3cff52540a19e9f5625 Signed-off-by: Omer <oschwart@redhat.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Commit 08448e3 mistakenly updated the location of the Ironic compute
driver to be loaded from within the Nova tree. However, no such module
exists as the compute and scheduler drivers both live in the Ironic tree.
This reverts that and adds a note explaining the setting.
Change-Id: I7f32f77bd7e5fd1f6b41014ac71bbf6e1a7d84cf