Hi Amey,
On Tue, Feb 16, 2021 at 8:40 AM Amey Abhyankar <sco1984(a)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)
To narrow down it further if it's related to horizon itself or other
services:-
- Do you see the same error when launching from CLI?
- Are you able to create vm directly from an image, without bootable volume?
- Can you also check logs for glance api and cinder volume service or share
it here?
- What error do you see when creating a key pair?
- Is the error also while creating the key pair from CLI?
- For this can u also check nova api logs.
Any hints how to fix this?
[root@prod-openstack-svr ~(keystone_admin)]# openstack image list
+--------------------------------------+--------+--------+
| ID | Name | Status |
+--------------------------------------+--------+--------+
| 11568f06-7513-4750-8be6-e531c9829a01 | cirros | active |
+--------------------------------------+--------+--------+
[root@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@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@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@lvm | nova | enabled | up |
2021-02-16T03:08:24.000000 | - | - | up
|
+------------------+------------------------+------+---------+-------+----------------------------+---------+-----------------+---------------+
[root@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@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(a)gmail.com> wrote:
>
> Hi Amey,
>
> On Fri, Feb 12, 2021 at 9:31 PM Amey Abhyankar <sco1984(a)gmail.com>
wrote:
>>
>> Hello Yatin,
>>
>> On Thu, 11 Feb 2021 at 14:17, YATIN KAREL <yatinkarel(a)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(a)lists.rdoproject.org
>> >> >>
http://lists.rdoproject.org/mailman/listinfo/users
>> >> >>
>> >> >> To unsubscribe: users-unsubscribe(a)lists.rdoproject.org
>> >> >
>> >> >
>> >> >
>> >> > Thanks and Regards
>> >> > Yatin Karel
>> >
>> >
>> >
>> > Thanks and Regards
>> > Yatin Karel
>
>
>
> Thanks and Regards
> Yatin Karel