Add ReNo support to manage release notes.
http://docs.openstack.org/developer/reno/
We'll start using it during Ocata.
Change-Id: Ie8945b6da8c37d5d4e7bc5a09f0d6f75ede9f58f
Currently we hit an issue in update and upgrade, when heatclieant
try to process the templates and failed because there was some
missing unrendered template files, ie : post.j2.yaml
Co-Authored-By: Steven Hardy <shardy@redhat.com>
Change-Id: If95825e7df5d2c0e6cbe3575d06d57db1e8182da
Closes-Bug: #1624727
This command talks to glance, and as such it does in fact require
authentication details. With auth_required set to false, osc-lib
doesn't populate the auth details of the glance client which causes
the attached bug.
Change-Id: Ib7a28587a09e16819aad62d9ec123a286fd5c6a8
Closes-Bug: 1630743
To avoid pushing an artificial alpha tag, following PBR semver keyword
bumps major version. See http://docs.openstack.org/developer/pbr/#version
Change-Id: I23e7b43569b7aefddedcd11ea6ce2d2730b9aa0e
Sem-Ver: api-break
Allows users to optionally pass -r roles_data.yaml to override the
default file in the plan.
Note this is the first step, a similar interface needs to be added
to the overcloud plan create command but this may require rework
of the default plan creation workflow (or some way to re-trigger
the j2 templating after modifying the roles data).
Change-Id: I5c6e22fe9516c4e2dad4495127d923f971c32f5d
Partial-Bug: #1626955
When sourcing the Keystone RC file, some of the variable options are
conflicting, and may provide the wrong information to a token request.
For example, If both OS_USERNAME and OS_USER_ID are passed, the
Keystone Client has to chose which one to add to the token request,
and it might not be the one the user expects. The same is true for
any value that can be passed both by name and ID. In addition, some
of the combinations lead to cryptic error messages.
To clearly identify the users intention, the old environment is
cleared of all variables that start with the `OS_` prefix
before setting any new variables.
Change-Id: I6badc5864426a371323a59100155e1c284af84b8
For a while now the recommended approach for managing parameters has
been with a Heat environment file that is passed into the deploy
command. However, there are a number of CLI args that still map directly
to parameters. This change marks them as deprecated and includes
direction for users in the help message.
They can then be removed in a later release.
Change-Id: I583521c5c72a5377e9ee3047376c0f7bcf5fbdf6
While working on upgrade Mitaka to newton we hit this issue
https://bugs.launchpad.net/tripleo/+bug/1626422
It appear that the keystone credentials needs to be generated
and store with the overcloud password only once
Change-Id: I15888f31c6b275ac785107bb95256296fd67487f
Closes-Bug: #1626422
The action result was not properly checked, leading to errors being
missed and the plan creation failing, sometimes silently.
Change-Id: I8c5391be5ff7bc4c7227ebbe4f8200eda6f8de09
Closes-Bug: #1621493
This change fixes the tripleoclient tests, which were broken
by an update in heatclient.
Previously it mocked something that was called by heatclient,
this is out of our control so we can't tell when the logic
changes. This patch updates the test to mock at our bounardy
which is the call to heatclient.
Change-Id: I0b959560ee7df194ec0f4a2b8a1605666fdec551
Swiftclient is logging a 404 when looking for
overcloud-without-mergepy.yaml. To stop this, disable logging
below the critical level for swiftclient. Note that we catch the
resulting exception from swiftclient and log it ourselves if
necessary, so there's no loss of information in the legitimate
error case.
Change-Id: I24144f3ab2b63c4a0f5fc2c9271e4a51a9ea1353
Closes-Bug: 1626267
This was previously changed by mistake in a bad merge which
caused th CLI to always call the create plan workflow.
See: I9d77880e82ec429a2ea340df87c89055a09e9720
Partial-Bug: #1622683
Change-Id: I8967b8badfeee1ba9ad473171103c7c37d6f7209
overcloud-without-mergepy.yaml file is removed in the
as part of bug #1619786. Removing its reference in the
client too.
Change-Id: Icaaec4190681f2d0f3c4ab6efc6b7f073372aed1
These were renamed in a previous commit, once the usages here
have been updated they can be removed.
Partial-Bug: #1625641
Depends-On: I247747c7d641a70f320faf109c15745d00d62ff3
Change-Id: I3f5f63751503ece0db9d703f28e9720011e81a1b
If you don't use the absolute path then the logic in
_process_and_upload_environment breaks and deployment fails
We probably need a more comprehensive fix but this provides a
stopgap solution while we figure out how to rework this.
Change-Id: I9c6a7394d1f831ab7f0b774f675f77f924fea335
Partial-Bug: #1623552
Because 'provide' calls to other workflows, the error message that
surfaces back can be quite difficult to parse. This attempts to make
the message more readable.
Change-Id: Iae3f29e5da25177fdee45752410f92b064c874c3
Depends-On: I8da43e4ff76488fc5cdb7bd2efa0cf9c39e7bb5e
Closes-Bug: #1620949
When the new filesa re re-created the environments will be re-added
based on the capabilities map and the users choices.
Partial-Bug: #1622683
Depends-On: Ia014d85d7e601d436ae9267df5988f4a6e962574
Change-Id: I1e1d6634663bf38fd21cb5f10f1422294321c5aa
Emilien Macchi