Bug 2005221
| Summary: | Cluster compatibility version upgrade from 4.5 to 4.6 | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Lorenzo Sartoratti <lorenzo.sartoratti> | ||||||||
| Component: | Database.Core | Assignee: | Martin Perina <mperina> | ||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Guilherme Santos <gdeolive> | ||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | urgent | ||||||||||
| Version: | 4.4.8.5 | CC: | ahadas, arusakov, bugs, ffutigam, michal.skrivanek, mkalinin, mperina | ||||||||
| Target Milestone: | ovirt-4.4.8-2 | Keywords: | ZStream | ||||||||
| Target Release: | 4.4.8.6 | Flags: | mperina:
ovirt-4.4+
|
||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | ovirt-engine 4.4.8.6 | Doc Type: | Release Note | ||||||||
| Doc Text: |
When oVirt engine is upgraded to 4.4.8 and a user is upgrading a cluster, then VMs time zones are removed and reset to default (UTC). This change is fixing the upgrade script, so users which haven't yet upgraded to 4.4.8 won't be affected by this issue.
|
Story Points: | --- | ||||||||
| Clone Of: | |||||||||||
| : | 2006284 (view as bug list) | Environment: | |||||||||
| Last Closed: | 2021-09-24 09:20:53 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Bug Depends On: | |||||||||||
| Bug Blocks: | 2006284 | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Lorenzo Sartoratti
2021-09-17 07:32:07 UTC
The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again. Could you please provide complete logs from your engine machine gathered by sos-logcollector? Hi, could you be more specific in the files to provide? sos-collector collects too much information and even through the clean function I cannot check all sensitive information. Thanks Lorenzo (In reply to Lorenzo Sartoratti from comment #3) > Hi, > could you be more specific in the files to provide? sos-collector collects > too much information and even through the clean function I cannot check all > sensitive information. > Thanks > > Lorenzo We ask for sos-logcollector, because then we can investigate thoroughly what happened. If you don't want to share all logs, then please share engine.log and server.log and let's see what we can find. Thanks Created attachment 1823917 [details]
engine.log
Hi,
steps done:
logrotate -f
launched compatibility update
server.log is an empty file
engine.log non empty file (attaching)
Lorenzo
Please don't use logrotate to rotate logs file generated by WildFly (server.log/engine.log/ui.log under /var/log/ovirt-engine). Doing that you might loose logged data and even WildFly might not work correctly. To fix that issue I suggest to restart ovirt-engine service. So anyway if you have any older engine.log files, could you please share them? *** Bug 2000770 has been marked as a duplicate of this bug. *** Created attachment 1825211 [details]
new engine log
this is reverting every VM's TZ to "null" on upgrade (package upgrade) to 4.4.8. As a side effect it breaks cluster level update of HE cluster due to timezone field not being updateable, for regular VMs there is just a WARN in logs. Shipped async: https://lists.ovirt.org/archives/list/announce@ovirt.org/thread/QBFVCEXUCBH6UIPFKHTKK7PLSPJ5OQWE/ *** Bug 2000770 has been marked as a duplicate of this bug. *** Still got same problem Curently on 4.4.8.6-1.el8 please check fresh engine log Created attachment 1830635 [details]
engine log on 4.4.8.6-1.el8
|