If a workload annotation has a key with spaces in it, filtering doesn't work

Bug #1928098 reported by Björn Tillenius
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
High
Alberto Donato

Bug Description

This with MAAS 3.0.0~rc1-9991-g.9e9a8d84b.

Create a workload annotation where the key has a space in it:

  maas $profile machine set-owner-data $systemid "my key"="my value"

Now if you go to the machine details page, you'll see that "my value" is a link that takes you to the machine listing with the following filter set:

  workload-my key:(my value)

The space in there makes it now work.

Looks like we either have to escape the spaces somehow in the UI, or restrict the keys to not contain spaces.

Related branches

Changed in maas:
milestone: none → 3.0.1
Changed in maas:
milestone: 3.0.1 → 3.0.0-rc1
Revision history for this message
Björn Tillenius (bjornt) wrote :

Note that characters like :, (, and ) also cause problem. So we probably want to restrict keys to only contain certain characters, like alphanumeric, _, ., -

Changed in maas:
importance: Undecided → High
Alberto Donato (ack)
Changed in maas:
assignee: nobody → Alberto Donato (ack)
status: New → In Progress
Changed in maas:
status: In Progress → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
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.