[pull] master from openstack:master#825
Merged
pull[bot] merged 9 commits intoQSLee-Net:masterfrom Oct 20, 2023
Merged
Conversation
* Update openstack-helm from branch 'master'
to 5500b2ae0b7a030eb2281fe52748c6268a2703ba
- Remove unnecessary doc locales
Change-Id: Id2f101783973dd935b41403442f1f78533d7ac73
* Update cinderlib from branch 'master'
to ab28330d859899b2b9ff1ec85904344915751e26
- Continue 2023.2 (Bobcat) development
As a cycle-with-intermediary release with trailing deliverable type,
cinderlib's master remains the 2023.2 development branch until early
in the 2024.1 (Caracal) cycle when the cinderlib 2023.2 (Bobcat)
release is made. So update tox.ini and .zuul.yaml to test against
cinder and os-brick stable/2023.2 instead of their master branches,
and restrict cinder and os-brick in requirements.txt to the 2023.2
series.
See the cinderlib docs for more info about this change:
https://docs.openstack.org/cinderlib/latest/contributor/contributing.html#cinderlib-tox-and-zuul-configuration-maintenance
Change-Id: I830b8e2f9766746a7f81b24ce1b7c1f4d4c7c5a1
* Update neutron from branch 'master'
to 5bdd0d36759fbd3b5a299a441119ae609cfc6e69
- Merge "Don't respawn a process that has been stopped"
- Don't respawn a process that has been stopped
The ``AsyncProcess`` has a watchdog process executed by
``_watch_process`` method. This method detects if the process has
been stopped and if a respawn interval is defined, the method revives
the process. However if the ``stop`` command has been triggered, the
process should not be respawned again.
Closes-Bug: #2039038
Change-Id: I3afad9346ef426960fd3e2a7480f94eae88f9de4
* Update neutron from branch 'master'
to 1d9e9e01e7d96fc04cc2d01d5cec08554870ca2b
- Merge "Add note to avoid version checks in sanity checks"
- Add note to avoid version checks in sanity checks
Change-Id: I71be7929a3ed9c0bcec350a35f054b8faddbeea7
* Update neutron from branch 'master'
to 452dd89ab02aea5595ea7e6095369dd552af96d9
- Merge "[OVN] Set the Neutron port status based on "lsp.up" and "lsp.enabled""
- [OVN] Set the Neutron port status based on "lsp.up" and "lsp.enabled"
The Neutron "port.status" field ("ACTIVE", "DOWN") is set depending on
the Logical Switch Port "up" and "enabled" flags. Before this patch,
the "port.status" depended only on the "up" flag. However, the user
can set the "port.admin_state_up" field that will modify the
"lsp.enabled" flag. If the "port.admin_state_up" is DOWN, the port
does not transmit and the status should be "DOWN".
The OVN backend is correctly disabling the port transmission; what
was incorrect in the Neutron API is only the "port.status" field.
This is currently working in other mechanism drivers like LB or OVS.
Closes-Bug: #2036705
Change-Id: I5b7b55b0b365df7246a571cea97a392cdf89bdb6
* Update charm-guide from branch 'master'
to 4160c1b470aedecf46be2ec570e66e78b1c8a880
- Document how to deploy and use Watcher
Change-Id: I8a3d4aa74e034ac1bd826904491562fff34af003
* Update nova from branch 'master'
to 67063dcfabe0b6fff51aa95a09a72c6bd1ccba3c
- Merge "Do not manage CPU0's state"
- Do not manage CPU0's state
If cpu_power_management_strategy is "cpu_state" and CPU0 is in the
dedicated set, we should just ignore it whenever we go to manage the
state. Since CPU0 cannot be powered off, but may be otherwise suitable
for the dedicated set, we can just skip it whenever we would normally
go to power it up or down.
Change-Id: I995c0953b361c7016bd77482fa2e2f276d239828
Fixes-Bug: #2038840
* Update requirements from branch 'master'
to e54dc19f590bd0ea74fd2d7ada3d0d1b3321260b
- update constraint for openstacksdk to new release 2.0.0
meta: version: 2.0.0
meta: diff-start: -
meta: series: caracal
meta: branch: master
meta: release-type: release
meta: pypi: yes
meta: first: yes
meta: release:Author: Slawek Kaplonski <skaplons@redhat.com>
meta: release:Commit: Slawek Kaplonski <skaplons@redhat.com>
meta: release:Change-Id: I0f23199eb723384d98e80b4e42d465691756d6f0
meta: release:Code-Review+2: Thierry Carrez <thierry@openstack.org>
meta: release:Code-Review+2: Elod Illes <elod.illes@est.tech>
meta: release:Workflow+1: Thierry Carrez <thierry@openstack.org>
meta: release:Code-Review+1: Artem Goncharov <artem.goncharov@gmail.com>
Change-Id: Iac601730a57732b3a65665516fe4b1e368a2a843
* Update manila from branch 'master'
to 8229f3e5c19b079edc3a7a23185e4bd8ce52d1ec
- Fix BadRequest from share-server-migration-get-progress
The share-server-migration-get-progress command was returning error
when executed immediataly after starting migration.
This patch fix all the errors related to this change.
Closes-bug: #2025075
Change-Id: Iaaf15906aa3a29543860d878cde305cfddc7f70e
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
4 participants
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.
See Commits and Changes for more details.
Created by
pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )