| Summary: | [RFE] Provide a simple way to track update/upgrade state | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Udi Shkalim <ushkalim> |
| Component: | RFEs | Assignee: | OSP Team <rhos-maint> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 8.0 (Liberty) | CC: | ccamacho, grosenbe, jbadiapa, jfrancoa, jpretori, lbezdick, mandreou, markmc, mbollo, mbracho, mbultel, mburns, morazi, sathlang, srevivo |
| Target Milestone: | --- | Keywords: | FutureFeature, Reopened, Triaged, UserExperience |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-12-21 10:39:21 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: | |
|
Description
Udi Shkalim
2016-04-11 12:54:06 UTC
Hi Udi, So to make this clear, you're looking for automation of each section in the manual: https://access.redhat.com/documentation/en/red-hat-openstack-platform/8/paged/upgrading-red-hat-openstack-platform/chapter-3-director-based-environments-performing-upgrades-to-major-versions It would be like a "script" that automate the whole process. Is that what you're after ? Regards, Hi Udi, This is very old, I'm going to close this one, but don't hesitate to re-open it if it's still relevant. Regards, Hi Sofer, Sorry for the late response, I usually track bug that are in need_info on me. I'll appreciate the use of that flag next time. Not sure if it is more of an RFE then a bug. Not exactly automation script or anything like that. More of a tracking system. When you run the upgrade commands/script there is no indication from the openstack side (heat/undercloud/overcloud) what steps passed or what failed. For example you have a automated script that run the whole upgrade steps and you run it and after certain time it fail I cannot find anywhere in the system when it failed(without starting a debugging session). Another example, say I'm running the upgrade manually, and the undercloud upgrade passed but the overcloud deploy command failed. A day passes or few hours and another engineer is looking on the setup and he needs to re-trace all my steps and making sure that they passed and so on... instead of running: $ overcloud upgrade status Step1...: passed Step2...: finished with error Step3...: pending step 2 Hope I was able to explain myself better here. Feel free to ping me on IRC or shoot me an e-mail. Thanks, Udi Hi Udi, make sense, and sounds like a good idea. Asking PM for decision on this one. Thanks, Marking as FutureFeature, we will review priority for next release planning. Checked today in the triaged session, we will discuss it with PM. Hello Udi, This Bugzilla is really old already and I believe that it has been taken into account into the current upgrades workflow. When upgrading in Stein, the upgrade tasks will show the step they belong to and you can even re-run the upgrade for a specific step thanks to the Ansible tags. Is it ok if we close the bug then? Thanks for your understanding. I think we could do something easily to address this RFE. I can propose a PoC and see what TripleO folks think about it. (In reply to Jose Luis Franco from comment #10) > Hello Udi, > > This Bugzilla is really old already and I believe that it has been taken > into account into the current upgrades workflow. When upgrading in Stein, > the upgrade tasks will show the step they belong to and you can even re-run > the upgrade for a specific step thanks to the Ansible tags. > > Is it ok if we close the bug then? > > Thanks for your understanding. Hi Jose, Should we wait for comment #11 POC? In any chance it is covered we can go ahead and close it. If you think we can improve the current process it will be even better. Thanks a lot! Udi @Udi, @mathieu, Sure, if you could do some POC for the RFE would be great. I just thought that the RFE was more the less addressed by the use of ansible where we specify the task we're running and provide with more transparency. I understand that in OSP7/8 this was quite of an achievement because of heat, but I believe this has improved quite a lot. Anyway, let's wait for @mathieu to finish the POC. If we can close the BZ with an improvement it's even better. Hey, I have attached the PoC review to this BZ, for now it's WIP. So maybe you will be able to apply the patch and test it when it will be ready. I don't think that required a lot of code and hours. It should be addressed quickly. Hi, You can test the review: https://review.opendev.org/702873 It's implemented for: openstack overcloud upgrade prepare and then you can get the status by: openstack overcloud upgrade status I'm going to implement every steps, but I need to rework a little the code. As Jesse commented, this BZ was filed pre-Ansible. Currently the logs has improved a lot. If you think the logs need to improve and are not good enough, do not hesitate to re-open the BZ. |