** Description changed: == Impact == The ceph upstart configurations don't work correctly on systems with hostnames that contain uppercase characters. == Test == Easiest todo with juju: Configured your MAAS environment with servers with uppercase hostname. juju bootstrap mkdir raring (cd raring; bzr branch lp:charms/ceph) cat > local.yaml << EOF ceph: fsid: '6547bd3e-1397-11e2-82e5-53567c8d32dc' monitor-count: 3 monitor-secret: 'AQCXrnZQwI7KGBAAiPofmKEXKxu5bUzoYLVkbQ==' - osd-devices: '/dev/vdb' + osd-devices: '/dev/sdb' osd-reformat: 'yes' - ephemeral-unmount: '/mnt' EOF Deploy charm on raring using the above configuration juju deploy --config local.yaml --repository . -n 3 local:raring/ceph No ceph daemons will start due to missing uppercase pattern matching in the upstart configurations. == Regression Potential == Limited; this fix is already in Saucy (and tested OK) and simple extends the range of permitted chars to include uppercase letters == Original Bug Report == Its possible to configure a server with uppercase letters in the hostname: OS01-07 for example. When initializing a ceph mon filesystem this gets created OK in /var/lib/ceph/mon/ceph-OS01-07 - but the upstart configuration won't detect the mon filesystem as it contains uppercase letters. I was initially confused as running the same find command in the shell worked OK - but running it under the POSIX locale as happens in the upstart configuration causes the filesystem to be missed. I'm not 100% sure this is actually a bug - raising for discussion!
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1218852 Title: [SRU] hostnames with upper case letters don't make good MON's To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1218852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
