I think close notabug. Also, should really all users of engine-backup be notified about upgrades? You know, they might use it for simple backups... We discussed adding a flag such as "--for-migration" or something like that. We can do that, but people will normally not know they should use it.
(In reply to Yedidyah Bar David from comment #2) > I think close notabug. Also, should really all users of engine-backup be > notified about upgrades? You know, they might use it for simple backups... > > We discussed adding a flag such as "--for-migration" or something like that. > We can do that, but people will normally not know they should use it. 3.6 is a special use case since the user might use it for update. We should make the text sound optional, some thing like: "If you are backing up the engine as part of a migration to 4.0, please refer to upgrade helper <link>" We are getting a lot of issues in later stages of the migration, because people don't get to the helper until late in the migration.
(In reply to Yaniv Dary from comment #3) > (In reply to Yedidyah Bar David from comment #2) > > I think close notabug. Also, should really all users of engine-backup be > > notified about upgrades? You know, they might use it for simple backups... > > > > We discussed adding a flag such as "--for-migration" or something like that. > > We can do that, but people will normally not know they should use it. > > 3.6 is a special use case since the user might use it for update. > We should make the text sound optional, some thing like: > "If you are backing up the engine as part of a migration to 4.0, please > refer to upgrade helper <link>" This means to have a downstream-only patch for engine-backup. > > We are getting a lot of issues in later stages of the migration, because > people don't get to the helper until late in the migration. With what flow? This bug is cloned from bug 1370041, which is about hosted-engine. You probably refer to the standalone case. Ok, fine with me then. Sandro, please ack. If [1] was in 3.6, we could have this as a hook instead of a downstream-only patch... [1] https://gerrit.ovirt.org/54878
(In reply to Yedidyah Bar David from comment #4) > Sandro, please ack. Acked > If [1] was in 3.6, we could have this as a hook instead > of a downstream-only patch... > > [1] https://gerrit.ovirt.org/54878 Let's backport
Moving this bug to verified forth to https://bugzilla.redhat.com/show_bug.cgi?id=1398374#c15.
Is this a dup of BZ #1398374?
(In reply to Yaniv Dary from comment #8) > Is this a dup of BZ #1398374? Currently it is. Originally bug 1398374 was on the branding package. Since both bugs have merged patches we decided to not close as duplicate. If you decide to close, please copy the links to the patches.
*** This bug has been marked as a duplicate of bug 1398374 ***