<div dir="ltr"><div>Yes. I can only confirm. </div><div><br></div><div>Please make a public (OpenSUSE) account and report the bug using the</div><div><a href="https://bugzilla.suse.com/enter_bug.cgi?product=PUBLIC%20SUSE%20Linux%20Enterprise%20Server%2015%20SP6" rel="noreferrer" target="_blank">https://bugzilla.suse.com/enter_bug.cgi?product=PUBLIC%20SUSE%20Linux%20Enterprise%20Server%2015%20SP6</a> <br></div><div>or <br></div><div><a href="http://bugzilla.opensuse.org" rel="noreferrer" target="_blank">https://bugzilla.opensuse.org/enter_bug.cgi?product=PUBLIC%20SUSE%20Linux%20Enterprise%20Server%2015%20SP6 <br></a></div><div><br></div><div>Thank you very much</div><div>Rado<br></div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 10, 2024 at 8:51 AM Stefan Weiberg <<a href="mailto:stefan.weiberg@hetzner.com">stefan.weiberg@hetzner.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
it's usually the same account used in the openSUSE community for <br>
<a href="http://bugzilla.opensuse.org" rel="noreferrer" target="_blank">bugzilla.opensuse.org</a> and <a href="http://build.opensuse.org" rel="noreferrer" target="_blank">build.opensuse.org</a>. But I can only open a bug <br>
in the PUBLIC SLES 15 SP6 product, which is usually used for bug <br>
reporting during the beta phase: <br>
<a href="https://bugzilla.suse.com/enter_bug.cgi?product=PUBLIC%20SUSE%20Linux%20Enterprise%20Server%2015%20SP6" rel="noreferrer" target="_blank">https://bugzilla.suse.com/enter_bug.cgi?product=PUBLIC%20SUSE%20Linux%20Enterprise%20Server%2015%20SP6</a><br>
<br>
For the other link I don't have permissions, which is (at least for me) <br>
as expected.<br>
<br>
Cheers,<br>
Stefan Weiberg<br>
<br>
On 10/04/2024 07:04, Gmeinwieser, Klaus wrote:<br>
> Do I need a separate account for the Bugzilla? My SUSE Partner login <br>
> seems not to work…<br>
> <br>
> Please advise<br>
> <br>
> <<a href="https://www.cpp.canon/" rel="noreferrer" target="_blank">https://www.cpp.canon/</a>><br>
> Canon Production Printing Germany GmbH & Co. KG<br>
> P.O. Box 1260, 85581 Poing<br>
> Siemensallee 2, 85586 Poing<br>
> Germany | www.cpp.canon <<a href="https://www.cpp.canon" rel="noreferrer" target="_blank">https://www.cpp.canon</a>><br>
> <br>
> Canon Production Printing Germany GmbH & Co. KG.<br>
> The company is a limited partnership with its registered office in Poing <br>
> - Trade Register HRA 100955 (Amtsgericht München) - WEEE-Reg. - No. DE <br>
> 888 05 443<br>
> <br>
> General Partner: Canon Production Printing Geschäftsführungsgesellschaft <br>
> mbH Registered Office: Poing<br>
> Trade Register HRB 206480 (Amtsgericht München)<br>
> Executive Officer: Johann Meyer<br>
> <br>
> This message and attachment(s) are intended solely for use by the <br>
> addressee and may contain information that is privileged, confidential <br>
> or otherwise exempt from disclosure under applicable law. If you are not <br>
> the intended recipient or agent thereof responsible for delivering this <br>
> message to the intended recipient, you are hereby notified that any <br>
> dissemination, distribution or copying of this communication is strictly <br>
> prohibited. If you have received this communication in error, please <br>
> notify the sender immediately by telephone or with a 'reply' message and <br>
> delete the message and its attachment(s), if any, from your system(s). <br>
> Thank you for your co-operation.<br>
> <br>
> *Von:* Beta Program Manager <<a href="mailto:beta-programs@suse.com" target="_blank">beta-programs@suse.com</a>><br>
> *Gesendet:* Dienstag, 9. April 2024 16:46<br>
> *An:* Gmeinwieser, Klaus <klaus.gmeinwieser@cpp.canon><br>
> *Cc:* <a href="mailto:sle-beta@lists.suse.com" target="_blank">sle-beta@lists.suse.com</a><br>
> *Betreff:* Re: SLE15 SP6 RC1 and rabbitmqctl problem<br>
> <br>
> Hello Klaus,<br>
> <br>
> Thank you very much for this message. One small request: *Could you <br>
> please enter a bug report?* This is the fastest way to get to the <br>
> rabbitmqctl maintainer.<br>
> <br>
> Please fill the bug on:<br>
> <br>
> <a href="https://bugzilla.suse.com/enter_bug.cgi?product=SUSE%20Linux%20Enterprise%20Server%2015%20SP6" rel="noreferrer" target="_blank">https://bugzilla.suse.com/enter_bug.cgi?product=SUSE%20Linux%20Enterprise%20Server%2015%20SP6</a> <<a href="https://bugzilla.suse.com/enter_bug.cgi?product=SUSE%20Linux%20Enterprise%20Server%2015%20SP6" rel="noreferrer" target="_blank">https://bugzilla.suse.com/enter_bug.cgi?product=SUSE%20Linux%20Enterprise%20Server%2015%20SP6</a>><br>
> <br>
> Thank you very much in advance<br>
> <br>
> On Tue, Apr 9, 2024 at 12:21 PM Gmeinwieser, Klaus <br>
> <klaus.gmeinwieser@cpp.canon <mailto:<a href="mailto:klaus.gmeinwieser@cpp.canon" target="_blank">klaus.gmeinwieser@cpp.canon</a>>> wrote:<br>
> <br>
> Hello,<br>
> <br>
> I did a fresh install of SLE15SP6 RC1 and encountered an issue, that<br>
> the “rabbitmqctl” command is broken.<br>
> <br>
> I tried the command within a script:<br>
> <br>
> echo $rabbit_random_password | rabbitmqctl add_user <username><br>
> <br>
> which then prompts for the password instead of using it from the pipe<br>
> <br>
> Then I tried the command:<br>
> <br>
> rabbitmqctl add_user <username><br>
> <br>
> it also prompts (this time correct) for the password. But it does<br>
> not accept any passwords typed and remains frozen!<br>
> <br>
> Therefore the rabbitmq server is not useable with RC1 as the user<br>
> configuration is broken…<br>
> <br>
> This was not the case in the SLE15SP6 Public Beta version.<br>
> <br>
> Could you please check and verify this issue and reply your findings?<br>
> <br>
> Thank you very much in advance & regards<br>
> <br>
> Klaus<br>
> <br>
> <<a href="https://www.cpp.canon/" rel="noreferrer" target="_blank">https://www.cpp.canon/</a>><br>
> Canon Production Printing Germany GmbH & Co. KG<br>
> P.O. Box 1260, 85581 Poing<br>
> Siemensallee 2, 85586 Poing<br>
> Germany | www.cpp.canon <<a href="https://www.cpp.canon" rel="noreferrer" target="_blank">https://www.cpp.canon</a>><br>
> <br>
> Canon Production Printing Germany GmbH & Co. KG.<br>
> The company is a limited partnership with its registered office in<br>
> Poing - Trade Register HRA 100955 (Amtsgericht München) - WEEE-Reg.<br>
> - No. DE 888 05 443<br>
> <br>
> General Partner: Canon Production Printing<br>
> Geschäftsführungsgesellschaft mbH Registered Office: Poing<br>
> Trade Register HRB 206480 (Amtsgericht München)<br>
> Executive Officer: Johann Meyer<br>
> <br>
> This message and attachment(s) are intended solely for use by the<br>
> addressee and may contain information that is privileged,<br>
> confidential or otherwise exempt from disclosure under applicable<br>
> law. If you are not the intended recipient or agent thereof<br>
> responsible for delivering this message to the intended recipient,<br>
> you are hereby notified that any dissemination, distribution or<br>
> copying of this communication is strictly prohibited. If you have<br>
> received this communication in error, please notify the sender<br>
> immediately by telephone or with a 'reply' message and delete the<br>
> message and its attachment(s), if any, from your system(s). Thank<br>
> you for your co-operation.<br>
> <br>
<br>
-- <br>
Mit freundlichen Grüßen<br>
<br>
Stefan Weiberg<br>
IT-Projektmanager<br>
<br>
Hetzner Online GmbH<br>
Industriestr. 25<br>
91710 Gunzenhausen<br>
Tel: +49 9831 505-134<br>
Fax: +49 9831 505-3<br>
<a href="mailto:stefan.weiberg@hetzner.com" target="_blank">stefan.weiberg@hetzner.com</a><br>
<a href="http://www.hetzner.com" rel="noreferrer" target="_blank">www.hetzner.com</a><br>
<br>
<br>
Registergericht Ansbach, HRB 6089<br>
Geschäftsführer: Martin Hetzner,<br>
Stephan Konvickova, Günther Müller<br>
<br>
Hinweise zur Verarbeitung Ihrer personenbezogenen Daten<br>
im Rahmen der Kommunikation mit Ihnen finden Sie unter:<br>
<a href="http://www.hetzner.com/de/privacy-policy-notice" rel="noreferrer" target="_blank">www.hetzner.com/de/privacy-policy-notice</a><br>
</blockquote></div>