'/bin/systemctl enable atop' returned 1: Failed to issue method call: No such file or directory

[Charles Hsu]

I'm doing some upgrade MOS 8.0 to 9.0/9.1 tests, when I build a new MOS 8.0 env that I stuck in this service (atop).

2016-12-09 08:35:01 ERR /usr/lib/ruby/vendor_ruby/puppet/provider/command.rb:23:in `execute'
2016-12-09 08:35:01 ERR /usr/lib/ruby/vendor_ruby/puppet/util/execution.rb:219:in `execute'
2016-12-09 08:35:01 ERR Execution of '/bin/systemctl enable atop' returned 1: Failed to issue method call: No such file or directory
2016-12-09 08:34:57 ERR (/Stage[main]/Osnailyfacter::Atop/Service[atop]/enable) change from false to true failed: Execution of '/bin/systemctl enable atop' returned 1: Failed to issue method call: No such file or directory

I already update to latest version of MOS 8.0.

[Oleksiy Molchanov (omolchanov)]

Charles, can you write down steps you were doing? Marking this as Incomplete.

[Oleksiy Molchanov (omolchanov)]

Seems that it is already fixed https://bugs.launchpad.net/fuel/+bug/1645304

[Charles Hsu (charles0126)]

Oleksiy,

Here are all steps I did,

1. Use MOS 8.0 ISO with virutalbox script
2. Create setup a fuel-master (configure network)
3. Fuel-createmirror -U
4. Fuel-createmirror -M
5. Update fuel-master (https://docs.mirantis.com/openstack/fuel/fuel-8.0/maintenance-updates.html#mu8-0-how-to-update)
6. Create a openstack env (all default, use ubuntu 14.04 + vlan)
5. Add one node (controller + cinder), one node for compute
6. Deployment env

I tried to disable/enable our plugin and all got same result.

https://cloud.swiftstack.com/v1/AUTH_charz/fuel/fuel-snapshot-2016-12-09_09-11-07.tar.xz

BTW, I clean up all nodes (fuel-master and slaves) and recreate it again, but still no lucky.

[Charles Hsu (charles0126)]

Is there a way to do a workaround for this issue? That I can move forward to test upgrade MOS 9.x?

[Johnson (zhengmx)]

Hi
I intalled MOS9.0 one month ago successly. But I got the same error above after installing another new MOS9.0 yesterday. I wondered how could I fix this issue ?

Thanks !

[greg (loughmiller)]

I install MOS9.0 last week(week of 12/5) successfully. when cleaning up and re-installing on 12/11 thru 12/13 - same error as other reported.. I'm not able to update to MOS 9.1 - I need to use MOS 9.0 but am now unable to successfully install due to this error.
thus, what work around is available? anything to adjust with repo within Fuel? Effectively has disabled the ability to install Fuel/MOS at this time.

[ganesan (ganesan-jd)]

same issue for me, I installed MOS9.0 last week and it worked fine. I was cleaning up and installing again and struck.

Any possible solution to move ahead with deployment of OpenStack environment