Bug 114652

Summary: udevd: add_to_rules: unknown key 'PLACE', in 'BUS'
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Thorsten Kukuk <kukuk>
Component: BasesystemAssignee: Kay Sievers <kasievers>
Status: RESOLVED FIXED QA Contact: Klaus Kämpf <kkaempf>
Severity: Normal    
Priority: P5 - None CC: hare, yast2-maintainers
Version: Beta 4   
Target Milestone: ---   
Hardware: Other   
OS: All   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Thorsten Kukuk 2005-09-01 08:43:44 UTC
The message from the summary appears very often in /var/log/messages.
Comment 1 Kay Sievers 2005-09-01 12:23:34 UTC
I don't have a rule with PLACE here.
Which rules file has it (/etc/udev/rules.d/*)?
And which rpm provides the file with this rule?
Comment 2 Thorsten Kukuk 2005-09-01 12:28:07 UTC
It is from 20-cdrom.rules and the content is:

# cdrom links generated by YaST2
# 
BUS="ide", PLACE="1.0", SYSFS{removable}="1", SYMLINK="dvd cdrom"


Seems YaST2 did generate it. Since it has a timestamp from Mar 17, I think
we have an update problem here.
Comment 3 Thorsten Kukuk 2005-09-01 13:56:15 UTC
YaST2 Team, who of YaST2 wrote this? How was the update planned?
Comment 4 Klaus Kämpf 2005-09-13 10:13:55 UTC
My workstation also hit this problem after updating RC1 -> RC2 
 
Thomas ? Arvin ? 
Comment 5 Kay Sievers 2005-09-13 10:29:10 UTC
Would be nice if someone can take over the bug. It is not a udev issue I could
solve. I have no idea about yast's update mechanism.
Comment 7 Thomas Fehr 2005-09-13 10:35:50 UTC
The lines with 
BUS="ide", PLACE="1.0", SYSFS{removable}="1", SYMLINK="dvd cdrom"
were created for every cdrom device in SL 9.3 in /etc/udev/rules.d/20-cdrom.rules

On an update from a version with major number < 10
/etc/udev/rules.d/20-cdrom.rules is removed and a file
/etc/udev/rules.d/55-cdrom.rules is created instead. 

Since you updated from 10.x this mechanism was not working and you are stuck
with old /etc/udev/rules.d/20-cdrom.rules. The code handling the update was
added in RC2.

Try an update from a real 9.3 to 10.0 and it should work fine otherwise reopen
this bug, reassign it to me and attach y2log files.