Hmm, I can't reproduce that. If I set --s3_port=3334 in my /etc/nova/nova.conf, nova-objectstore starts on port 3334 alright:
Started S3 Objectstore on 192.168.0.111:3334
That said, it starts up as root, while it should start up as nova -> created bug 820968 to track that
Andrew, any funky permissions on /etc/nova/nova.conf that would prevent root from reading it on your setup ? Does running as nova solve it ?
Hmm, I can't reproduce that. If I set --s3_port=3334 in my /etc/nova/ nova.conf, nova-objectstore starts on port 3334 alright:
Started S3 Objectstore on 192.168.0.111:3334
That said, it starts up as root, while it should start up as nova -> created bug 820968 to track that
Andrew, any funky permissions on /etc/nova/nova.conf that would prevent root from reading it on your setup ? Does running as nova solve it ?