June 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 978833] New: systemsmanagement:saltstack/salt broken pkgrepo.managed priority atribute
by bugzilla_noreply＠novell.com 08 Feb '21

08 Feb '21

http://bugzilla.suse.com/show_bug.cgi?id=978833 Bug ID: 978833 Summary: systemsmanagement:saltstack/salt broken pkgrepo.managed priority atribute Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bmaryniuk(a)suse.com Reporter: tchatzimichos(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- pkgrepo.managed priority attribute shows the following error: Failed to configure repo 'NON_Public:Infrastructure': zypper command failed: Invalid priority ''102''. Use a positive integer number. The greater the number, the lower the priority. -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1032452] New: salt-cloud package misses deployment scripts
by bugzilla_noreply＠novell.com 08 Feb '21

08 Feb '21

http://bugzilla.suse.com/show_bug.cgi?id=1032452 Bug ID: 1032452 Summary: salt-cloud package misses deployment scripts Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: openSUSE 42.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dkarakasilis(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 Build Identifier: There is a number of scripts that salt-cloud uses in order to "saltify" (aka bootstrap) the minions: https://github.com/saltstack/salt/tree/develop/salt/cloud/deploy One of them (bootstrap-salt.sh) is the default when no specific (or custom) script is specified in configuration. None of our packages (salt, salt-cloud) provide that script. As a result, when a machine is started on some public cloud (only tried ec2 driver), the machine doesn't get salt-master or salt-minion services installed or run. The bootstrap process is completely ignored. After copying the bootstrap-salt.sh script from the github repo in "/usr/lib/python2.7/site-packages/salt/cloud/deploy" directory, the machines gets saltified. One thing to keep in mind though, if we are going to package those files, is that there is a "salt-cloud -u" command that fetches the latest versions from i-dont-know-where. That might mean, our users will use versions of those scripts that weren't packaged (or tested) by us. The 'salt-cloud -u' command doesn't fetch anything in my case, I don't know if this is because of the files missing in the first place or some other problem. Reproducible: Always Steps to Reproduce: 1. In OpenSUSE LEAP 42.2 install the packages salt-cloud and salt 2. Create ec2 provider and profile configuration 3. Try to create a saltified machine. E.g. "salt-cloud -p my_ec2_profile my_machine_name" Actual Results: The machine is created but there is no salt related package installed and no salt service running. We should get at least salt-minion running. Expected Results: Depending on configuration we should get "salt-minion" services installed and running. If we set "make_master: True" in our configuration we should also get salt-master service installed and running. below are an ec2 provider and profile examples. Replace placeholders with something working. > cat /etc/salt/cloud.providers.d/my-ec2.provider.conf my-ec2-provider: id: your_id_here key: 'your_key_here' keyname: your_key_name_as_it_appears_in_aws_console subnetid: comment_out_if_no_subnet_is_used private_key: your_pem_key_path # Make sure it is owned by whatever user salt is run as driver: ec2 ssh_interface: public_ips > cat /etc/salt/cloud.profiles.d/base_ec2.conf base_ec2: provider: my-ec2-provider # Opensuse image image: ami-eada30fc size: t2.micro make_master: True ssh_username: ec2-user -- You are receiving this mail because: You are on the CC list for the bug.

2 28

[Bug 1020831] New: All salt commands hang and cause salt-master to crash soon after
by bugzilla_noreply＠novell.com 08 Feb '21

08 Feb '21

http://bugzilla.suse.com/show_bug.cgi?id=1020831 Bug ID: 1020831 Summary: All salt commands hang and cause salt-master to crash soon after Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: hguo(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 710818 --> http://bugzilla.suse.com/attachment.cgi?id=710818&action=edit master journal I started 3 fresh instances of Leap 42.2 on EC2, then proceed to install all updates and salt. Two minions can successfully join the master, but then all salt commands issued by master hang and cause salt-master to crash soon after a python error is raised. See attached log files. -- You are receiving this mail because: You are on the CC list for the bug.

2 41

[Bug 1046104] New: Monospaced font SourceCodePro is bold by default after update to texlive 2017
by bugzilla_noreply＠novell.com 02 Feb '21

02 Feb '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1046104 Bug ID: 1046104 Summary: Monospaced font SourceCodePro is bold by default after update to texlive 2017 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: mail(a)philipp-wagner.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 730330 --> http://bugzilla.opensuse.org/attachment.cgi?id=730330&action=edit Screenshot with texlive-sourcecodepro installed Since the last update including the new texlive 2017 packages, the default monospace font (SourceCodePro) on my system was overwritten with a bold one. Things are better explained in a picture as seen in the attached screenshots. I got things back to normal by deinstalling the texlive versions of the font with > sudo zypper remove texlive-sourcecodepro* Now the following packets are installed: > LANG=C sudo zypper search sourcecodepro Loading repository data... Reading installed packages... S | Name | Summary | Type ---+-----------------------------+----------------------------------------------------------+-------- i+ | adobe-sourcecodepro-fonts | A set of OpenType fonts designed for coding environments | package | texlive-sourcecodepro | Use SourceCodePro with TeX(-alike) systems | package | texlive-sourcecodepro-doc | Documentation for texlive-sourcecodepro | package | texlive-sourcecodepro-fonts | Severed fonts for texlive-sourcecodepro | package I've confirmed with fc-match that if the texlive packages are installed, the texlive version of SourceCodePro is used. Otherwise, it's the version from the adobe-sourcecodepro-fonts package. I've also attached the output of "fc-match -v monospace" before and after deinstalling the texlive package. My system information: > cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20170625" ID=opensuse ID_LIKE="suse" VERSION_ID="20170625" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:tumbleweed:20170625" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 980577] New: "cobbler get-loaders" doesn't resolve www.clobberd.org
by bugzilla_noreply＠novell.com 14 Jan '21

