OpenStack Designate-Bind Charm

designate-bind missing source config option

Bug #1631559 reported by Ryan Beisner on 2016-10-08

This bug affects 1 person

	Status	Importance	Assigned to
OpenStack Barbican Charm	Invalid	Undecided	Unassigned
OpenStack Barbican SoftHSM Charm	Invalid	Undecided	Unassigned
OpenStack Designate Charm	Invalid	Undecided	Unassigned
OpenStack Designate-Bind Charm	Triaged	Medium	Unassigned

Bug Description

The designate-bind charm is missing source and/or openstack-origin config options.

Those tests currently fail like so:

# Designate charm tests:
DEBUG:runner:2016-10-08 00:10:25 Invalid config charm /tmp/charmixqybl/trusty/designate-bind openstack-origin=cloud:trusty-mitaka

# Barbican charm tests:
DEBUG:runner:2016-10-08 03:43:26 Invalid config charm /tmp/charm9FB_tE/xenial/barbican-softhsm openstack-origin=cloud:xenial-newton

Logs and the built charm artifact are available here:
https://openstack-ci-reports.ubuntu.com/artifacts/test_charm_pipeline_amulet_full/openstack/charm-designate-bind/375018/9/154/index.html

I've also attached the complete config.yaml and build manifest from the built charm to this bug.

See original description

Revision history for this message

Ryan Beisner (1chb1n) wrote on 2016-10-08:

config.yaml Edit (729 bytes, text/plain)

Revision history for this message

Ryan Beisner (1chb1n) wrote on 2016-10-08:

.build.manifest Edit (14.1 KiB, text/cache-manifest)

summary:

- designate and designate-bind are missing source and/or openstack-origin
- config options
+ missing source and/or openstack-origin config option(s)

Ryan Beisner (1chb1n) on 2016-10-08

description:

updated

Revision history for this message

Ryan Beisner (1chb1n) wrote on 2016-10-10: Re: missing source and/or openstack-origin config option(s)

barbican-softhsm is a subordinate, no source or openstack-origin expected there.

Changed in charm-barbican-softhsm:
status:	New → Invalid
Changed in charm-designate:
status:	New → Invalid

Revision history for this message

Ryan Beisner (1chb1n) wrote on 2016-10-10:

designate does have openstack-origin

Changed in charm-barbican:
status:	New → Invalid

Revision history for this message

Ryan Beisner (1chb1n) wrote on 2016-10-10:

barbican does have openstack-origin

description:

updated

Ryan Beisner (1chb1n) on 2016-10-12

Changed in charm-barbican-softhsm:
status:	Invalid → New

Revision history for this message

Liam Young (gnuoy) wrote on 2016-10-12:

Desiginate bind just deploys bind and has interfaces that work with the designate charm. No part of the charm comes from OpenStack or is anyway tied to Openstack code names.

Changed in charm-designate-bind:
status:	New → Invalid

Liam Young (gnuoy) on 2016-10-12

Changed in charm-designate-bind:
status:	Invalid → Confirmed

Revision history for this message

James Page (james-page) wrote on 2016-12-12:

barbican-softhsm is a suboridinate charm - no source/openstack-origin applies.

Changed in charm-barbican-softhsm:
status:	New → Invalid
Changed in charm-designate-bind:
status:	Confirmed → Triaged
importance:	Undecided → Medium

Corey Bryant (corey.bryant) on 2017-03-30

summary:

- missing source and/or openstack-origin config option(s)
+ designate-bind missing source config option

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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