external_ids cannot be set on interfaces

Bug #1961643 reported by deadalnix
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
puppet-vswitch
In Progress
Wishlist
Unassigned

Bug Description

As the title says.

This cannot set external ids on interfaces, and this is a bit unfortunate.

Revision history for this message
Takashi Kajinami (kajinamit) wrote (last edit ):

Could you please elaborate the configuration you want to achieve ?

AFAIK ovs supports setting external ids to only ovs bridges. If you expect the similar functionality for vs_port then that is not possible unless the feature is implemented in ovs (or I'm wrong).

Changed in puppet-vswitch:
status: New → Incomplete
Revision history for this message
Takashi Kajinami (kajinamit) wrote :

I was looking at only interface of the ovs-vsctl command but it seems the external ids column actually exists in interface level.

I think we can add the external_ids property to vs_port so that users can customize the property.

Changed in puppet-vswitch:
status: Incomplete → Triaged
importance: Undecided → Wishlist
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to puppet-vswitch (master)
Changed in puppet-vswitch:
status: Triaged → In Progress
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.