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
The default value of domain caused the user to be unable to create
role which no domain.
The patch delete the default value of domain.
Change-Id: Ic67b22c435e29f67bafa8e14ab502ebec5b07ec5
Story: 2002671
Task: 22488
Useing get_attr, pulling index 0 in the segments list
of a network to associate the a subnet with the "first"
segment is useful since the "first" segment is created
by neutron behind the scenes on network create. A resource
reference cannot be used since the "first" segment is'nt
a heat resource.
The issue is the order of the segments list is'nt reliable.
On stack update index 0 may be a different segment, and
we end up trying to update the segment_id for a subnet.
Changeing the segment association is not allowed, so
the stack update fails.
While not perfect, sorting the list so that segments where
name is None comes first will ensure that index 0 can be used.
The template author should ensure segments defined in the heat
template all have a names set, so that only the segment creted
implicitly by neutron have 'None' name.
Closes-Bug: #1894920
Change-Id: I097aba2a97144327bec188e6c71629d0f6c95901
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
