On Mon 2020-04-27, Christian Boltz wrote:
Now we "only" need to move the forums and bugzilla (and of course also openid), but that are different stories for the next weeks ;-)
Moving bugzilla.opensuse.org/bugzilla.suse.com is in the works, with the migration away from Micro Focus planned for May.
That one is more tricky since Micro Focus (Novell,...), SUSE, and openSUSE all share one database instance and part of the carve out is to separate out openSUSE and SUSE issues from all others with surgical precision.
Christian and one or two others already helped test an earlier export. Thank you! Now there is a public instance available at
https://bugzilla-opensuse-devel.suse.de/index.cgi
If you spot any REGRESSION (that is, something no longer works) please let me know here TODAY (yes, very tight) and I'll relay.
Gerald
PS: Full focus is on moving this off Micro Focus, not updating, enhancing, improving yet. So let's focus in the move for now.
Hello,
Am Mittwoch, 29. April 2020, 11:21:42 CEST schrieb Gerald Pfeifer:
On Mon 2020-04-27, Christian Boltz wrote:
Now we "only" need to move the forums and bugzilla (and of course also openid), but that are different stories for the next weeks ;-)
Moving bugzilla.opensuse.org/bugzilla.suse.com is in the works, with the migration away from Micro Focus planned for May.
That one is more tricky since Micro Focus (Novell,...), SUSE, and openSUSE all share one database instance and part of the carve out is to separate out openSUSE and SUSE issues from all others with surgical precision.
To make it clear for those who read about the bugzilla move for the first time: This means that bugreports that are unrelated to openSUSE or SUSE will _not_ be moved to the new bugzilla.
If you ever reported a bug for a product that doesn't have SUSE or openSUSE in its name (or got a bug moved there), please check if you can still find it in the new bugzilla. During earlier testing, I've already found (actually: missed) a few of my reports which are now also included in the migration, so this is not only a theoretical problem.
Christian and one or two others already helped test an earlier export. Thank you! Now there is a public instance available at
https://bugzilla-opensuse-devel.suse.de/index.cgi
If you spot any REGRESSION (that is, something no longer works) please let me know here TODAY (yes, very tight) and I'll relay.
I'm afraid I'll have to dig out some things that I reported earlier - I've seen them fixed in the meantime, but they came back:
- saved searches (for example "my bugs" or "my reports") give me the "Please stand by..." page forever, but doesn't show a bug list - clicking the "Search" link gives me a "504 Gateway Time-out" for query.cgi - tabular and graphical eports (which also use query.cgi) also run into into a gateway timeout
Needless to say that this makes it impossible to check if all my bugreports are still there - typing (or copy&paste) each of my > 1300 bug numbers is close to impossible ;-)
On the positive side, accessing bugreports with known numbers work, and creating new bugs also works. A somewhat funny detail is that bugzilla mails still get sent with From: bugzilla_noreply@novell.com - it's not a serious problem, but maybe you want to change it nevertheless ;-)
Regards,
Christian Boltz
On Wed 2020-04-29, Christian Boltz wrote:
If you ever reported a bug for a product that doesn't have SUSE or openSUSE in its name (or got a bug moved there), please check if you can still find it in the new bugzilla. During earlier testing, I've already found (actually: missed) a few of my reports which are now also included in the migration, so this is not only a theoretical problem.
To be clear: The criterion for moving/keeping bugs to/in the joint SUSE+openSUSE Bugzilla instance is the relationship to a product, not the affilation of the reporter.
(In other words, a Groupwise bug report of mine would not be moved over. Christian's missing ones were more on the common tools side, so less clear cut.)
I'm afraid I'll have to dig out some things that I reported earlier - I've seen them fixed in the meantime, but they came back:
- saved searches (for example "my bugs" or "my reports") give me the "Please stand by..." page forever, but doesn't show a bug list
Reported in the internal system used for the migration as https://sd.suse.com/servicedesk/customer/portal/1/SD-3848
(Please do not get me started on why we are not using Bugzilla to track Bugzilla issues.)
- clicking the "Search" link gives me a "504 Gateway Time-out" for query.cgi
https://sd.suse.com/servicedesk/customer/portal/1/SD-3849
- tabular and graphical eports (which also use query.cgi) also run into into a gateway timeout
I included that as a note in the above; presumably the same root cause.
A somewhat funny detail is that bugzilla mails still get sent with From: bugzilla_noreply@novell.com - it's not a serious problem, but maybe you want to change it nevertheless ;-)
https://sd.suse.com/servicedesk/customer/portal/1/SD-3850
Thanks for reporting those findings!
Gerald
On Wed, Apr 29, 2020 at 19:01, Gerald Pfeifer gp@suse.com wrote:
On Wed 2020-04-29, Christian Boltz wrote:
I'm afraid I'll have to dig out some things that I reported earlier
I've seen them fixed in the meantime, but they came back:
- saved searches (for example "my bugs" or "my reports") give me the "Please stand by..." page forever, but doesn't show a bug list
Reported in the internal system used for the migration as https://sd.suse.com/servicedesk/customer/portal/1/SD-3848
(Please do not get me started on why we are not using Bugzilla to track Bugzilla issues.)
But do you use bugzilla to track jira bugs? :P
LCP [Stasiek] https://lcp.world
On Wed, 2020-04-29 at 19:08 +0200, Stasiek Michalski wrote:
On Wed, Apr 29, 2020 at 19:01, Gerald Pfeifer gp@suse.com wrote:
On Wed 2020-04-29, Christian Boltz wrote:
I'm afraid I'll have to dig out some things that I reported earlier
I've seen them fixed in the meantime, but they came back:
- saved searches (for example "my bugs" or "my reports") give me
the "Please stand by..." page forever, but doesn't show a bug list
Reported in the internal system used for the migration as https://sd.suse.com/servicedesk/customer/portal/1/SD-3848
(Please do not get me started on why we are not using Bugzilla to track Bugzilla issues.)
But do you use bugzilla to track jira bugs? :P
Let's not do that. I've seen one company doing that extensively and then people complained that most of bugzilla traffic is caused by polling from jira side.
Same fore Community SLE change requests in October, this is not the way I'd like to see it going :-)
LCP [Stasiek] https://lcp.world
-
Christian Boltz -
Gerald Pfeifer -
Lubos Kocman -
Stasiek Michalski