Bug #10297
closed
I'm not sure how that's possible. All objects in an erasure coded pool (3.59s0 shard shows it is one because of the trailing s0) are supposed to have hinfo_key attributes. Could this come from a newly added tests that is over zealous ?
description: upgrade:firefly-x/stress-split-erasure-code/{0-cluster/start.yaml 1-firefly-install/firefly.yaml
2-partial-upgrade/firsthalf.yaml 3-thrash/default.yaml 4-mon/mona.yaml 5-workload/ec-rados-default.yaml
6-next-mon/monb.yaml 8-next-mon/monc.yaml 9-workload/ec-rados-plugin=jerasure-k=3-m=1.yaml
distros/ubuntu_12.04.yaml}
Loic Dachary wrote:
I'm not sure how that's possible. All objects in an erasure coded pool (3.59s0 shard shows it is one because of the trailing s0) are supposed to have hinfo_key attributes. Could this come from a newly added tests that is over zealous ?
This suite is new in part that it runs all workloads in parallel with upgrade.
Actually, the problem is likely that the hinfo_key was missing on whatever osd ended up as the "authoritative" osd. So, it's not an extra attr, it's a missing attr.
- Priority changed from Normal to Urgent
- Subject changed from "extra attr hinfo_key" error in upgrade:firefly-x-next-distro-basic-multi run to missing attr hinfo, error: "extra attr hinfo_key" error in upgrade:firefly-x-next-distro-basic-multi run
- Assignee set to Loïc Dachary
- Assignee deleted (
Loïc Dachary)
- Regression set to No
- Status changed from New to Resolved
bdc664fb3d2d363ca55b0761c9054294315f054f
- Status changed from Resolved to Duplicate
Also available in: Atom
PDF