14 Jan '21

http://bugzilla.suse.com/show_bug.cgi?id=980577 Bug ID: 980577 Summary: "cobbler get-loaders" doesn't resolve www.clobberd.org Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: pablo.suarezhernandez(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ferruja:~ # cobbler get-loaders task started: 2016-05-18_154111_get_loaders task started (id=Download Bootloader Content, time=Wed May 18 15:41:11 2016) downloading http://www.cobblerd.org/loaders/README to /var/lib/cobbler/loaders/README Exception occured: <class 'urlgrabber.grabber.URLGrabError'> Exception value: [Errno 14] PYCURL ERROR 6 - "Could not resolve host: www.cobblerd.org" Exception Info: File "/usr/lib/python2.7/site-packages/cobbler/remote.py", line 87, in run rc = self._run(self) File "/usr/lib/python2.7/site-packages/cobbler/remote.py", line 181, in runner return self.remote.api.dlcontent(self.options.get("force",False), self.logger) File "/usr/lib/python2.7/site-packages/cobbler/api.py", line 751, in dlcontent return grabber.run(force) File "/usr/lib/python2.7/site-packages/cobbler/action_dlcontent.py", line 72, in run urlgrabber.grabber.urlgrab(src, filename=dst, proxies=proxies) File "/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 618, in urlgrab return default_grabber.urlgrab(url, filename, **kwargs) File "/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 982, in urlgrab return self._retry(opts, retryfunc, url, filename) File "/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 886, in _retry r = apply(func, (opts,) + args, {}) File "/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 968, in retryfunc fo = PyCurlFileObject(url, filename, opts) File "/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 1063, in __init__ self._do_open() File "/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 1352, in _do_open self._do_grab() File "/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 1482, in _do_grab self._do_perform() File "/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 1339, in _do_perform raise err !!! TASK FAILED !!! -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 956264] New: cobbler_web apache config uses old syntax
by bugzilla_noreply＠novell.com 14 Jan '21

14 Jan '21

http://bugzilla.suse.com/show_bug.cgi?id=956264 Bug ID: 956264 Summary: cobbler_web apache config uses old syntax Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: osynge(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Please set up cobbler and cobbler_web to use new syntax. Require all granted instead of Order allow,deny Allow from all See http://httpd.apache.org/docs/2.4/upgrading.html. -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 1032027] New: btrfs cleaner => freeze
by bugzilla_noreply＠novell.com 11 Jan '21

11 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1032027 Bug ID: 1032027 Summary: btrfs cleaner => freeze Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: epistemepromeneur(a)free.fr QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- each time btrfs cleaner is active then all dialogs are freezed. we must wait for the end to use our pc. on a slow laptop we must wait several minutes! -- You are receiving this mail because: You are on the CC list for the bug.

2 27

[Bug 956153] New: Software Update Error "License Agreement Failed" But A License Agreement Is Never Presented
by bugzilla_noreply＠novell.com 08 Jan '21

08 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=956153 Bug ID: 956153 Summary: Software Update Error "License Agreement Failed" But A License Agreement Is Never Presented Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: bill_wayson(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 656868 --> http://bugzilla.opensuse.org/attachment.cgi?id=656868&action=edit Zip file with error message screenshot, zypper.log, and pk_backend_zypp files On Saturday morning (11/21/2015 PST) I am presented with 246 updates by the software updater. I press the "Install Updates" button, and the update begins. But it quickly stops with a message dialog "Update Error The license agreement failed. The license agreement was not agreed to. To use this software you have to accept the license." The problems are that a license agreement dialog is never presented, and there is no indication of which of the 246 updates require the license agreement (so that I can, say, deselect it). I have attached a zip file that contains a screenshot of the message along with the zypper.log and pk_backend_zypp files. The latter file appears to be the log updated by the software updater. My tumbleweed is currently at 20151113. I hope I chose the correct component. -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 1004049] New: /usr/bin/socat ... openpty() is not allowd to do chown of resulting /dev/pts/ device
by bugzilla_noreply＠novell.com 08 Jan '21

08 Jan '21

http://bugzilla.suse.com/show_bug.cgi?id=1004049 Bug ID: 1004049 Summary: /usr/bin/socat ... openpty() is not allowd to do chown of resulting /dev/pts/ device Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: All OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: werner(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Even with apparmor disabled I see in the strace close(8) = 0 close(7) = 0 chown("/dev/pts/8", 223, 5) = -1 EPERM (Operation not permitted) close(6) = 0 which makes this tool useless for normal users. Beside this: why we do have setcap/getcap installed by default? With this we would be able to set permissions based on capabilities for tools like setcap and ping, ping6, ... in the %post install section of the rpm of the affected tools -- You are receiving this mail because: You are on the CC list for the bug.

2 16

[Bug 954603] New: Leap lacks tomcat
by bugzilla_noreply＠novell.com 08 Jan '21

08 Jan '21

http://bugzilla.suse.com/show_bug.cgi?id=954603 Bug ID: 954603 Summary: Leap lacks tomcat Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Java Assignee: bnc-team-java(a)forge.provo.novell.com Reporter: tchvatal(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Leap lacks tomcat as it didn't build. I will submit fixed dbcp that should go later as maint-update to SLE12 directly and for tomcat we can grab 1:1 the SLE-12:SP1 counterpart. -- You are receiving this mail because: You are on the CC list for the bug.

2 11