Document/Link to the RDO spec update process in the docs

[Julie Pichon]

Packages are built on the fly on DLRN to test incoming gerrit patches. When a new dependency is added, it also needs to be included in the spec by updating the appropriate distgit [1][2], or the patch will fail CI. This is confusing to debug and seems to only be transmitted via tribal knowledge so far. It would be good to document both the process and which CI logs to consult to get at the package building info. This could perhaps be added as a section under the developer docs at [3]?

[1] https://github.com/rdo-packages/
[2] https://review.rdoproject.org/
[3] http://tripleo.org/developer/developer.html

[Honza Pokorny (hpokorny)]

This should go into the ui-specific documentation that we're planning to write. But I agree that for now, we should add it to the developer docs as per above.

[Julie Pichon (jpichon)]

Actually this applies to the other projects as well, who also have distgits (see e.g. https://review.rdoproject.org/r/#/c/2054/ ). I agree the UI might need a special addendum for the deps stuff... perhaps let's keep bug 1651106 for that, and keep this one for the general case? Unless you're happy to write it as well, in which case go for it :)

[Julie Pichon (jpichon)]

The RDO documentation appears to live at https://www.rdoproject.org/documentation/rdo-packaging/ and makes for excellent reading. We probably still need something on our side for the dev perspective.

[Julie Pichon (jpichon)]

I just saw a somewhat related problem happen on a patch so, adding a few notes here for reference!

See https://review.openstack.org/#/c/409791/8 . Most test runs are failing, with something like that in the console log:

2016-12-20 22:39:32.467621 | 2016-12-20 22:39:32,466 ERROR:dlrn-build:cmd failed. See logs at: /opt/stack/new/delorean/data/repos/1c/07/1c07996164fe3861f73a9b4c483112b28a02be8f_7082fe70/
2016-12-20 22:39:32.468800 | 2016-12-20 22:39:32,467 INFO:dlrn:Received exception Error in build_rpm_wrapper for python-tripleoclient:

( http://logs.openstack.org/91/409791/8/check/gate-tripleo-ci-centos-7-nonha-multinode/cbdbebc/console.html#_2016-12-20_22_39_32_467621 )

This indicates some kind of issue when building the RPMs.

To debug what happened, one should go under logs/delorean_repos.tar.xz then dig down into that tarball until they find the rpmbuild.log.

In this case, we can see that the package failed to build because the unit tests are run during package building, and one failed (yet they passed on the review itself... a mystery for another day). So the package can't be built and all related CI jobs fail.

I realise this isn't related to updating dependencies per se but even if this piece of debugging doesn't make it into the docs, the logs to use to figure out if there's a dependency issue are the same, it's simply the error that will be different. build.log seems to have similar information, in a more compact way - maybe better to check there first and dig into rpmbuild.log if the error wasn't obvious in there?

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/418941

[OpenStack Infra (hudson-openstack)]

Change abandoned by Honza Pokorny (<email address hidden>) on branch: master
Review: https://review.openstack.org/418941
Reason: Merging with https://review.openstack.org/#/c/421000/

[Emilien Macchi (emilienm)]

There are no currently open reviews on this bug, changing the status back to the previous state and unassigning. If there are active reviews related to this bug, please include links in comments.

[Emilien Macchi (emilienm)]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
  Valid example: CONFIRMED FOR: FUTURE