[Starlingx-discuss] Use of sysinv_api_bind_ip and sysinv_api_pxeboot_ip, Difference ?

Tue Nov 27 14:24:38 UTC 2018

Are you trying to manually start sysinv-api.service? This and other controller platform services are managed by SM, as are the floating controller and pxecontroller (169.254.202.2) IP addresses. I’m assuming you have successfully run config_controller? Have you checked the state of services under SM (sudo sm-dump)?

From: Saju M [mailto:sajuptpm at gmail.com]
Sent: Tuesday, November 27, 2018 3:35 AM
To: Penney, Don
Cc: luis.ramirez at opencloud.es; starlingx-discuss at lists.starlingx.io
Subject: Re: [Starlingx-discuss] Use of sysinv_api_bind_ip and sysinv_api_pxeboot_ip, Difference ?

HI,

Thanks Luis and Penny.

1)
I am getting error "Cannot assign requested address" when I start sysinv-api.service.

2018-11-26 08:46:09.324 18046 ERROR oslo.service.wsgi [-] Could not bind to 169.254.202.2:6385<http://169.254.202.2:6385> <===Error

2018-11-26 08:46:09.326 18046 CRITICAL sysinv [-] [Errno 99] Cannot assign requested address
Error: http://paste.openstack.org/show/735998/

2)
I can't ping to 169.254.202.2. Do I miss any network configuration. I am trying "Simplex" mode.

controller-0:~$
controller-0:~$ ping 169.254.202.2
PING 169.254.202.2 (169.254.202.2) 56(84) bytes of data.
^C
--- 169.254.202.2 ping statistics ---
23 packets transmitted, 0 received, 100% packet loss, time 22005ms
3)
Attached "/tmp/config/cgcs_config" and output of "ifconfig -a"
http://dpaste.com/0TW920F

Regards
Saju Madhavan
+91 09535134654

On Tue, Nov 27, 2018 at 3:43 AM Penney, Don <Don.Penney at windriver.com<mailto:Don.Penney at windriver.com>> wrote:
The 169.254.202.2 address is assigned for pxeboot:

controller-0:~$ sudo grep -r 169.254.202.2 /etc 2>/dev/null
/etc/sysinv/sysinv.conf:sysinv_api_pxeboot_ip=169.254.202.2
/etc/dnsmasq.conf:dhcp-range=set:pxeboot,169.254.202.2,169.254.202.254,255.255.255.0,1h
/etc/dnsmasq.conf:dhcp-option=tag:pxeboot,option:dns-server,169.254.202.2
/etc/dnsmasq.conf:dhcp-boot=tag:bios,tag:pxeboot,pxelinux.0,pxecontroller,169.254.202.2
/etc/dnsmasq.conf:dhcp-boot=tag:efi,tag:pxeboot,EFI/grubx64.efi,pxecontroller,169.254.202.2
/etc/hosts:169.254.202.2        pxecontroller

The address gets added to the mgmt interface on the active controller, for responding to pxeboot/dhcp requests from hosts during installation from the active controller. Sysinv binds to the address so that it can respond to limited API queries and notifications that occur during the installation process.

From: Luis Ramirez [mailto:luis.ramirez at opencloud.es<mailto:luis.ramirez at opencloud.es>]
Sent: Monday, November 26, 2018 5:04 PM
To: sajuptpm at gmail.com<mailto:sajuptpm at gmail.com>
Cc: starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>
Subject: Re: [Starlingx-discuss] Use of sysinv_api_bind_ip and sysinv_api_pxeboot_ip, Difference ?

Hi,

This IP is provided by Automatic Private IP Addressing. This process assigns an IP address even in the absence of a DHCP server. If a DISCOVER message is not answered, the client picks a random 16-bit number and prepends it with 169.254.x.x. It performs a gratuitous ARP and assigns that address to itself. It means that the DHCP server is not reachable.

Br,
Luis Rmz<https://www.linkedin.com/in/luisframirez/>
Blockchain, DevOps & Open Source Cloud Solutions Architect
----------------------------------------
Founder & CEO
OpenCloud.es<http://www.opencloud.es/>
luis.ramirez at opencloud.es<mailto:luis.ramirez at opencloud.es>
Skype ID: d.overload
Hangouts: luis.ramirez at opencloud.es<mailto:luis.ramirez at opencloud.es>
[Image removed by sender. ] +34 682 740 973 / [Image removed by sender. ] +39 392 1289553 / [Image removed by sender. ] +49 152 26917722 / Česká republika: +420 774 274 882
-----------------------------------------------------

El lun., 26 nov. 2018 a las 10:39, Saju M (<sajuptpm at gmail.com<mailto:sajuptpm at gmail.com>>) escribió:
HI,

I have noticed that sysinv is trying to listen to 6385 with 2 different IPs.
I dont know, How 169.254.202.2 came in etc/sysinv/sysinv.conf, I could not find that IP in hiera.

Error from /var/log/sysinv.log
==========================
2018-11-26 08:46:09.298 18046 INFO oslo.service.wsgi [-] sysinv_api listening on 0.0.0.0:6385<http://0.0.0.0:6385>
ERROR oslo.service.wsgi [-] Could not bind to 169.254.202.2:6385<http://169.254.202.2:6385>

http://paste.openstack.org/show/735998/

Somebody please explain the use of sysinv_api() and sysinv_pxe()
==========================================
https://github.com/openstack/stx-config/blob/ddb407fccbf5d5490400f21d26973ff5a148d737/sysinv/sysinv/sysinv/sysinv/cmd/api.py#L68

https://github.com/openstack/stx-config/blob/ddb407fccbf5d5490400f21d26973ff5a148d737/sysinv/sysinv/sysinv/sysinv/api/__init__.py#L28

Regards
Saju Madhavan
+91 09535134654
_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss at lists.starlingx.io<mailto:Starlingx-discuss at lists.starlingx.io>
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20181127/cfa32522/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 823 bytes
Desc: image001.jpg
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20181127/cfa32522/attachment-0001.jpg>