[rdo-users] OpenStack PackStack fails to install in DELL360 PowerEdge

Amey Abhyankar sco1984 at gmail.com
Tue Feb 16 03:16:27 UTC 2021


More information =

- output of "ip a"

[root at prod-openstack-svr ~(keystone_admin)]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: em1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group
default qlen 1000
    link/ether 18:66:da:fb:f4:98 brd ff:ff:ff:ff:ff:ff
3: em2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group
default qlen 1000
    link/ether 18:66:da:fb:f4:99 brd ff:ff:ff:ff:ff:ff
4: em3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group
default qlen 1000
    link/ether 18:66:da:fb:f4:9a brd ff:ff:ff:ff:ff:ff
5: em4: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group
default qlen 1000
    link/ether 18:66:da:fb:f4:9b brd ff:ff:ff:ff:ff:ff
6: p2p1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group
default qlen 1000
    link/ether a0:36:9f:88:44:fc brd ff:ff:ff:ff:ff:ff
7: p2p2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master
ovs-system state UP group default qlen 1000
    link/ether a0:36:9f:88:44:fe brd ff:ff:ff:ff:ff:ff
    inet6 fe80::a236:9fff:fe88:44fe/64 scope link
       valid_lft forever preferred_lft forever
8: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
group default qlen 1000
    link/ether e2:99:54:94:f7:cb brd ff:ff:ff:ff:ff:ff
9: br-int: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group
default qlen 1000
    link/ether 0e:7c:fd:c2:c6:44 brd ff:ff:ff:ff:ff:ff
10: br-ex: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
state UNKNOWN group default qlen 1000
    link/ether a0:36:9f:88:44:fe brd ff:ff:ff:ff:ff:ff
    inet 10.200.104.32/24 brd 10.200.104.255 scope global br-ex
       valid_lft forever preferred_lft forever
    inet6 fe80::7ce5:5eff:fea4:ac40/64 scope link
       valid_lft forever preferred_lft forever
[root at prod-openstack-svr ~(keystone_admin)]#


- output of "getenforce"
[root at prod-openstack-svr ~(keystone_admin)]# getenforce
Disabled

[root at prod-openstack-svr ~(keystone_admin)]# cat /etc/redhat-release
CentOS Linux release 7.9.2009 (Core)
[root at prod-openstack-svr ~(keystone_admin)]# uname -a
Linux prod-openstack-svr 3.10.0-1160.15.2.el7.x86_64 #1 SMP Wed Feb 3
15:06:38 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
[root at prod-openstack-svr ~(keystone_admin)]#


Regards,
Amey.

