Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1547568 - FFU: Provide a way to set up Queens/OSP13 repos during FFU
FFU: Provide a way to set up Queens/OSP13 repos during FFU
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates (Show other bugs)
13.0 (Queens)
Unspecified Unspecified
urgent Severity urgent
: beta
: 13.0 (Queens)
Assigned To: Sofer Athlan-Guyot
Marius Cornea
: Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2018-02-21 09:48 EST by Marius Cornea
Modified: 2018-06-27 09:46 EDT (History)
8 users (show)

See Also:
Fixed In Version: openstack-tripleo-heat-templates-8.0.0-0.20180326192239.e59fd2c.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-06-27 09:45:38 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
mbracho: needinfo+


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
OpenStack gerrit 553826 None stable/queens: MERGED tripleo-heat-templates: FFU: Introduce post FFU steps and use them for qeens switch (I649afc6fa384ae21edc5bc917f8bb58635... 2018-03-22 13:01 EDT
Red Hat Product Errata RHEA-2018:2086 None None None 2018-06-27 09:46 EDT

  None (edit)
Description Marius Cornea 2018-02-21 09:48:42 EST
Description of problem:
Currently the Queens/OSP13 repos setup is done by manually running the repo setup command on the overcloud nodes before running the upgrade_steps_playbook.yaml  playbook. We need a way to set the repos via director to avoid any overcloud nodes manual intervention.
Comment 9 errata-xmlrpc 2018-06-27 09:45:38 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2018:2086

Note You need to log in before you can comment on or make changes to this bug.