delta/openstack/python-ironicclient.git, branch stable/queens opendev.org: openstack/python-ironicclient.git OpenDev Migration Patch 2019-04-19T19:29:53+00:00 OpenDev Sysadmins openstack-infra@lists.openstack.org 2019-04-19T19:29:53+00:00 876c132a536d7c8bf28f565d82bc28aba28735e7 This commit was bulk generated and pushed by the OpenDev sysadmins as a part of the Git hosting and code review systems migration detailed in these mailing list posts: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html Attempts have been made to correct repository namespaces and hostnames based on simple pattern matching, but it's possible some were updated incorrectly or missed entirely. Please reach out to us via the contact information listed at https://opendev.org/ with any questions you may have. 
This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:

http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html

Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.
Replace openstack.org git:// URLs with https:// 2019-03-24T20:35:51+00:00 Ian Wienand iwienand@redhat.com 2019-03-24T20:35:51+00:00 110257b4f50596ec2e2f4ac72ff038ce48a2905d This is a mechanically generated change to replace openstack.org git:// URLs with https:// equivalents. This is in aid of a planned future move of the git hosting infrastructure to a self-hosted instance of gitea (https://gitea.io), which does not support the git wire protocol at this stage. This update should result in no functional change. For more information see the thread at http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html Change-Id: I93314f6964c0a1b5c898517f7b0755b58af40859 
This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.

This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.

This update should result in no functional change.

For more information see the thread at

 http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html

Change-Id: I93314f6964c0a1b5c898517f7b0755b58af40859
Fix a LOG.warning which didn't work properly 2018-10-23T00:47:47+00:00 Kaifeng Wang kaifeng.w@gmail.com 2018-10-18T02:44:28+00:00 e945946df4b2bbd050c9f7b2ca3b8a3722b1f69b Found when checking ci logs here: http://logs.openstack.org/41/587041/3/check/ironic-inspector-tempest-dsvm-discovery/7912a3a/logs/screen-ironic-inspector.txt.gz#_Oct_17_16_44_39_477744 It's supposed to be printing missing arguments when constructing an http client. The http client is supposed to be removed ?soon?, so if the fix is not required, please let me know. Change-Id: I2bad387afa2ede56da7164a7bc9a5ac461e78d9c (cherry picked from commit a28ccb9ef8a55f96923ba4a3af12b73a91b2e448) 
Found when checking ci logs here:

http://logs.openstack.org/41/587041/3/check/ironic-inspector-tempest-dsvm-discovery/7912a3a/logs/screen-ironic-inspector.txt.gz#_Oct_17_16_44_39_477744

It's supposed to be printing missing arguments when constructing
an http client.

The http client is supposed to be removed ?soon?, so if the fix is
not required, please let me know.

Change-Id: I2bad387afa2ede56da7164a7bc9a5ac461e78d9c
(cherry picked from commit a28ccb9ef8a55f96923ba4a3af12b73a91b2e448)
import zuul job settings from project-config 2018-08-16T13:48:58+00:00 Doug Hellmann doug@doughellmann.com 2018-08-16T13:48:58+00:00 65f617311625dbdb9cc61d7d0fa98f56cdb1c5df This is a mechanically generated patch to complete step 1 of moving the zuul job settings out of project-config and into each project repository. Because there will be a separate patch on each branch, the branch specifiers for branch-specific jobs have been removed. Because this patch is generated by a script, there may be some cosmetic changes to the layout of the YAML file(s) as the contents are normalized. See the python3-first goal document for details: https://governance.openstack.org/tc/goals/stein/python3-first.html Change-Id: I5ff71b2146f1100ab790f58107265c2673c2fe8b Story: #2002586 Task: #24302 
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.

Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.

Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.

See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html

Change-Id: I5ff71b2146f1100ab790f58107265c2673c2fe8b
Story: #2002586
Task: #24302
Do not abort wait_for_provision_state of last_errors becomes non-empty 2018-06-05T13:24:57+00:00 Dmitry Tantsur divius.inside@gmail.com 2018-05-24T11:55:24+00:00 de77496644fd1f12d829717a51b0d565a4c82283 It can happen if one of heartbeats encounteres "node locked" error, which is normal, because the next heartbeat will succeed. Change-Id: Iaed9b83e199761eac4e0e2157c16ea1efa564c24 Story: #2002094 Task: #19772 (cherry picked from commit 8940d72521ea69cbb63cd813baa720c65f70b86f) 
It can happen if one of heartbeats encounteres "node locked" error, which
is normal, because the next heartbeat will succeed.

