current-tripleo RDO link is broken (bad openstack-tripleo-common package?)

Bug #1680171 reported by Dan Prince
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Expired
Undecided
Unassigned

Bug Description

Just tried to build containers off of the current-tripleo RDO link. The openstack-tripleo-common packages is missing entrypoints in the actions/baremetal.py class:

http://trunk.rdoproject.org/centos7/current-tripleo/openstack-tripleo-common-5.8.1-0.20170331213602.cca2b6f.el7.centos.noarch.rpm

This RPM does not contain the tripleo.baremetal.validate_nodes. How is this passing CI?

Dan Prince (dan-prince)
Changed in tripleo:
status: New → Triaged
importance: Undecided → Medium
milestone: none → pike-1
Revision history for this message
Alfredo Moralejo (amoralej) wrote :

Last promoted repo is https://trunk.rdoproject.org/centos7/cf/b0/cfb06558778c23f430c4da5136e084d243fe95cf_a371e2ff, which was built on 2017-04-04 01:17 .

https://review.openstack.org/#/c/408581/ which contains the mentioned change was merged on 2017-04-04 12:39PM

Newer versions are built in RDO but it needs a promotion.

Changed in tripleo:
milestone: pike-1 → pike-2
Changed in tripleo:
milestone: pike-2 → pike-3
Changed in tripleo:
milestone: pike-3 → pike-rc1
Changed in tripleo:
milestone: pike-rc1 → queens-1
Changed in tripleo:
milestone: queens-1 → queens-2
Changed in tripleo:
milestone: queens-2 → queens-3
Changed in tripleo:
milestone: queens-3 → queens-rc1
Changed in tripleo:
milestone: queens-rc1 → rocky-1
Changed in tripleo:
milestone: rocky-1 → rocky-2
Changed in tripleo:
milestone: rocky-2 → rocky-3
Changed in tripleo:
milestone: rocky-3 → rocky-rc1
Changed in tripleo:
milestone: rocky-rc1 → stein-1
Changed in tripleo:
milestone: stein-1 → stein-2
Revision history for this message
Emilien Macchi (emilienm) wrote : Cleanup EOL bug report

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

Changed in tripleo:
importance: Medium → Undecided
status: Triaged → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.