Bug 1391716
| Summary: | rhel-osp-director: regular expression not honored when specifying node in minor update | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Alexander Chuzhoy <sasha> |
| Component: | rhosp-director | Assignee: | Angus Thomas <athomas> |
| Status: | CLOSED NOTABUG | QA Contact: | Omri Hochman <ohochman> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 10.0 (Newton) | CC: | dbecker, jcoufal, mandreou, mburns, morazi, rhel-osp-director-maint, sasha |
| Target Milestone: | ga | ||
| Target Release: | 10.0 (Newton) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-11-08 07:03:22 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Alexander Chuzhoy
2016-11-03 20:19:40 UTC
Note the following in comment #0 on_breakpoint: [u'overcloud-compute-0', u'overcloud-controller-2', u'overcloud-controller-0'] Breakpoint reached, continue? Regexp or Enter=proceed (will clear af95276d-de2d-4320-adc6-5f270471c910), no=cancel update, C-c=quit interactive mode: overcloud-compute-0 WAITING completed: [u'overcloud-cephstorage-0', u'overcloud-controller-1'] on_breakpoint: [u'overcloud-compute-0', u'overcloud-controller-2', u'overcloud-controller-0'] Expected result: overcloud-compute-0 should be completed. Clearing the breakpoints does not dictate the order in which a node will be updated but that there will be no pause before that node is updated. So if you clear breakpoints from 3 compute nodes for example, then their update can proceed w/out user prompt and simultaneously. You cannot dictate which node will be updated next, this is randomly chosen. I don't think this is a bug. This is what I understand from below: Section 2.3 in https://access.redhat.com/documentation/en/red-hat-openstack-platform/9/paged/upgrading-red-hat-openstack-platform/chapter-2-director-based- environments-performing-updates-to-minor-versions " Press Enter to clear the breakpoint from last node on the on_breakpoint list. This begins the update for that node. You can also type a node name to clear a breakpoint on a specific node, or a regular expression to clear breakpoints on multiple nodes at once. " Seems like adjusting docs to specify correct expectations should be enough. Sasha, can you verify the behavior sync with our docs team to put together update to our documentation text? Thanks So the issue didn't reproduce and I got exactly what I expected: on_breakpoint: [u'overcloud-compute-0', u'overcloud-serviceapi-1', u'overcloud-controller-2', u'overcloud-cephstorage-0', u'overcloud-controller-1', u'overcloud-objectstorage-0', u'overcloud-controller-0', u'overcloud-serviceapi-0', u'overcloud-serviceapi-2'] Breakpoint reached, continue? Regexp or Enter=proceed (will clear f4ff235d-6607-4835-9b43-f2be407d8cfe), no=cancel update, C-c=quit interactive mode: overcloud-compute-0 WAITING completed: [u'overcloud-compute-0'] on_breakpoint: [u'overcloud-serviceapi-1', u'overcloud-controller-2', u'overcloud-cephstorage-0', u'overcloud-controller-1', u'overcloud-objectstorage-0', u'overcloud-controller-0', u'overcloud-serviceapi-0', u'overcloud-serviceapi-2'] Breakpoint reached, continue? Regexp or Enter=proceed (will clear f4ff235d-6607-4835-9b43-f2be407d8cfe), no=cancel update, C-c=quit interactive mode: overcloud-controller-2 IN_PROGRESS WAITING completed: [u'overcloud-compute-0', u'overcloud-controller-2'] on_breakpoint: [u'overcloud-serviceapi-1', u'overcloud-cephstorage-0', u'overcloud-controller-1', u'overcloud-objectstorage-0', u'overcloud-controller-0', u'overcloud-serviceapi-0', u'overcloud-serviceapi-2'] Breakpoint reached, continue? Regexp or Enter=proceed (will clear f4ff235d-6607-4835-9b43-f2be407d8cfe), no=cancel update, C-c=quit interactive mode: overcloud-objectstorage-0 WAITING completed: [u'overcloud-compute-0', u'overcloud-controller-2', u'overcloud-objectstorage-0'] on_breakpoint: [u'overcloud-serviceapi-1', u'overcloud-cephstorage-0', u'overcloud-controller-1', u'overcloud-controller-0', u'overcloud-serviceapi-0', u'overcloud-serviceapi-2'] Breakpoint reached, continue? Regexp or Enter=proceed (will clear f4ff235d-6607-4835-9b43-f2be407d8cfe), no=cancel update, C-c=quit interactive mode: overcloud-serviceapi-0 WAITING completed: [u'overcloud-compute-0', u'overcloud-controller-2', u'overcloud-objectstorage-0', u'overcloud-serviceapi-0'] on_breakpoint: [u'overcloud-controller-0', u'overcloud-controller-1', u'overcloud-cephstorage-0', u'overcloud-serviceapi-2', u'overcloud-serviceapi-1'] Breakpoint reached, continue? Regexp or Enter=proceed (will clear 11bbc3cc-4a6f-4c3a-9ca4-ec363f70cb46), no=cancel update, C-c=quit interactive mode: overcloud-cephstorage-0 WAITING completed: [u'overcloud-compute-0', u'overcloud-controller-2', u'overcloud-cephstorage-0', u'overcloud-objectstorage-0', u'overcloud-serviceapi-0'] on_breakpoint: [u'overcloud-controller-0', u'overcloud-controller-1', u'overcloud-serviceapi-2', u'overcloud-serviceapi-1'] Breakpoint reached, continue? Regexp or Enter=proceed (will clear 11bbc3cc-4a6f-4c3a-9ca4-ec363f70cb46), no=cancel update, C-c=quit interactive mode: overcloud-serviceapi-1 IN_PROGRESS WAITING completed: [u'overcloud-compute-0', u'overcloud-serviceapi-1', u'overcloud-controller-2', u'overcloud-cephstorage-0', u'overcloud-objectstorage-0', u'overcloud-serviceapi-0'] on_breakpoint: [u'overcloud-controller-0', u'overcloud-serviceapi-2', u'overcloud-controller-1'] Breakpoint reached, continue? Regexp or Enter=proceed (will clear dbb1297e-a13f-4a23-95da-4525448 thanks Sasha closing for now then as per our discussion yesterday and comment #8 |