Fedora 31 was retired and the image is gone from mirrors.
heat-cfntools have been dropped from fedora images, disable
the test till that's resolved.
Also makes grenade job non-voting, till this is backported
to stable/victoria.
Change-Id: Id869f83a46454897c2fe7a532eebfa2863befe5e
(cherry picked from commit 61e53c4eca)
This patch returns a stack validation error if the nova microversion
is 2.57 or greater and the personality parameter is also specified
in the templates.
Change-Id: I0919150baa36112ccbd8bfd7ccebc7aab5735cf3
Task: 41229
(cherry picked from commit b068f45add)
https://review.opendev.org/750941 changed the default
swap to 1024MB for jobs and this seems to resulting in
high failure rate of the functional and grenade jobs.
Let's configure it back to what used to before i.e 8192MB.
Change-Id: I627f2df7f6135b3d194e7146ae45c3b7f8b6394d
(cherry picked from commit f419923a0d)
Update the URL to the upper-constraints file to point to the redirect
rule on releases.openstack.org so that anyone working on this branch
will switch to the correct upper-constraints list automatically when
the requirements repository branches.
Until the requirements repository has as stable/victoria branch, tests will
continue to use the upper-constraints list on master.
Change-Id: Ie987f60222c1690fe3b180385f8ee891adea0fb1
Ceilometer uses gnocchi as the default backend. Also we use
gnocchi based aodh alarms in tests.
gnocchi seems unmaintained with last commit a year or so ago and
does not look like the openstack telemetry team is involved in
that project.
It's better to disable the services and tests in heat to avoid
broken gate like last time, where we fixed it by banning latest
pecan release[1] that does not work with python-gnocchiclient.
[1] https://review.opendev.org/#/c/746261/
Change-Id: Id2ffdf6b9d342e800bab4a94ec46742228361ee8
This patch changes the lower-constraint requirements to make them
py3.8 compatible. See https://bugs.launchpad.net/nova/+bug/1886298
Markupsafe==1.1.1
PyMySQL==0.8.0
PyYAML==3.13
cffi==1.14.0
greenlet==0.4.15
kombu==5.0.1
lxml==4.5.0
oslo.db==6.0.0
paramiko==2.7.1
psycopg2==2.8
sqlalchemy-migrate==0.13.0
tenacity==6.1.0
Also update the test-setup.sh to work with recent version of mysql.
Change-Id: Ibe60d1e536f0e887eceea32b7cb4eec6318e96af
Partial-Bug: #1886298
Parsing the value of JSON parameters at the time we create them (or
update the default value) results in exceptions occurring while creating
the Stack object, that are then not caught and transformed. The result
is an HTTP 500 Internal Error reported by the API, with an unhelpful
error message.
By not parsing the JSON until it is needed, we ensure that any errors
will occur during validation, where errors are appropriately transformed
(to StackValidationFailed) and annotated with the necessary information
to help the user determine the source.
Depends-On: https://review.opendev.org/#/c/748359/
Change-Id: I70e341c344d6254173ad4519276626230087263a
Story: 2007957
Task: 40443
Don't override ResourceStatus.ACTIONS, as it's used internally by the
Resource class.
Change-Id: Icf306e981c19e3d5410905befa7907dcdba33337
Story: 2008013
Task: 40663
The patch adding this new property was approved during the Ussuri
release cycle, but only merged in the Victoria release. Therefore the
version in the SupportStatus should be 15.0.0, not 14.0.0.
Change-Id: I1e825834049f47a470280cce6c8bd89ef7e9ae61
Without this, the QoSAssociation resource is being created without a
resource_id. This raises an Exception while peforming stack_adopt on
such resources, since adopt requires resource_id for all resources.
The proposed approach is to set uuid to QoSAssociation as well.
Change-Id: Ic4c50b36d40592e1159827376ef78eaa86c31b53
Task: #39994
Story: #39994
Supports the 'virtio-forwarder' vnic type for port sync with Neutron.
The 'virtio-forwarder' is an indirect mode for SR-IOV interfaces used to
connect the instances into the Neutron networks. It has been supported
since the Queens release:
I28315fb12f62dc7d52d099c211086b2b81eca39a
Note that 'virtio-forwarder' is already supported by Horizon:
openstack_dashboard/api/neutron.py:
('virtio-forwarder', _('Virtio Forwarder'))
Nova:
nova/network/model.py:
VNIC_TYPE_VIRTIO_FORWARDER = 'virtio-forwarder'
openstackclient:
openstackclient/network/v2/port.py:
choices=(...), virtio-forwarder
neutron-lib:
neutron_lib/api/definitions/portbindings.py
VNIC_VIRTIO_FORWARDER = 'virtio-forwarder'
Task: 40435
Change-Id: Ie65f8858d6d1a1854702eb33c40ea827505bfe51
The type of the entry point objects returned in stevedore has
been changed from`pkg_resources.EntryPoint` to
`importlib.metadata.EntryPoint`[1] and it does not have module_name
attribute.
It also bumps requirements/lower-constraints as stevedore==3.1.0 is
not backward compatible.
[1] https://review.opendev.org/#/c/740515/
Task: 40355
Change-Id: Icd68f6eab73e44406f2ff5073636dcdd111e00ea
This used to be just a list of allowed names, but now it's a dict
mapping names to types. Use variable names that reflect the current
meaning, fix the docs, and use named constants where available.
Change-Id: I3aadca4e1e9db5da5d07d521c2313162062639b7
Now context username is set from X-Auth-User header, that is not set
with session client. This results in stack_owner attribute None for
newly created stacks.
This commit sets context username from auth token in case of absent
X-Auth-User header.
Affects all releases at least since Ocata.
Story: 2007856
Change-Id: I9cba3495fd472769498486d52d3909bff03010d4
If stacks are already migrated to convergence, there is no point
in checking stack status before returning. This will allow re-run
of the command inspite of migrated stacks in FAILED state.
Change-Id: Ia0e34423377843adee8efc7f23d2c2df5dac8e20
Task: 40266
When detaching and attaching volumes nova would raise an
exception.Conflict, if attach and detach can't happen. Let's
use that to retry rather than using task_state.
Change-Id: I50904e4254568cd807b9ff18eef482cadb626ce5
Task: 40169
The mock third party library was needed for mock support in py2
runtimes. Since we now only support py36 and later, we can use the
standard lib unittest.mock module instead.
Change-Id: Ie0e43904d375e542ca00cd43b3c84c7afb31ee85
Don't use timestamp when generating ec2 signed url for alarm url
attributes of resource.
This will resolve the issue for new resources even if they are cached
in attributes or resource_data.
However, for existing stacks containing these resources the current
best option is to not cache these attributes and allow alarm resources
to be able to get a new never expiring urls in the next forced update.
Change-Id: If2ebc3deacb770294004ae023500367af603b59e
Task: 39985
Related-Bug: #1872737
As part of a CVE keystone has started checking[1] the timestamp
of signed ec2 token with default TTL of 15 mins. We can't
store the ec2 url anymore for future use for those.
This moves the caching logic to BaseWaitConditionHandle class.
[1] https://review.opendev.org/#/c/724124/
Change-Id: I6b74faed820caccd39210bd48a212b2dedca46b9
Related-Bug: #1872737
When user wants to do manual scale-up of ASG by increasing the
desired_capacity and also update some member properties as
part of a stack update, if it fails due to insufficient
resources when resizing, trying to manually scale-down by
decreasing the desired_capacity won't work, as it would
always expect to update the group with the earlier size
before scaling down.
This patch uses the target_size when building the batches.
Task: 39867
Change-Id: Id851530b424f68b5e0e967fe34431483bfffd852
Switch to openstackdocstheme 2.2.1 and reno 3.1.0 versions. Using
these versions will allow especially:
* Linking from HTML to PDF document
* Allow parallel building of documents
* Fix some rendering problems
Update Sphinx version as well.
Set openstackdocs_pdf_link to link to PDF file. Note that
the link to the published document only works on docs.openstack.org
where the PDF file is placed in the top-level html directory. The
site-preview places the PDF in a pdf directory.
Change pygments_style to 'native' since old theme version always used
'native' and the theme now respects the setting and using 'sphinx' can
lead to some strange rendering.
openstackdocstheme renames some variables, so follow the renames
before the next release removes them. A couple of variables are also
not needed anymore, remove them.
See also
http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014971.html
Change-Id: I4ebb6e663471a7096bd9d0e1a90d8114d1875546
flake8 new release 3.8.0 added new checks and gate pep8
job start failing. hacking 3.0.1 fix the pinning of flake8 to
avoid bringing in a new version with new checks.
Though it is fixed in latest hacking but 2.0 and 3.0 has cap for
flake8 as <4.0.0 which mean flake8 new version 3.9.0 can also
break the pep8 job if new check are added.
To avoid similar gate break in future, we need to bump the hacking min
version.
- http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014828.html
Change-Id: I4586bde1bd9f33dcdd803900bc648720073bdb62
Matthias Runge
David Hill
Rabi Mishra
OpenStack Release Bot
Zuul
Emilien Macchi
Zane Bitter
Jan Horstmann
Arun Vinod
Andrii Ostapenko
OpenStack Proposal Bot
Hervé Beraud
Andreas Jaeger
Luigi Toscano
Ghanshyam Mann