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