[Starlingx-discuss] Can not launch instance

Wed Jan 23 09:59:30 UTC 2019

Ok, after some other hard working starting with my AMD compute-nodes, i will come back to this problem. if i try to start an instance with any typ of security-group the build/launch will fail:

No valid host was found. There are not enough hosts available. compute-0: (RetryFilter) Previously tried: [[u'compute-0', u'compute-0'], [u'compute-1', u'compute-1']], compute-1: (RetryFilter) Previously tried: [[u'compute-0', u'compute-0'], [u'compute-1

after some research, the problem seems to be to my networks are missing "enable-port-security". so, there is no way (for me) to enable this feature. via horizon there is by default no button/checkbox to handle this and CLI calls doesnt work as well:

$ openstack network create --enable --enable-port-security test
Error while executing command: Unrecognized attribute(s) 'port_security_enabled' (HTTP 400) (Request-ID: req-c673e8e6-bf40-49df-8093-ee8015764672)

same error if i try to update network settings:

$ openstack network set --enable-port-security P1
HttpException: Unrecognized attribute(s) 'port_security_enabled' (HTTP 400) (Request-ID: req-87d63162-80bb-49a2-9987-1bf7e6300e82), Unrecognized attribute(s) 'port_security_enabled'

any hints?

________________________________________
Von: von Hoesslin, Volker
Gesendet: Mittwoch, 21. November 2018 15:04
An: 'Michel Thebeau'
Betreff: AW: [Starlingx-discuss] Can not launch instance

Indeed, but current i'm out of time :( soon, i will come back to this issue...

Thx, volker...

-----Ursprüngliche Nachricht-----
Von: Michel Thebeau [mailto:michel.thebeau at windriver.com]
Gesendet: Mittwoch, 21. November 2018 14:43
An: von Hoesslin, Volker
Betreff: Re: [Starlingx-discuss] Can not launch instance

Hi Volker,

Jim's (James') message inquired about the nova compute log:

"Log into each compute and look for error/exceptions in
/var/log/nova/nova-compute.log at the specific timestamp of launch.  A
similar error message will likely present in the nova-conductor.log (on
the controller).  Depending on the specific error, you may need to dig
into other logs on the compute (eg, /var/log/kern.log,
/var/log/libvirt/qemu/instance-<x>.log, /var/log/libvirt/libvirtd.log,
/var/log/openstack.log, etc). This should give hints.  Some of the logs
are extraneous noise, so focus near the exact timestamp."

If you shared some of that detail we might be able to comment about "a
solution with security groups"

M

On Wed, 2018-11-21 at 10:24 +0000, von Hoesslin, Volker wrote:
> Hi,
> nothing easier than that, basically use the normal instance wizard in
> the horizon and don't make any entries in the step "security groups".
> regardless of that, i would be interested in a solution with security
> groups in the future!
>
> Volker…
>
> Von: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] 
> Gesendet: Dienstag, 20. November 2018 17:33
> An: von Hoesslin, Volker; starlingx
> Betreff: RE: [Starlingx-discuss] Can not launch instance
>
> Hello Volker,
>
> Can you share me the steps to create an instance successfully? I am
> facing the same issue.
>
> Regards.
> Juan Carlos Alonso
>
> From: von Hoesslin, Volker [mailto:Volker.Hoesslin at swsn.de] 
> Sent: Thursday, November 15, 2018 4:25 AM
> To: starlingx <starlingx-discuss at lists.starlingx.io>
> Subject: Re: [Starlingx-discuss] Can not launch instance
>
> cool, thanks for your feedback! i've already read and understood the
> topic with the backing. i'm now so far that it seems to work if I
> create an instance without the security-groups (default-group)
> specification, i don't know why exactly. as far as i've understood it
> now, it's supposed to have something to do with "port-security-
> enabled=false"?
>
> sorry that i got in touch with the group so quickly before i
> exhausted all my possibilities... I promise improvement ;)
>
> Von: Dinescu, Stefan [mailto:Stefan.Dinescu at windriver.com] 
> Gesendet: Donnerstag, 15. November 2018 11:15
> An: volker.von.hoesslin at gmx.de; starlingx
> Betreff: Re: [Starlingx-discuss] Can not launch instance
>
> hello,
>
> Just a few quick questions to eliminate some potential issues (or
> maybe even figure out the issue):
> 1. Are the storage nodes in an available state?
> 2. On the compute nodes, is nova-local configures for remote backing
> as well? To check use "system host-lvg-show compute-0 nova-local" and
> check the "instance_backing" parameter.
> From: volker.von.hoesslin at gmx.de [volker.von.hoesslin at gmx.de]
> Sent: Thursday, November 15, 2018 11:03 AM
> To: starlingx
> Subject: Re: [Starlingx-discuss] Can not launch instance
>
> ok, after download the first official ISO (Cengn-mirror) and
> reinstall the complete starlingX i got the same error. for now, i can
> see some lines in "/var/log/nova/nova-scheduler.log". i have pasted
> here: https://pastebin.com/TbvYwTqu
>
> i really need a running openstack and i am willing to spend money for
> service, please help me guys...
>
> volker...
>
> i don't understand that, either i am the only one who builds a
> starlingX-stack at all or i have to fight very hard for all the
> additional knowledge i need in addition to the install-doku...
> now i have created all necessary components:
> - external network
> - internal network
> - router (add external and internal network)
> - add flavoir (aggregate_instance_extra_specs:storage=remote)
> - add image (cirrOS 0.4.0 RAW/QCOW2)
> - add key pairs
> now i created a new instance (via horizon/CLI), without success. the
> instance is created but it ends in an error-stat :( error messages in
> the horizon GUI are meaningless for me:
>
> Fault
> Message: No valid host was found. There are not enough hosts
> available. compute-0: (RetryFilter) Previously tried: [[u'compute-1',
> u'compute-1'], [u'compute-0', u'compute-0']], compute-1:
> (RetryFilter) Previously tried: [[u'compute-1', u'compute-1'],
> [u'compute-0
> Code: 501
> Details: compute-0: (RetryFilter) Previously tried: [[u'compute-1',
> u'compute-1'], [u'compute-0', u'compute-0']], compute-1:
> (RetryFilter) Previously tried: [[u'compute-1', u'compute-1'],
> [u'compute-0', u'compute-0']]
> Created: Nov. 13, 2018, 11:49 a.m.
>
> ================================================
>
> Alarm UUID: 15f5bc85-de93-4109-a278-425bafc7c997
> Alarm ID: 700.001
> Severity: critical
> Alarm State: set
> Alarm Type: processing-error
> Timestamp: Nov. 13, 2018, 11:49 a.m.
> Suppression:
> Entity Instance ID: tenant=571bfa02-4736-4359-a15d-
> 871224b3b202.instance=3ef09380-47e6-479a-91cc-6813474a183d
> Entity Type ID: tenant.instance
> Probable Cause: underlying-resource-unavailable
> Proposed Repair Action: Manual intervention required
> Service Affecting: True
> Management Affecting: True
> Reason: Instance foobar123 owned by admin has failed to schedule
>
>
> Interesting is, half of the instance is missing: @see: https://imgur.
> com/a/UVmEZhF
> - missing NIC
> - missing IP Addresses
> - missing Security Groups
> - missing Volumes Attached
>
>
> does anyone still have a tip for me? Volker
>
>
> _______________________________________________
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io
> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss