Bug 1457259
Summary: | [OSP 9] Packstack fails to deploy with an error during Puppet run. | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Jason Joyce <jjoyce> |
Component: | openstack-packstack | Assignee: | Alfredo Moralejo <amoralej> |
Status: | CLOSED ERRATA | QA Contact: | nlevinki <nlevinki> |
Severity: | urgent | Docs Contact: | |
Priority: | high | ||
Version: | 9.0 (Mitaka) | CC: | amoralej, aortega, apevec, mburns, srevivo |
Target Milestone: | --- | Keywords: | Rebase, Triaged, ZStream |
Target Release: | 9.0 (Mitaka) | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | openstack-packstack-8.0.3-1.el7ost.src.rpm | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-06-19 14:49:23 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jason Joyce
2017-05-31 12:24:43 UTC
This bugzilla has been removed from the release and needs to be reviewed and Triaged for another Target Release. This was with openstack-puppet-modules-8.1.13-2.el7ost * Wed May 10 2017 Alex Schultz <aschultz> 1:8.1.13-2 - Add support for migration over SSH (rhbz#1449324) which updated puppet-nova, so we need backport of Adjust live migration config to changes in puppet-nova https://review.openstack.org/#/q/I43e3a2171981886da5e6c779fd24510540a7c07a,n,z I'm getting following error running nova manifest with proposed patch: Error: Could not apply complete catalog: Found 1 dependency cycle: (File_line[/etc/libvirt/libvirtd.conf auth_tcp] => Service[libvirt] => Class[Nova::Compute::Libvirt] => Class[Nova::Migration::Libvirt] => File_line[/etc/libvirt/libvirtd.conf auth_tcp]) I'm still investigating it. CI for packstack is passing, marking verified 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/RHBA-2017:1501 |