Change-Id: Iaed9b83e199761eac4e0e2157c16ea1efa564c24
Story: #2002094
Task: #19772
(cherry picked from commit 8940d72521ea69cbb63cd813baa720c65f70b86f)
Gate fix: Cap hacking to avoid gate failure 2018-05-10T11:49:25+00:00 ghanshyam gmann@ghanshyammann.com 2018-05-09T02:47:31+00:00 e944146e86aa4a796a4fe7caf6e5a702906b6268 hacking is not capped in g-r and it is in blacklist for requirement as hacking new version can break the gate jobs. Hacking can break gate jobs because of various reasons: - There might be new rule addition in hacking - Some rules becomes default from non-default - Updates in pycodestyle etc That was the main reason it was not added in g-r auto sync also. Most of the project maintained the compatible and cap the hacking version in test-requirements.txt and update to new version when project is ready. Bumping new version might need code fix also on project side depends on what new in that version. If project does not have cap the hacking version then, there is possibility of gate failure whenever new hacking version is released by QA team. Example of such failure in recent release of hacking 1.1.0 - http://lists.openstack.org/pipermail/openstack-dev/2018-May/130282.html Change-Id: I904a85633198436acbb0d4a7bba89bbe006736a2 (cherry picked from commit c6596e9f41ad3de1b3283679e41f9662eeb02864) 
hacking is not capped in g-r and it is in
blacklist for requirement as hacking new version
can break the gate jobs.

Hacking can break gate jobs because of various
reasons:
- There might be new rule addition in hacking
- Some rules becomes default from non-default
- Updates in pycodestyle etc

That was the main reason it was not added in g-r
auto sync also. Most of the project maintained the
compatible and cap the hacking version in
test-requirements.txt and update to new version when
project is ready. Bumping new version might need code
fix also on project side depends on what new in that
version.

If project does not have cap the hacking version then,
there is possibility of gate failure whenever new hacking
version is released by QA team.

Example of such failure in recent release of hacking 1.1.0
- http://lists.openstack.org/pipermail/openstack-dev/2018-May/130282.html

Change-Id: I904a85633198436acbb0d4a7bba89bbe006736a2
(cherry picked from commit c6596e9f41ad3de1b3283679e41f9662eeb02864)
Update UPPER_CONSTRAINTS_FILE for stable/queens 2018-01-26T00:28:16+00:00 OpenStack Release Bot infra-root@openstack.org 2018-01-26T00:28:16+00:00 2cf2d0e4503db5fa02c70673ee66d357692bf40c Change-Id: I8171d81f31ccd6f2b3a4a1ba2b65d553b88e347b 
Change-Id: I8171d81f31ccd6f2b3a4a1ba2b65d553b88e347b
Update .gitreview for stable/queens 2018-01-26T00:28:11+00:00 OpenStack Release Bot infra-root@openstack.org 2018-01-26T00:28:11+00:00 7c25dd524c049efc71b7bdf5bc6cd779b765cd26 Change-Id: I8a79fa44a986b0df50c799d36b21be690926a640 
Change-Id: I8a79fa44a986b0df50c799d36b21be690926a640
Merge "Add release note for fix to bug 1745099" 2018-01-25T23:28:14+00:00 Zuul zuul@review.openstack.org 2018-01-25T23:28:14+00:00 683b7c6e780f0cb4acaad34886d50e988bd3cd0c 






Add release note for fix to bug 1745099
2018-01-25T19:24:31+00:00

Ruby Loo
ruby.loo@intel.com

2018-01-25T19:17:12+00:00

80ab8a682a6b3ac667c0c98e4f44c70a93cd9a56

This adds a release note about the fix to bug 1745099.
This is a follow up to 677a4d82358ac453744716952f6227bd6534f352.

Change-Id: I452c7ee23ebd4af72f62e10c43d539b8cea62a94
Partial-Bug: #1745099





This adds a release note about the fix to bug 1745099.
This is a follow up to 677a4d82358ac453744716952f6227bd6534f352.

Change-Id: I452c7ee23ebd4af72f62e10c43d539b8cea62a94
Partial-Bug: #1745099