This transition the Pike branch to End of Life. The last patch of the
branch will be tagged with pike-eol tag. The stable/pike branch cannot
be used anymore and will be deleted if this patch merges.
This is needed as stable/pike is not actively maintained in the recent
period and thus gates are mostly broken due to job failures. Besides,
by removing these branches, infra resources will be freed up, too.
Please try to identify any zuul job, that is defined outside of the
repositories in this patch (for example in openstack-zuul-jobs, etc.)
and won't be used anymore if stable/pike is deleted, and propose a job
removal patch for them.
Please +1 if the team is ready for us to proceed with this transition,
or -1 if there are still some activity on the branch and the team wants
to continue to maintain it.
Change-Id: I53f175106f81c3e757899ece83b3aaf037cc172a
This transition the Pike branch to End of Life. The last patch of the
branch will be tagged with pike-eol tag. The stable/pike branch cannot
be used anymore and will be deleted if this patch merges.
This is needed as stable/pike is not actively maintained in the recent
period and thus gates are mostly broken due to job failures. Besides,
by removing these branches, infra resources will be freed up, too.
Please try to identify any zuul job, that is defined outside of the
repositories in this patch (for example in openstack-zuul-jobs, etc.)
and won't be used anymore if stable/pike is deleted, and propose a job
removal patch for them.
Please +1 if the team is ready for us to proceed with this transition,
or -1 if there are still some activity on the branch and the team wants
to continue to maintain it.
Change-Id: I180be745a34994764073ed5e3746c9dcc90b7411
This transition the Pike branch to End of Life. The last patch of the
branch will be tagged with pike-eol tag. The stable/pike branch cannot
be used anymore and will be deleted if this patch merges.
This is needed as stable/pike is not actively maintained in the recent
period and thus gates are mostly broken due to job failures. Besides,
by removing these branches, infra resources will be freed up, too.
Please try to identify any zuul job, that is defined outside of the
repositories in this patch (for example in openstack-zuul-jobs, etc.)
and won't be used anymore if stable/pike is deleted, and propose a job
removal patch for them.
Please +1 if the team is ready for us to proceed with this transition,
or -1 if there are still some activity on the branch and the team wants
to continue to maintain it.
Change-Id: I5a3d03af75205dab471327ac4630bac0fdcad8b8
This transition the Pike branch to End of Life. The last patch of the
branch will be tagged with pike-eol tag. The stable/pike branch cannot
be used anymore and will be deleted if this patch merges.
This is needed as stable/pike is not actively maintained in the recent
period and thus gates are mostly broken due to job failures. Besides,
by removing these branches, infra resources will be freed up, too.
Please try to identify any zuul job, that is defined outside of the
repositories in this patch (for example in openstack-zuul-jobs, etc.)
and won't be used anymore if stable/pike is deleted, and propose a job
removal patch for them.
Please +1 if the team is ready for us to proceed with this transition,
or -1 if there are still some activity on the branch and the team wants
to continue to maintain it.
Change-Id: Iee7e7b748eb4a39afc41d2f5679d177a5a891243
This transition the Pike branch to End of Life. The last patch of the
branch will be tagged with pike-eol tag. The stable/pike branch cannot
be used anymore and will be deleted if this patch merges.
This is needed as stable/pike is not actively maintained in the recent
period and thus gates are mostly broken due to job failures. Besides,
by removing these branches, infra resources will be freed up, too.
Please try to identify any zuul job, that is defined outside of the
repositories in this patch (for example in openstack-zuul-jobs, etc.)
and won't be used anymore if stable/pike is deleted, and propose a job
removal patch for them.
Please +1 if the team is ready for us to proceed with this transition,
or -1 if there are still some activity on the branch and the team wants
to continue to maintain it.
Change-Id: Icb8d042aeaf5e83cab587ff3f60af6b0f2c275b6
This transition the Pike branch to End of Life. The last patch of the
branch will be tagged with pike-eol tag. The stable/pike branch cannot
be used anymore and will be deleted if this patch merges.
This is needed as stable/pike is not actively maintained in the recent
period and thus gates are mostly broken due to job failures. Besides,
by removing these branches, infra resources will be freed up, too.
Please try to identify any zuul job, that is defined outside of the
repositories in this patch (for example in openstack-zuul-jobs, etc.)
and won't be used anymore if stable/pike is deleted, and propose a job
removal patch for them.
Please +1 if the team is ready for us to proceed with this transition,
or -1 if there are still some activity on the branch and the team wants
to continue to maintain it.
Change-Id: I58b9f2f8e073674ac61e8604e5b5473cacfbaf3d
This transition the Pike branch to End of Life. The last patch of the
branch will be tagged with pike-eol tag. The stable/pike branch cannot
be used anymore and will be deleted if this patch merges.
This is needed as stable/pike is not actively maintained in the recent
period and thus gates are mostly broken due to job failures. Besides,
by removing these branches, infra resources will be freed up, too.
Please try to identify any zuul job, that is defined outside of the
repositories in this patch (for example in openstack-zuul-jobs, etc.)
and won't be used anymore if stable/pike is deleted, and propose a job
removal patch for them.
Please +1 if the team is ready for us to proceed with this transition,
or -1 if there are still some activity on the branch and the team wants
to continue to maintain it.
Change-Id: I6338e25979156cf69f6948863ddbce27b14cc105
This transition the Pike branch to End of Life. The last patch of the
branch will be tagged with pike-eol tag. The stable/pike branch cannot
be used anymore and will be deleted if this patch merges.
This is needed as stable/pike is not actively maintained in the recent
period and thus gates are mostly broken due to job failures. Besides,
by removing these branches, infra resources will be freed up, too.
Please try to identify any zuul job, that is defined outside of the
repositories in this patch (for example in openstack-zuul-jobs, etc.)
and won't be used anymore if stable/pike is deleted, and propose a job
removal patch for them.
Please +1 if the team is ready for us to proceed with this transition,
or -1 if there are still some activity on the branch and the team wants
to continue to maintain it.
Change-Id: I603d7ce390d5bcc864580c9feb9f6522943fb828
This transition the Pike branch to End of Life. The last patch of the
branch will be tagged with pike-eol tag. The stable/pike branch cannot
be used anymore and will be deleted if this patch merges.
This is needed as stable/pike is not actively maintained in the recent
period and thus gates are mostly broken due to job failures. Besides,
by removing these branches, infra resources will be freed up, too.
Please try to identify any zuul job, that is defined outside of the
repositories in this patch (for example in openstack-zuul-jobs, etc.)
and won't be used anymore if stable/pike is deleted, and propose a job
removal patch for them.
Please +1 if the team is ready for us to proceed with this transition,
or -1 if there are still some activity on the branch and the team wants
to continue to maintain it.
Change-Id: Ieb39b0ab55bd1d4b6ed6640ce90e2e639685c574
This release includes the following commits:
$ git log --oneline --no-merges 2.7.0..HEAD
74988cd Add traits for vIOMMU
62bb868 Add COMPUTE_MANAGED_PCI_DEVICE trait
a097c3f Add 'COMPUTE_STORAGE_VIRTIO_FS', 'COMPUTE_MEM_BACKING_FILE'
f64d50e Add nova and cyborg owner traits for resources
87b1165 Remove unnecessary unicode prefixes
1757c64 Update CI to use unversioned jobs template
Change-Id: I98e9a116f3f520d2083e0fb164c5cd39fde3188e
This release picks up new commits to ovn-octavia-provider since
the last release from stable/wallaby.
This is being proposed as a convenience to help make sure stable
changes are being released. If the team is good with this going out,
please respond with a +1 to let the release team know it is OK to
proceed.
If it is not wanted at this time, or if there are more changes that
would be good to get merged before doing a stable release, please
leave a -1 with a comment with what the team would prefer. We can
then either abandon this patch, or wait for an update with a new
commit hash to use instead.
$ git log --oneline --no-merges 1.0.0..6cfeb27
6cfeb27 Ensure members without subnet belong to VIP subnet or fail
5cf160a Fix IPv6 member delete on batch operation
b9c6239 Improve enabled_provider_drivers default in devstack
fb765e8 Delete vip port if create_vip_port raise exception
5b1d0be Apply ServiceMonitorEvent to affected LBs
1d73533 Fix way of calculate LB status after HM event
1aa4be5 Fix Load balancer remains on PENDING_CREATE
a32db16 Fix request to OVN NB DB API
9013681 Use python3-devel in bindep for rpm distros
9f0e263 Increase code coverage
0da5150 Avoid loadbalancer stuck in PENDING_X if delete_vip_port fails
5c71182 Fix deletion of members without subnet_id
6c1b8a9 Retry logical switch associations to load balancers
0fff165 Fix zuul templates for functional and tempest tests
dea57c8 Allow to create ovn loadbalancer on dual-stack provider networks
a348491 Check gateway IP while looking for LR plugged to LS
60d7b42 Add support for fullypopulated load balancers
08430b5 Support creating members without a subnet ID
f0b4408 Set listeners back to ACTIVE upon pool/member action failures
b259ebc [Stable only] Fix CI jobs
44db6c6 Fix race condition retrieving logical router rows
5469b7e Fix new pylint issues
59e09f0 Add Health Monitor support
9c362b3 Ensure that load balancer is added to logical switch
2358875 Add log for request_handler events
a1bc262 Update TOX_CONSTRAINTS_FILE for stable/wallaby
83073e3 Update .gitreview for stable/wallaby
Signed-off-by: Elod Illes <elod.illes@est.tech>
Change-Id: I84a937d97d52ffdd80aead22226f766bce8324e8
This release includes the following commits:
Changes between 0.19.0 and 58d7f8d
* 58d7f8d Fix for werkzeug 2.2 routing change
* 56e7ace Fix unit tests for Werkzeug 2.2.0
* 95ded9f novadriver, don't use instance.flavor.id
* 413a205 Replace the netboot job with a local-boot one
* c0acc3d aarch64/arm64 libvirt VMs should default to SCSI controller
* d8f0925 Remove support for Python 3.6 and 3.7
Change-Id: I13ec90355e438ef5e7c1fd931567b0fbaa6ed156
Kayobe Stein had no releases and no deliverable file and thus was
missed when other Kolla deliverables were EOLed.
The team has treated the branch as EOL.
No mail notification is being sent for this as to avoid potential
confusion.
This is done to EOL Train properly.
Change-Id: I1e213d0b9b2c6972458434b0a8f2b14303908d3b
Kayobe Rocky had no releases and no deliverable file and thus was
missed when other Kolla deliverables were EOLed.
The team has treated the branch as EOL.
No mail notification is being sent for this as to avoid potential
confusion.
This is done to EOL Train properly.
Change-Id: Ieec9eec1604efb7a4d56db680f478e3075f361c5
Kayobe Queens had no releases and no deliverable file and thus was
missed when other Kolla deliverables were EOLed.
The team has treated the branch as EOL.
No mail notification is being sent for this as to avoid potential
confusion.
This is done to EOL Train properly.
Change-Id: Id308ae74b1b63c82a2d7ec45d324465f850a5564
With the latest upper constraints updating generated patch [1] the
openstack-tox-docs job started to fail, due to conflict:
ERROR: Cannot install jsonschema<4.0.0 and >=3.2.0 because these
package versions have conflicting dependencies.
The conflict is caused by:
The user requested jsonschema<4.0.0 and >=3.2.0
The user requested (constraint) jsonschema===4.7.2
This is because we have jsonschema<4.0.0 in our requirements.txt.
By uncapping the constraint the docs job is passing.
Date validation needed to be updated as well, because a deprecated
usage of validator extending method was used in the code, which was
removed [2] from jsonschema with the 4.0.0 release. This patch replaces
that with adding a TYPE_CHECKER instead.
With the new jsonschema constraint openstack-tox-py36 job does not pass
anymore, but py36 is dropped from zed anyway. That job is pulled in by
an old job template, which needs to be replaced to the new zed job
templates, too.
[1] I89576353371aa87d181610eb6242cbe961487af6
[2] d9f6384060
Closes-Bug: #1982757
Change-Id: Ida6310dd822e587ce9c424a228fdff5192ba0476
Released changes are mostly related to requirements pins however
they fix downstream issues, so they are worth releasing.
Change-Id: I94b81c95184dd2564ebf61aff7b8940d8a0c4776
Not being released at this time:
- cinderlib (no functional changes)
- python-brick-cinderclient-ext (no functional changes)
- python-cinderclient (no functional changes)
Change-Id: I633eca33b086d4bfe2fa34b07cc37ccb3171ba4d
We merged a recent fix Ib001e2b4d1347754c2b46730bc10d86e8cdab7ad
that was not released with the recent yoga release of os-brick
5.2.1.
This issue shows up in cinder gate jobs and might potentially be
causing some tests to fail. This release will remove that failure
and possibly fix gate.
Change-Id: Idc41bf3d35dda3b68de097a8e21682ae6dd51364
This is the Zed milestone-2 release for os-brick.
Clients and libraries following the cycle-with-intermediary release
model are encouraged to release each milestone to make sure updates
are made available.
If you are happy with the current release hash, please +1 this patch
and we will process a release. If you need to get some important
changes merged first, leave a -1 and update the patch with a new
commit hash to use once it is ready.
If a release is definitely not wanted at this time, please -1 and
leave a comment explaining that and we can abandon the patch.
Any patches with no response will be assumed to be OK and will be
processed by July 14th.
Signed-off-by: Elod Illes <elod.illes@est.tech>
Change-Id: If61df2e0be59085372ae6247456b75746c41732f
This release includes a couple of bugfixes introduced in the Zed
cycle. Fixes included are:
git log --oneline --no-merges 3.4.0..cd8344c
c0d3aae Add availability zones functional tests for OSC
fcd4ade Add FIPS testing jobs
0e7d3bf [OSC] Add OSC Functional Tests Share Actions
4951255 [OSC] Implement Share Migration Cancel and Complete Command
fa84d61 [OSC] Implement Share Migration Start Command
00caf0a Fix "test_share_server_migration" sporadic failure
8f60f69 Fix test to not check service updated_at time
6786284 [OSC] Add functional tests for share access rules
b41e401 [OSC] Add functional tests for share services
9658930 Add functional tests for OSC User Messages
fdac503 [OSC] Add OSC Functional Tests Share set unset
bedefd0 Add support for --export-location filtering when listing shares
ee536bd [OSC] Add functional tests for share types
db8eafd Avoid using "force" kwarg in extend API
4e7a23b Update Python as per the Zed cycle testing runtime
4a2857a Add functional tests for "os share limits show"
cb918d3 Add functional tests for "os share pool list"
Change-Id: I2f8b04bfd262419d6030baa3cde1cebd8ad14d97