On Tue, 16 Feb 2021 at 08:40, Amey Abhyankar <sco1984 at gmail.com> wrote:
>
> Hello,
>
> Well it doesn't stop here unfortunately.
> Installation is successful but If I do any actions I get errors.
>
> When I am creating a instance using cirros-0.5.1-x86_64-disk.img from
> Horizon dashboard, I am getting following error =
>
> Block Device Mapping is Invalid: failed to get image
> 11568f06-7513-4750-8be6-e531c9829a01. (HTTP 400) (Request-ID:
> req-c208f78c-d649-482e-8a0c-fc950b127ebe)
>
> Also,
> I am getting error while creating key pair from horizon dashboard.
>
> Any hints how to fix this?
>
> [root at prod-openstack-svr ~(keystone_admin)]# openstack image list
> +--------------------------------------+--------+--------+
> | ID                                   | Name   | Status |
> +--------------------------------------+--------+--------+
> | 11568f06-7513-4750-8be6-e531c9829a01 | cirros | active |
> +--------------------------------------+--------+--------+
>
> [root at prod-openstack-svr ~(keystone_admin)]# nova service-list
> +--------------------------------------+----------------+-----------------------------------+----------+---------+-------+----------------------------+-----------------+-------------+
> | Id                                   | Binary         | Host
>                      | Zone     | Status  | State | Updated_at
>         | Disabled Reason | Forced down |
> +--------------------------------------+----------------+-----------------------------------+----------+---------+-------+----------------------------+-----------------+-------------+
> | 460f8560-476c-4b13-bab9-48db345c51bf | nova-conductor |
> prod-openstack-svr.datametica.com | internal | enabled | up    |
> 2021-02-16T03:07:21.000000 | -               | False       |
> | c1a3c31e-f67b-49f0-96dc-b9870e81e1c4 | nova-scheduler |
> prod-openstack-svr.datametica.com | internal | enabled | up    |
> 2021-02-16T03:07:27.000000 | -               | False       |
> | c1332b4c-6b7f-4927-bb76-83cae19fa51b | nova-compute   |
> prod-openstack-svr.datametica.com | nova     | enabled | up    |
> 2021-02-16T03:07:29.000000 | -               | False       |
> +--------------------------------------+----------------+-----------------------------------+----------+---------+-------+----------------------------+-----------------+-------------+
>
> [root at prod-openstack-svr ~(keystone_admin)]# systemctl status
> openstack-cinder-api
> ● openstack-cinder-api.service - OpenStack Cinder API Server
>    Loaded: loaded
> (/usr/lib/systemd/system/openstack-cinder-api.service; enabled; vendor
> preset: disabled)
>    Active: active (running) since Fri 2021-02-12 19:13:10 IST; 3 days ago
>  Main PID: 2254 (cinder-api)
>     Tasks: 45
>    CGroup: /system.slice/openstack-cinder-api.service
>            ├─ 2254 /usr/bin/python2 /usr/bin/cinder-api --config-file
> /usr/share/cinder/cinder-dist.conf --config-file
> /etc/cinder/cinder.conf --logfile /var/log/cinder/api.log
>            ├─12355 /usr/bin/python2 /usr/bin/cinder-api --config-file
> /usr/share/cinder/cinder-dist.conf --config-file
> /etc/cinder/cinder.conf --logfile /var/log/cinder/api.log
>            ├─12356 /usr/bin/python2 /usr/bin/cinder-api --config-file
> /usr/share/cinder/cinder-dist.conf --config-file
> /etc/cinder/cinder.conf --logfile /var/log/cinder/api.log
>
> [root at prod-openstack-svr ~(keystone_admin)]# cinder service-list
> +------------------+------------------------+------+---------+-------+----------------------------+---------+-----------------+---------------+
> | Binary           | Host                   | Zone | Status  | State |
> Updated_at                 | Cluster | Disabled Reason | Backend State
> |
> +------------------+------------------------+------+---------+-------+----------------------------+---------+-----------------+---------------+
> | cinder-backup    | prod-openstack-svr     | nova | enabled | up    |
> 2021-02-16T03:08:25.000000 | -       | -               |
> |
> | cinder-scheduler | prod-openstack-svr     | nova | enabled | up    |
> 2021-02-16T03:08:25.000000 | -       | -               |
> |
> | cinder-volume    | prod-openstack-svr at lvm | nova | enabled | up    |
> 2021-02-16T03:08:24.000000 | -       | -               | up
> |
> +------------------+------------------------+------+---------+-------+----------------------------+---------+-----------------+---------------+
>
> [root at prod-openstack-svr ~(keystone_admin)]# service neutron-server status
> Redirecting to /bin/systemctl status neutron-server.service
> ● neutron-server.service - OpenStack Neutron Server
>    Loaded: loaded (/usr/lib/systemd/system/neutron-server.service;
> enabled; vendor preset: disabled)
>    Active: active (running) since Fri 2021-02-12 19:13:40 IST; 3 days ago
>  Main PID: 2291 (/usr/bin/python)
>     Tasks: 92
>    CGroup: /system.slice/neutron-server.service
>            ├─ 2291 /usr/bin/python2 /usr/bin/neutron-server
> --config-file /usr/share/neutron/neutron-dist.conf --config-dir
> /usr/share/neutron/server --config-file /etc/neutron/neutron.conf
> --co...
>            ├─12358 /usr/bin/python2 /usr/bin/neutron-server
> --config-file /usr/share/neutron/neutron-dist.conf --config-dir
> /usr/share/neutron/server --config-file /etc/neutron/neutron.conf
> --co...
>            ├─12360 /usr/bin/python2 /usr/bin/neutron-server
> --config-file /usr/share/neutron/neutron-dist.conf --config-dir
> /usr/share/neutron/server --config-file /etc/neutron/neutron.conf
> --co...
>            ├─12362 /usr/bin/python2 /usr/bin/neutron-server
> --config-file /usr/share/neutron/neutron-dist.conf --config-dir
> /usr/share/neutron/server --config-file /etc/neutron/neutron.conf
> --co...
>
> [root at prod-openstack-svr ~(keystone_admin)]# neutron agent-list
> neutron CLI is deprecated and will be removed in the future. Use
> openstack CLI instead.
> +--------------------------------------+----------------------+-----------------------------------+-------------------+-------+----------------+-------------------------------+
> | id                                   | agent_type           | host
>                            | availability_zone | alive |
> admin_state_up | binary                        |
> +--------------------------------------+----------------------+-----------------------------------+-------------------+-------+----------------+-------------------------------+
> | 083285ae-3709-4087-934d-38fd674f1bd0 | OVN Metadata agent   |
> prod-openstack-svr.datametica.com | n/a               | :-)   | True
>         | networking-ovn-metadata-agent |
> | 3e0fcc51-0016-48f4-823c-20b1d070049d | OVN Controller agent |
> prod-openstack-svr.datametica.com | n/a               | :-)   | True
>         | ovn-controller                |
> +--------------------------------------+----------------------+-----------------------------------+-------------------+-------+----------------+-------------------------------+
>
> Regards,
> Amey.
>
> On Fri, 12 Feb 2021 at 22:07, YATIN KAREL <yatinkarel at gmail.com> wrote:
> >
> > Hi Amey,
> >
> > On Fri, Feb 12, 2021 at 9:31 PM Amey Abhyankar <sco1984 at gmail.com> wrote:
> >>
> >> Hello Yatin,
> >>
> >> On Thu, 11 Feb 2021 at 14:17, YATIN KAREL <yatinkarel at gmail.com> wrote:
> >> >
> >> > Hi Amey,
> >> >> >> 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
> >> >snip<
> >> > 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.
> >> When there are no proper errors, it is difficult to troubleshoot.
> >> Finally the issue is resolved.
> >> It was due to the warning of SMT [1] while installing CentOS.
> >> I disabled the logical CPU's in BIOS > Installed CentOS 7 > Installed
> >> packstack Train > All good.
> >> But now I have half of the CPU threads available for use.
> >> Very strange issue BTW of SMT + CentOS kernel + PackStack
> >>
> >> [1] access.redhat.com/solutions/rhel-smt
> >> >
> >
> > Yeap it's a strange issue, good to hear you get it resolved. /me still didn't get why services were failing to start, No idea how to handle it during deployment, If you can share more details wrt Error, Environment details, how you got to identify that SMT was the issue, etc, maybe you can create a bug so we can see if it's possible to handle the issue in packstack itself if it's packstack related.
> >>
> >> > Also you can connect on Freenode IRC channel #rdo where you may get more early responses.
> >> >
> >> >> >> 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 at lists.rdoproject.org
> >> >> >> http://lists.rdoproject.org/mailman/listinfo/users
> >> >> >>
> >> >> >> To unsubscribe: users-unsubscribe at lists.rdoproject.org
> >> >> >
> >> >> >
> >> >> >
> >> >> > Thanks and Regards
> >> >> > Yatin Karel
> >> >
> >> >
> >> >
> >> > Thanks and Regards
> >> > Yatin Karel
> >
> >
> >
> > Thanks and Regards
> > Yatin Karel


More information about the users mailing list