ceph-radosgw/config.yaml fails lint

Bug #1747002 reported by Tilman Baumann
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ceph-radosgw (Juju Charms Collection)
Fix Committed
Low
Unassigned

Bug Description

$ yamllint config.yaml
config.yaml
  1:1 warning missing document start "---" (document-start)
  63:14 warning truthy value is not quoted (truthy)
  85:14 warning truthy value is not quoted (truthy)
  145:14 warning truthy value is not quoted (truthy)
  150:14 warning truthy value is not quoted (truthy)
  279:3 error duplication of key "haproxy-server-timeout" in mapping (key-duplicates)
  285:3 error duplication of key "haproxy-client-timeout" in mapping (key-duplicates)
  291:3 error duplication of key "haproxy-queue-timeout" in mapping (key-duplicates)
  297:3 error duplication of key "haproxy-connect-timeout" in mapping (key-duplicates)
  323:1 error too many blank lines (1 > 0) (empty-lines)

Somehow the haproxy-* keys got duplicated.

I have a fix for it which I will try to feed through gerrit...

Tags: 4010
Revision history for this message
Tilman Baumann (tilmanbaumann) wrote :
tags: added: 4010
Revision history for this message
Corey Bryant (corey.bryant) wrote :

Note, the config duplicates are exact duplicates, so no change in behavior expected if they're removed.

Changed in ceph-radosgw (Juju Charms Collection):
status: New → Triaged
importance: Undecided → Low
Revision history for this message
Corey Bryant (corey.bryant) wrote :

Seems like perhaps we should start running yamllint as part of tox. We could propose a change for that and see what others think.

Revision history for this message
Tilman Baumann (tilmanbaumann) wrote :

I think that would be a good test.
YAML files are easily broken by accident since they are sensitive to hidden whitespace mismatches. (python legacy)
Happens easily when you edit a file.

Revision history for this message
Corey Bryant (corey.bryant) wrote :
Changed in ceph-radosgw (Juju Charms Collection):
status: Triaged → Fix Committed
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.