RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1175726 - Disabling glance deployment does not work if you don't disable demo provisioning
Summary: Disabling glance deployment does not work if you don't disable demo provisioning
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RDO
Classification: Community
Component: openstack-packstack
Version: Juno
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: Juno
Assignee: Martin Magr
QA Contact: yeylon@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-18 13:36 UTC by Antoni Segura Puimedon
Modified: 2016-04-18 06:49 UTC (History)
6 users (show)

Fixed In Version: openstack-packstack-2014.2-0.13.dev1395.gaabe0a2.fc22
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-30 23:02:49 UTC
Embargoed:


Attachments (Terms of Use)

Description Antoni Segura Puimedon 2014-12-18 13:36:46 UTC
Description of problem:
When installing without nova, glance, swift, heat, cinder, horizon and
celiometer, packstack should not try to deploy anything that requires any of
those services.


Version-Release number of selected component (if applicable):
openstack-packstack-2014.1.1-0.31.1.dev1266.el7.centos.noarch

How reproducible:
100%


Steps to Reproduce:
1. sudo packstack --install-hosts=$IP \
 --nagios-install=n \
 --os-ceilometer-install=n \
 --os-cinder-install=n \
 --os-glance-install=n \
 --os-heat-install=n \
 --os-horizon-install=n \
 --os-nova-install=n \
 --os-swift-install=n \
 --provision-demo=n

Actual results:

    192.168.123.31_provision_glance.pp:               [ ERROR ]                   
    Applying Puppet manifests                         [ ERROR ]

    ERROR : Error appeared during Puppet run: 192.168.123.31_provision_glance.pp
    Error: Could not prefetch glance_image provider 'glance': File: /etc/glance/glance-api.conf does not contain all required sections

Expected results:
Deployment succeeds


Additional info:
disabling provision-demo works around the issue.


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