To top it all off, I fail to see the reason why support was cut in the
first place.
The change was made in the way init and upstart configurations are
installed to align Debian and Ubuntu, so that users can choose which
init system to use; same applied for systemd configurations now.
--
You
Todd
The service command should work just fine with upstart only
configurations; the service command is written to use the upstart
configuration on upstart based systems and sysvinit scripts on older
style systems such as Debian.
--
You received this bug notification because you are a member of
Todd
Do the Chef configurations call /etc/init.d/keystone directly? or use
the service command?
** Changed in: keystone (Ubuntu)
Status: Confirmed = Opinion
** Changed in: keystone (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member
Todd
Do the Chef configurations call /etc/init.d/keystone directly? or use
the service command?
** Changed in: keystone (Ubuntu)
Status: Confirmed = Opinion
** Changed in: keystone (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member
To top it all off, I fail to see the reason why support was cut in the
first place.
The change was made in the way init and upstart configurations are
installed to align Debian and Ubuntu, so that users can choose which
init system to use; same applied for systemd configurations now.
--
You
Todd
The service command should work just fine with upstart only
configurations; the service command is written to use the upstart
configuration on upstart based systems and sysvinit scripts on older
style systems such as Debian.
--
You received this bug notification because you are a member of
Maybe I'm missing something but why doesn't Canonical fix this. On one
hand they advertise as being Open-Stack Friendly and even the best
flavor to use with OpenStack but yet they refuse to play nice with a
script that was written by OpenStack to automate installation, opting
instead for it's them
Maybe I'm missing something but why doesn't Canonical fix this. On one
hand they advertise as being Open-Stack Friendly and even the best
flavor to use with OpenStack but yet they refuse to play nice with a
script that was written by OpenStack to automate installation, opting
instead for it's them
Shall we temporary fix the cookbook by manually specifying Upstart
Provider? e.g.
provider Chef::Provider::Service::Upstart if platform?(ubuntu)
node[platform_version].to_f = 13.10
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Shall we temporary fix the cookbook by manually specifying Upstart
Provider? e.g.
provider Chef::Provider::Service::Upstart if platform?(ubuntu)
node[platform_version].to_f = 13.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug also affects OpenStack deployment and configuration via Chef.
OpenStack's official cookbooks require the initscripts or they fail.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
Can confirm Todd Crane's comment. Just hit this using the StackForge
coookbooks.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/1315188
Title:
No init.d script included in
** Tags added: 14.04
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/1315188
Title:
No init.d script included in icehouse ubuntu packaging
To manage notifications about this bug
I was able to work around this by issuing an 'ln -s /lib/init/upstart-
job /etc/init.d/keystone'
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/1315188
Title:
No init.d script
This bug also affects OpenStack deployment and configuration via Chef.
OpenStack's official cookbooks require the initscripts or they fail.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315188
Can confirm Todd Crane's comment. Just hit this using the StackForge
coookbooks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315188
Title:
No init.d script included in icehouse ubuntu packaging
** Tags added: 14.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315188
Title:
No init.d script included in icehouse ubuntu packaging
To manage notifications about this bug go to:
I was able to work around this by issuing an 'ln -s /lib/init/upstart-
job /etc/init.d/keystone'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315188
Title:
No init.d script included in icehouse
It is - keystone only ships an upstart configuration (no init script)
which installs to /etc/init
Using the service command is the correct way to call init
scripts/upstart configuration:
sudo service keystone restart
This will ensure that the preferred method of managing the service is
used
The errors in the original bug report are non-fatal. Packages are
supposed to provide both init scripts and equivalent upstart
configurations but this is not enforced.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in
James. I thought this might be the case, but if it is, it still doesn't
solve the original problem. My understanding is that Upstart scripts
require registration with initctl in order for the service commands to
work. This does not appear to be occurring during install, so the above
mentioned
The errors in the original bug report are non-fatal. Packages are
supposed to provide both init scripts and equivalent upstart
configurations but this is not enforced.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It is - keystone only ships an upstart configuration (no init script)
which installs to /etc/init
Using the service command is the correct way to call init
scripts/upstart configuration:
sudo service keystone restart
This will ensure that the preferred method of managing the service is
used
James. I thought this might be the case, but if it is, it still doesn't
solve the original problem. My understanding is that Upstart scripts
require registration with initctl in order for the service commands to
work. This does not appear to be occurring during install, so the above
mentioned
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: keystone (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
This is confusing as some services like rabbitmq-server still have an
init script:
root@stackforge-ubuntu:~# dpkg -S /etc/init.d/rabbitmq-server
rabbitmq-server: /etc/init.d/rabbitmq-server
root@stackforge-ubuntu:~# ls -al /etc/init.d/rabbitmq-server
-rwxr-xr-x 1 root root 3991 Mar 5 21:32
Was this removal intentional? I just assumed it was an omission since
it's setup process still exists in the package, and it's assumed to be
that way in the docs.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: keystone (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315188
Title:
This is confusing as some services like rabbitmq-server still have an
init script:
root@stackforge-ubuntu:~# dpkg -S /etc/init.d/rabbitmq-server
rabbitmq-server: /etc/init.d/rabbitmq-server
root@stackforge-ubuntu:~# ls -al /etc/init.d/rabbitmq-server
-rwxr-xr-x 1 root root 3991 Mar 5 21:32
Was this removal intentional? I just assumed it was an omission since
it's setup process still exists in the package, and it's assumed to be
that way in the docs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Project changed: keystone = keystone (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/1315188
Title:
No init.d script included in icehouse ubuntu packaging
To manage
** Project changed: keystone = keystone (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315188
Title:
No init.d script included in icehouse ubuntu packaging
To manage notifications about
32 matches
Mail list logo
