10:22 p.m.
Hello Yatin,
On Wed, 10 Feb 2021 at 10:51, YATIN KAREL <yatinkarel(a)gmail.com> wrote:
Hi Amey,
On Wed, Feb 10, 2021 at 9:37 AM Amey Abhyankar <sco1984(a)gmail.com> wrote:
>
> Hello,
>
> I am trying to install OpenStack PackStack in DELL360 server but getting issues.
>
> Details as follows:
>
> Hardware: DELL360 PowerEdge
> Processor: Intel XEON E5-2699 v4 @ 2.20 Ghz [2 physical CPU's]
> Memory: 512 GB
> Disk type: Intel SSD's
> OS tried: Cent OS 7 (2003,2009) , Cent OS 8.3
> RDO repo's tried: Victoria,Ussuri,Train
Victoria, Ussuri should install fine over CentOS8, Train should install fine on both
CentOS7 and CentOS8.
>
> Errors statements:
> - Command Exceeded timeout at the end of pp execution
> - Systemd start for openstack-nova-scheduler failed
Have you checked the nova-scheduler logs(/var/log/nova/nova-scheduler.log) to see why it
failed and also the pp execution log to see where it's stuck? From there it could have
some hint.
Need to see more logs/info to understand the issue, starting with:-
- nova-scheduler log
- packstack install logs
- output of "dnf repolist"
- answer file and installation commands used
- output of "ip a"
- output of "getenforce"
I tried with Rocky release yesterday.
I saw file descriptor errors in MySQL DB log.
I am using CentOS 7 (2003 version)
MySQL DB kept eating 99% CPU for an hour+
eventually packstack installation failed
Errors from the log file =
--------------------------------------------------------------------------------
Warning: Unknown variable: '::nova::vncproxy::host'. at
/var/tmp/packstack/2f41026548a941369ed4234e12e1a3a3/modules/nova/manifests/vncproxy/common.pp:31:5
Warning: Unknown variable: '::nova::vncproxy::vncproxy_protocol'. at
/var/tmp/packstack/2f41026548a941369ed4234e12e1a3a3/modules/nova/manifests/vncproxy/common.pp:36:5
Warning: Unknown variable: '::nova::vncproxy::port'. at
/var/tmp/packstack/2f41026548a941369ed4234e12e1a3a3/modules/nova/manifests/vncproxy/common.pp:41:5
Warning: Unknown variable: '::nova::vncproxy::vncproxy_path'. at
/var/tmp/packstack/2f41026548a941369ed4234e12e1a3a3/modules/nova/manifests/vncproxy/common.pp:46:5
Warning: This method is deprecated, please use the stdlib
validate_legacy function,
with Stdlib::Compat::Bool. There is further
documentation for validate_legacy function in the README. at
["/var/tmp/packstack/2f41026548a941369ed4234e12e1a3a3/modules/nova/manifests/placement.pp",
101]:["/var/tmp/packstack/2f41026548a941369ed4234e12e1a3a3/manifests/10.200.104.32_compute.pp",
26]
(at
/var/tmp/packstack/2f41026548a941369ed4234e12e1a3a3/modules/stdlib/lib/puppet/functions/deprecation.rb:28:in
`deprecation')
Warning: Scope(Class[Nova::Placement]): The os_region_name parameter
is deprecated and will be removed \
in a future release. Please use region_name instead.
Warning: Unknown variable: '::nova::compute::pci_passthrough'. at
/var/tmp/packstack/2f41026548a941369ed4234e12e1a3a3/modules/nova/manifests/compute/pci.pp:19:38
Warning: This method is deprecated, please use the stdlib
validate_legacy function,
with Stdlib::Compat::String. There is further
documentation for validate_legacy function in the README. at
["/var/tmp/packstack/2f41026548a941369ed4234e12e1a3a3/modules/nova/manifests/compute/libvirt.pp",
278]:["/var/tmp/packstack/2f41026548a941369ed4234e12e1a3a3/manifests/10.200.104.32_compute.pp",
32]
(at
/var/tmp/packstack/2f41026548a941369ed4234e12e1a3a3/modules/stdlib/lib/puppet/functions/deprecation.rb:28:in
`deprecation')
Warning: This method is deprecated, please use match expressions with
Stdlib::Compat::Ip_address instead. They are described at
https://docs.puppet.com/puppet/latest/reference/lang_data_type.html#match....
at
["/var/tmp/packstack/2f41026548a941369ed4234e12e1a3a3/modules/nova/manifests/compute/neutron.pp",
31]:["/var/tmp/packstack/2f41026548a941369ed4234e12e1a3a3/manifests/10.200.104.32_compute.pp",
47]
(at
/var/tmp/packstack/2f41026548a941369ed4234e12e1a3a3/modules/stdlib/lib/puppet/functions/deprecation.rb:28:in
`deprecation')
Warning: This method is deprecated, please use match expressions with
Stdlib::Compat::Array instead. They are described at
https://docs.puppet.com/puppet/latest/reference/lang_data_type.html#match....
at
["/var/tmp/packstack/2f41026548a941369ed4234e12e1a3a3/modules/neutron/manifests/init.pp",
492]:["/var/tmp/packstack/2f41026548a941369ed4234e12e1a3a3/manifests/10.200.104.32_compute.pp",
48]
(at
/var/tmp/packstack/2f41026548a941369ed4234e12e1a3a3/modules/stdlib/lib/puppet/functions/deprecation.rb:28:in
`deprecation')
Warning: ModuleLoader: module 'vswitch' has unresolved dependencies -
it will only see those that are resolved. Use 'puppet module list
--tree' to see information about modules
(file & line not available)
Warning: ModuleLoader: module 'mysql' has unresolved dependencies - it
will only see those that are resolved. Use 'puppet module list --tree'
to see information about modules
(file & line not available)
Notice: /Stage[main]/Ceilometer::Deps/Anchor[ceilometer::service::end]:
Triggered 'refresh' from 1 events
Notice: /Stage[main]/Nova::Deps/Anchor[nova::config::end]: Triggered
'refresh' from 21 events
Notice: /Stage[main]/Nova::Deps/Anchor[nova::service::begin]:
Triggered 'refresh' from 1 events
Error: Systemd start for openstack-nova-compute failed!
journalctl log for openstack-nova-compute:
-- Logs begin at Wed 2021-02-10 20:08:31 +0530, end at Wed 2021-02-10
23:34:41 +0530. --
Feb 10 23:34:41 prod-openstack-svr1 systemd[1]:
openstack-nova-compute.service: main process exited, code=exited,
status=1/FAILURE
Feb 10 23:34:41 prod-openstack-svr1 systemd[1]: Failed to start
OpenStack Nova Compute Server.
Feb 10 23:34:41 prod-openstack-svr1 systemd[1]: Unit
openstack-nova-compute.service entered failed state.
Feb 10 23:34:41 prod-openstack-svr1 systemd[1]:
openstack-nova-compute.service failed.
Error:
/Stage[main]/Nova::Compute/Nova::Generic_service[compute]/Service[nova-compute]/ensure:
change from stopped to running failed: Systemd start for
openstack-nova-compute failed!
journalctl log for openstack-nova-compute:
-- Logs begin at Wed 2021-02-10 20:08:31 +0530, end at Wed 2021-02-10
23:34:41 +0530. --
Feb 10 23:34:41 prod-openstack-svr1 systemd[1]:
openstack-nova-compute.service: main process exited, code=exited,
status=1/FAILURE
Feb 10 23:34:41 prod-openstack-svr1 systemd[1]: Failed to start
OpenStack Nova Compute Server.
Feb 10 23:34:41 prod-openstack-svr1 systemd[1]: Unit
openstack-nova-compute.service entered failed state.
Feb 10 23:34:41 prod-openstack-svr1 systemd[1]:
openstack-nova-compute.service failed.
Notice: /Stage[main]/Nova::Compute/Nova::Generic_service[compute]/Service[nova-compute]:
Triggered 'refresh' from 1 events
Notice: /Stage[main]/Nova::Deps/Anchor[nova::service::end]: Dependency
Service[nova-compute] has failures: true
Warning: /Stage[main]/Nova::Deps/Anchor[nova::service::end]: Skipping
because of failed dependencies
Notice: /Stage[main]/Nova::Logging/File[/var/log/nova/nova-manage.log]:
Dependency Service[nova-compute] has failures: true
Warning: /Stage[main]/Nova::Logging/File[/var/log/nova/nova-manage.log]:
Skipping because of failed dependencies
Notice: /Stage[main]/Nova/Exec[networking-refresh]: Dependency
Service[nova-compute] has failures: true
Warning: /Stage[main]/Nova/Exec[networking-refresh]: Skipping because
of failed dependencies
Notice: /Stage[main]/Nova::Cell_v2::Discover_hosts/Exec[nova-cell_v2-discover_hosts]:
Dependency Service[nova-compute] has failures: true
Warning: /Stage[main]/Nova::Cell_v2::Discover_hosts/Exec[nova-cell_v2-discover_hosts]:
Skipping because of failed dependencies
Notice:
/Stage[main]/Neutron::Agents::Ml2::Ovs/Neutron::Plugins::Ovs::Bridge[extnet:br-ex]/Vs_bridge[br-ex]/external_ids:
external_ids changed '' to 'bridge-id=br-ex'
--------------------------------------------------------------------------------
> Installation type's tried: answer files, advanced networking
Have you also tried out basic packstack installation(sudo packstack --allinone) to ensure
it's not related to custom changes in the answer file.
>
> Yum update: tried with yum update & without yum update.
Yes it's better to do a yum update before installation to keep the system up to date
with latest CentOS packages.
>
>
> I did the same installation on Supermicro server with Intel XEON
> Silver 4110 @ 2.10 Ghz using the same set of software's & installation
> methods. No issues found.
>
Considering you have not faced issues in other hardware and different releases failed for
you on DELL360 PowerEdge seems more like hardware related.
> Anybody encountered similar issues? Thanks.
>
> Regards,
> Amey.
> _______________________________________________
> users mailing list
> users(a)lists.rdoproject.org
> http://lists.rdoproject.org/mailman/listinfo/users
>
> To unsubscribe: users-unsubscribe(a)lists.rdoproject.org
Thanks and Regards
Yatin Karel