[Update][Ceph] Health check fails with warning "too many PGs per OSD"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
Low
|
Andrey Epifanov |
Bug Description
Fuel 9.2 snapshot-id#662
!mos_mu tool was installed from git (https:/
Steps to reproduce:
- Deploy 9.0 env with following nodes:
* Controller
* Controller
* Controller
* Compute, ceph-osd
* Compute, ceph-osd
* Compute, ceph-osd
- Install mos-playbooks tool on master node (git clone https:/
- Execute preparation playbooks (ansible-playbook playbooks/
- Update fuel node (ansible-playbook playbooks/
- Update env (fuel2 update install --env 1 --repos mos9.2)
- Upgrade kernel on 4.4 for bootstrap img (ansible-playbook playbooks/
- Upgrade kernel on 4.4 (ansible-playbook playbooks/
- Update ceph (ansible-playbook playbooks/
Observed behavior:
TASK [Show health of Core OpenStack services] *******
skipping: [node-6.
ok: [node-1.
"msg": [
"### ceph:",
" cluster 07b4d8e0-
" health HEALTH_WARN",
" too many PGs per OSD (352 > max 300)",
" monmap e3: 3 mons at {node-1=
" election epoch 16, quorum 0,1,2 node-1,
" osdmap e65: 6 osds: 6 up, 6 in",
" pgmap v541: 704 pgs, 10 pools, 22052 kB data, 50 objects",
" 12591 MB used, 283 GB / 296 GB avail",
" 704 active+clean",
""
]
}
skipping: [node-5.
skipping: [node-4.
ok: [node-2.
"msg": [
"### ceph:",
" cluster 07b4d8e0-
" health HEALTH_WARN",
" too many PGs per OSD (352 > max 300)",
" monmap e3: 3 mons at {node-1=
" election epoch 16, quorum 0,1,2 node-1,
" osdmap e65: 6 osds: 6 up, 6 in",
" pgmap v541: 704 pgs, 10 pools, 22052 kB data, 50 objects",
" 12591 MB used, 283 GB / 296 GB avail",
" 704 active+clean",
""
]
}
ok: [node-3.
"msg": [
"### ceph:",
" cluster 07b4d8e0-
" health HEALTH_WARN",
" too many PGs per OSD (352 > max 300)",
" monmap e3: 3 mons at {node-1=
" election epoch 16, quorum 0,1,2 node-1,
" osdmap e65: 6 osds: 6 up, 6 in",
" pgmap v541: 704 pgs, 10 pools, 22052 kB data, 50 objects",
" 12591 MB used, 283 GB / 296 GB avail",
" 704 active+clean",
""
]
}
Changed in fuel: | |
importance: | Undecided → High |
milestone: | none → 9.2 |
As you can see it is active+clean, so it is fully operational.