schema for AWS::AutoScaling::AutoScalingGroup's VPCZoneIdentifier should say length=1

Bug #1294717 reported by Mike Spreitzer
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Heat
Fix Released
Medium
Mike Spreitzer

Bug Description

Only the first member of the list is used.

Revision history for this message
Mike Spreitzer (mike-spreitzer) wrote :

Fix by adding
            constraints=[
                constraints.Length(min=1, max=1)
            ]
to the schema for that property.

Revision history for this message
Mike Spreitzer (mike-spreitzer) wrote :

Might as well fix up the description too.

Revision history for this message
Mike Spreitzer (mike-spreitzer) wrote :

Here is what I suggest:

        VPCZONE_IDENTIFIER: properties.Schema(
            properties.Schema.LIST,
            _('Use only with Neutron.'),
            constraints=[
                constraints.Length(min=1, max=1)
            ],
            schema=properties.Schema(
                properties.Schema.STRING,
                _('UUID of the internal subnet to which the instance will be attached.')
            )
        ),

Revision history for this message
Steve Baker (steve-stevebaker) wrote :

I'm very happy to have this property better documented. Could you please submit this change to gerrit?

Changed in heat:
status: New → Triaged
importance: Undecided → Medium
milestone: none → icehouse-rc1
Changed in heat:
assignee: nobody → Mike Spreitzer (mike-spreitzer)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to heat (master)

Fix proposed to branch: master
Review: https://review.openstack.org/81605

Changed in heat:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Fix proposed to branch: master
Review: https://review.openstack.org/81638

Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Fix proposed to branch: master
Review: https://review.openstack.org/81727

Revision history for this message
Pavlo Shchelokovskyy (pshchelo) wrote :

could you abandon the first two not to confuse reviewers? looks like you are just getting used to Gerrit workflow :)

Revision history for this message
Mike Spreitzer (mike-spreitzer) wrote :

Done. I have gotten this right before, but don't remember an important detail now.
When I commit the second patch set, do I keep the change ID from the first or omit a change ID
in the commit message?

Revision history for this message
Pavlo Shchelokovskyy (pshchelo) wrote :

when you change your patch set you commit with --amend, so that there is always only one commit on you branch and do not change/remove Change-Id while you edit the commit message - Change-Id is what identifies a patch-set to Gerrit, so that commits with the same Change-Id are treated as belonging to one evolving patch-set. If you remove Change-Id from the commit message, git review hook will still insert one, but this time different.

Good read: https://wiki.openstack.org/wiki/GerritWorkflow

Changed in heat:
milestone: icehouse-rc1 → next
Changed in heat:
milestone: next → juno-1
tags: added: icehouse-rc-potential
tags: removed: icehouse-rc-potential
Revision history for this message
Openstack Gerrit (openstack-gerrit) wrote : Fix merged to heat (master)

Reviewed: https://review.openstack.org/81727
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=8902c6e331f2d5f6c4b764d5674c2789439896b9
Submitter: Jenkins
Branch: master

commit 8902c6e331f2d5f6c4b764d5674c2789439896b9
Author: Mike Spreitzer <email address hidden>
Date: Wed Mar 19 19:25:46 2014 +0000

    Refined schema for VPCZoneIdentifier

    The schema now says it is a list of strings. Also upgraded the
    description. Also clarified the name of
    test_invalid_vpc_zone_identifier.

    Change-Id: I4b17dbd146965df3df3f4205dddafc0b65061294
    Closes-Bug: #1294717

Changed in heat:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in heat:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in heat:
milestone: juno-1 → 2014.2
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.