Bug 1839676
Summary: | Run engine-setup with answerfile fails on "rollback failed: cannot use a string pattern on a bytes-like object" | ||||||
---|---|---|---|---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Ilan Zuckerman <izuckerm> | ||||
Component: | Setup.EngineCommon | Assignee: | Yedidyah Bar David <didi> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Petr Matyáš <pmatyas> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | high | ||||||
Version: | 4.4.1 | CC: | bugs, didi, michal.skrivanek, mtessun | ||||
Target Milestone: | ovirt-4.4.1 | Flags: | pm-rhel:
ovirt-4.4+
mtessun: planning_ack+ sbonazzo: devel_ack+ lleistne: testing_ack+ |
||||
Target Release: | 4.4.1.2 | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | ovirt-engine-4.4.1.2 | Doc Type: | No Doc Update | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2020-07-08 08:24:44 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | Integration | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Ilan Zuckerman
2020-05-25 08:46:16 UTC
Are there some reproduction steps? Otherwise this will be sanity only. The reproduction steps are generally to make engine-setup fail after it already updated the database (perhaps preferably both engine and dwh DBs) - after 'Creating/refreshing * database schema' - and see that it rolls back correctly. Manually, you can do this simply by pressing Ctrl-C at the right time. Automatically, you can do something like: - install, setup and backup a 4.3 engine+dwh (no need to be done specifically for this flow, btw - you can take a backup done elsewhere) - Install 4.4 engine+dwh, and: otopi-debug-plugins - Restore the backup from first step - Run: OTOPI_FORCE_FAIL_STAGE=STAGE_MISC OTOPI_FORCE_FAIL_PRIORITY=PRIORITY_LAST engine-setup --offline --accept-defaults Alternatively, for verifying just current bug (and not real 4.3->4.4 upgrade), you can upgrade to same version: - install, setup and backup engine+dwh - engine-cleanup. To automate: engine-cleanup --otopi-environment='OVESETUP_CORE/remove=bool:True OVESETUP_CORE/engineStop=bool:True' (and also, until we fix bug 1811593: /bin/rm /etc/pki/ovirt-engine/keys/engine.p12) - restore and setup the same as previous flow In both cases, make sure you only get these errors: [ ERROR ] Failed to execute stage 'Misc configuration': Force Fail: stage 11 priority 90000 (or something similar, if you pressed Ctrl-C) [ ERROR ] Execution of setup failed Sadly, I now tried this, with grafana set up, and it did have another error, related to grafna's db user. Filed bug 1846212 for this, so if you try latter flow (meaning, all in 4.4), please do not configure grafana (for current bug). (In reply to Yedidyah Bar David from comment #3) > - Run: OTOPI_FORCE_FAIL_STAGE=STAGE_MISC > OTOPI_FORCE_FAIL_PRIORITY=PRIORITY_LAST engine-setup --offline > --accept-defaults We default to 'Yes', in 'Configure grafana?', so: [snip] > Sadly, I now tried this, with grafana set up, and it did have another error, > related to grafna's db user. Filed bug 1846212 for this, so if you try > latter flow (meaning, all in 4.4), please do not configure grafana (for > current bug). To make it not configure grafana, for now, you can e.g.: OTOPI_FORCE_FAIL_PRIORITY=PRIORITY_LAST engine-setup --offline --accept-defaults --otopi-environment=OVESETUP_GRAFANA_CORE/enable=bool:False Verified on ovirt-engine-setup-4.4.1.2-0.10.el8ev.noarch Rollback of DB is successful (no string pattern for bytes-like object error appears) when engine-setup fails after creating DB schemas. I ran the upgrade from 4.3 flow as that seemed to be the main point of this bug. This bugzilla is included in oVirt 4.4.1 release, published on July 8th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.1 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |