August 2012 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 772075] dmsetup remove hangs forever
by bugzilla_noreply＠novell.com 01 Aug '12

01 Aug '12

https://bugzilla.novell.com/show_bug.cgi?id=772075 https://bugzilla.novell.com/show_bug.cgi?id=772075#c21 --- Comment #21 from Robert Milasan <rmilasan(a)suse.com> 2012-08-01 13:56:38 UTC --- Sorry, but I'm not getting the idea of the installation here... How exactly is device-mapper installed and udev? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 772075] dmsetup remove hangs forever
by bugzilla_noreply＠novell.com 01 Aug '12

01 Aug '12

https://bugzilla.novell.com/show_bug.cgi?id=772075 https://bugzilla.novell.com/show_bug.cgi?id=772075#c20 Adrian Schröter <adrian(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mls(a)suse.com --- Comment #20 from Adrian Schröter <adrian(a)suse.com> 2012-08-01 13:54:03 UTC --- The problem seems to exist already after setup of the build system, independend of kiwi. Either device-mapper needs to enforce that udevd re-reads the rules files or udevd needs to be fixed watching the rules.d directory. Currently check_rules_timestamp of udevd never will return true when it is called the first time. Thus we have a race between the first times the rules are read in in the first time check_rules_timestamp is called. The solution is to also set the stamp_usec array when the rules are read in the first time. (Of course the real problem can be something else, we're just guessing) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 700267] New: openSUSE:Factory:Contrib/cruisecontrol: Bug
by bugzilla_noreply＠novell.com 01 Aug '12

01 Aug '12

https://bugzilla.novell.com/show_bug.cgi?id=700267 https://bugzilla.novell.com/show_bug.cgi?id=700267#c0 Summary: openSUSE:Factory:Contrib/cruisecontrol: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: graham(a)andtech.eu ReportedBy: rozelak(a)volny.cz QAContact: opensuse-communityscreening(a)forge.provo.novell.com CC: opensuse-contrib(a)opensuse.org Found By: Other Blocker: No Dear developer. We decided to use cruisecontrol on 'encfs'-encrypted path, which is not well supported by your init scripts (cruisecontrol-2.8.4-1.1.noarch.rpm). Therefore, I'm sending changes we made. They are not perfect, but please, have a look at them and consider the proposed generalizations in order to simplify transfer of CC to other path (ideal case is only to change settings in /etc/default/cruisecontrol). Unfortunatelly, I cannot append a file with changed files and diffs from ..2.8.4-1.1 rpm. But if you want, I can send it to you to graham(a)andtech.eu e-mail. ----- /etc/default/cruisecontrol: # Run CruiseControl as this user ID (default: ccontrol) # # Set this to an empty string to prevent CruiseControl from starting # automatically. Think to stop CruiseControl before setting an empty string ;o) # CRUISE_USER="cruise" CRUISE_SPOOL=/home/cruise CRUISE_PID=${CRUISE_SPOOL}/cc.pid # Port used for the JMX Http Console CRUISE_JMX_PORT=8000 # Port used for RMI CRUISE_RMI_PORT=1099 # Port used for HTTP CRUISE_WEB_PORT=8080 # The home directory of the Java development kit (JDK). #JAVA_HOME="/usr/lib/jvm/java-1.5.0-sun" # Arguments to pass to the CruiseControl script CRUISE_OPTS="-Xmx256m -Xms256m -server -Xincgc -Dcc.config.file=${CRUISE_SPOOL}/config.xml -Dcc.artifacts=${CRUISE_SPOOL} /artifacts -Dcc.projects=${CRUISE_SPOOL}/projects -Dcc.logdir=${CRUISE_SPOOL}/logs -Dcc.ajp13port=8009 -Dlog4j.configurat ion=file://${CRUISE_SPOOL}/log4j.properties" ----- /etc/init.d/cruisecontrol: #!/bin/bash # # Init file for CruiseControl server daemon # # chkconfig: 2345 20 80 # description: CruiseControl server daemon # ### BEGIN INIT INFO # Provides: cruisecontrol # Required-Start: $local_fs $network $syslog # Should-Start: java # Required-Stop: $null # Default-Start: 3 5 # Default-Stop: 0 1 2 4 6 # Short-Description: CruiseControl # Description: CruiseControl ### END INIT INFO # source function library if [ -f /lib/lsb/init-functions ]; then . /lib/lsb/init-functions fi if [ -f /etc/default/cruisecontrol ]; then . /etc/default/cruisecontrol fi # DT: Must use values defined in /etc/default/cruisecontrol CRUISE_PID=${CRUISE_PID:-/var/spool/cruisecontrol/cc.pid} CRUISE_SPOOL=${CRUISE_SPOOL:-/var/spool/cruisecontrol} start() { # DT: /etc/cruisecontrol/cruisecontrol.xml replaced by ${CRUISE_SPOOL}/config.xml # DT: must go to the directory, otherwise CC is started somehow strange ... # It may be enough to set CCHOME, but I'm not sure ... CMD="cd $CRUISE_SPOOL; JAVA_HOME=${JAVA_HOME:-/usr} PATH=${JAVA_HOME:-/usr}/bin:$PATH CC_OPTS=\"${CRUISE_OPTS:-}\" /u sr/bin/cruisecontrol -configfile ${CRUISE_SPOOL}/config.xml -jmxport ${CRUISE_JMX_PORT:-8000} -rmiport ${CRUISE_RMI_PORT: -1099} -webport ${CRUISE_WEB_PORT:-8080} -webapppath /usr/share/cruisecontrol/webapps/cruisecontrol -dashboard /usr/share /cruisecontrol/webapps/dashboard >/dev/null &" pgrep -f cruisecontrol-launcher.jar >/dev/null PROCESS_EXIST=$? if [ $PROCESS_EXIST -ne 0 ]; then if [ "`whoami`" == "${CRUISE_USER:-cruise}" ]; then echo -n "Starting Cruise Control..." eval ${CMD} elif [ "`whoami`" == "root" ]; then echo -n "Starting Cruise Control..." su -s /bin/sh ${CRUISE_USER:-cruise} -c "${CMD}" echo "started." else echo "You are not root or ${CRUISE_USER:-cruise}, not starting" fi else echo "Cruise Control already started." exit fi } stop() { # DT: will fail, if $CRUISE_PID is not accessigle (e.g. encfs-crypted CC home ...) if [ -f $CRUISE_PID ]; then PID=`cat $CRUISE_PID` fi PID_EXISTS=-1 if [ ! -z $PID ]; then ps -p $PID >/dev/null PID_EXISTS=$? fi # DT: If PID not found, use pgrep instead (exactly as in start() section # TODO: check the user -u ${CRUISE_USER:-cruise} as well? if [ $PID_EXISTS -ne 0 ] ; then PID=$(pgrep -f cruisecontrol-launcher.jar) PID_EXISTS=$? fi if [ $PID_EXISTS -eq 0 ] ; then echo "Stopping Cruise Control (process $PID)..." kill $PID else echo "Cruise Control not running..." fi } case "$1" in start) start ;; stop) stop ;; restart) stop sleep 5 start ;; force-reload) ;; status) ;; *) echo "Usage: $0 [start|stop|restart|force-reload|status]" exit 1 esac exit 0 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 2

[Bug 773971] New: /etc/cups/cupsd.conf.default /etc/cups/cupsd.conf are hardlinks
by bugzilla_noreply＠novell.com 01 Aug '12

01 Aug '12

https://bugzilla.novell.com/show_bug.cgi?id=773971 https://bugzilla.novell.com/show_bug.cgi?id=773971#c0 Summary: /etc/cups/cupsd.conf.default /etc/cups/cupsd.conf are hardlinks Classification: openSUSE Product: openSUSE 12.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Printing AssignedTo: jsmeix(a)suse.com ReportedBy: jw(a)suse.com QAContact: jsmeix(a)suse.com Found By: --- Blocker: --- Currently $ diff /etc/cups/cupsd.conf.default /etc/cups/cupsd.conf is not a good way to find changes, as these files are hardlinks. Do we have an unwanted fdupes in the cups spec-file? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 2

[Bug 772075] dmsetup remove hangs forever
by bugzilla_noreply＠novell.com 01 Aug '12

01 Aug '12

https://bugzilla.novell.com/show_bug.cgi?id=772075 https://bugzilla.novell.com/show_bug.cgi?id=772075#c19 --- Comment #19 from Robert Milasan <rmilasan(a)suse.com> 2012-08-01 13:22:14 UTC --- Well it's also possible, but as I dont know kiwi and all of it how it works I cant really say my opinion. You need some maintainer of the "parts" to see whats going on. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 772075] dmsetup remove hangs forever
by bugzilla_noreply＠novell.com 01 Aug '12

01 Aug '12

https://bugzilla.novell.com/show_bug.cgi?id=772075 https://bugzilla.novell.com/show_bug.cgi?id=772075#c18 --- Comment #18 from Adrian Schröter <adrian(a)suse.com> 2012-08-01 13:18:55 UTC --- A guess from mls is that it is caused because device-mapper gets install <3 seconds after udev got installed and started, so it does not discover new files during that timeframe according its sleep 3sec loop. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 772075] dmsetup remove hangs forever
by bugzilla_noreply＠novell.com 01 Aug '12

01 Aug '12

https://bugzilla.novell.com/show_bug.cgi?id=772075 https://bugzilla.novell.com/show_bug.cgi?id=772075#c17 --- Comment #17 from Robert Milasan <rmilasan(a)suse.com> 2012-08-01 13:08:34 UTC --- Well the rules should be in /lib/udev/rules.d, like this: /lib/udev/rules.d/10-dm.rules /lib/udev/rules.d/13-dm-disk.rules /lib/udev/rules.d/95-dm-notify.rules This should exists on the system or in initrd. You can always enable debug at boot time for udev and see whats going on: udev.log_priority=debug and boot the system with that. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 772075] dmsetup remove hangs forever
by bugzilla_noreply＠novell.com 01 Aug '12

01 Aug '12

https://bugzilla.novell.com/show_bug.cgi?id=772075 https://bugzilla.novell.com/show_bug.cgi?id=772075#c16 --- Comment #16 from Adrian Schröter <adrian(a)suse.com> 2012-08-01 13:04:49 UTC --- Our current guess is that the running udevd is not aware of the rules files from device-mapper package. The problem does not exist at least, when doing manually a udevadm control --reload-rules before kiwi gets invoked. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 766217] New: Cannot add IPv6 routes in YaST: 'Gateway IP address is invalid'
by bugzilla_noreply＠novell.com 01 Aug '12

01 Aug '12

https://bugzilla.novell.com/show_bug.cgi?id=766217 https://bugzilla.novell.com/show_bug.cgi?id=766217#c0 Summary: Cannot add IPv6 routes in YaST: 'Gateway IP address is invalid' Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: i686 OS/Version: openSUSE 12.1 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: srid(a)rkmail.ru QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Opera/9.80 (X11; Linux x86_64; U; ru) Presto/2.10.229 Version/11.64 It is impossible to add IPv6 routes using YaST, because it does not understand IPv6 address format. Instead of adding a route, YaST show you a 'Gateway IP address is invalid' error message. Reproducible in ncurces and Qt fontends. Reproducible: Always Steps to Reproduce: 1. run YaST 2. go to Network Devices -> Network Settings -> Routing 3. try to add an IPv6 route -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 7

[Bug 772075] dmsetup remove hangs forever
by bugzilla_noreply＠novell.com 01 Aug '12

01 Aug '12

https://bugzilla.novell.com/show_bug.cgi?id=772075 https://bugzilla.novell.com/show_bug.cgi?id=772075#c15 --- Comment #15 from Robert Milasan <rmilasan(a)suse.com> 2012-08-01 12:31:23 UTC --- OK, checked a bit 12.2 and just shutdown udevd. If you do that the right the queue.bin is removed, so which means that dmsetup finds queue.bin and udevd for some reason wants shutdown properly. Maybe, just maybe this should be deleted from initrd after stopping udev, just to make sure. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0