[Starlingx-discuss] StarlingX R2.0 Issues against Green Build dated 17Th July 2019

Andy Ning andy.ning at windriver.com
Wed Jul 31 15:41:11 UTC 2019


Containerized keystone has the following settings:

|lockout_duration = 1800
lockout_failure_attempts = 5

|

So after 1800s the locked user should be unlocked.

Andy


On 2019-07-31 11:33 AM, Bailey, Henry Albert (Al) wrote:
>
> It says that the admin account in his containerized keystone is 
> “locked”  now.
>
> The account is locked for user: 76aca3c3ce404f28a042b366cc2434cd. 
> (HTTP 401) (Request-ID: req-ff102b9d-9afa-4fbc-b5c0-ec2fd46846bc)
>
> What are the steps for Jim to recover?
>
> Al
>
> *From:*Dinescu, Stefan [mailto:Stefan.Dinescu at windriver.com]
> *Sent:* Wednesday, July 31, 2019 11:18 AM
> *To:* Ning, Antai (Andy); starlingx-discuss at lists.starlingx.io
> *Subject:* Re: [Starlingx-discuss] StarlingX R2.0 Issues against Green 
> Build dated 17Th July 2019
>
> Yeah, if you want to use any openstack commands for the 
> containerized/application side you must NOT source the 
> /etc/platform/openrc file at all from the shell, as the expoted 
> variables will interfere with the settings saved in the clouds.yaml file.
>
> ------------------------------------------------------------------------
>
> *From:*Andy Ning [andy.ning at windriver.com]
> *Sent:* Wednesday, July 31, 2019 6:06 PM
> *To:* starlingx-discuss at lists.starlingx.io
> *Subject:* Re: [Starlingx-discuss] StarlingX R2.0 Issues against Green 
> Build dated 17Th July 2019
>
> So if you source /etc/platform/openrc alread, and then export 
> OS_CLOUD=openstack_helm, openstack will try to talk to the keystone 
> pointed to by OS_AUTH_URL and the command will fail. Using 
> OS_CLOUD=openstack_helm before source /etc/platform/openrc, openstack 
> command work for me
>
> Andy
>
> On 2019-07-31 10:49 AM, Andy Ning wrote:
>
>     On 2019-07-31 10:45 AM, Andy Ning wrote:
>
>         On 2019-07-31 10:40 AM, Gauld, James wrote:
>
>             Addendum,
>
>             If I create a modified version of /etc/platform/openrc,
>             and change the following line OS_AUTH_URL, source that
>             file, I can successfully run openstack commands from that
>             shell:
>
>             export
>             OS_AUTH_URL=http://keystone.openstack.svc.cluster.local/v3
>
>             Something not working for me with the
>             /etc/openstack/clouds.yaml, and horizon openstack GUI.
>
>
>         I checked a lab with load BUILD_ID="20190729T233000Z", and I
>         don't see this file exist. Are you sure it exist in your lab?
>
>
>     Sorry, I realized that you have to create such a file ...
>
>
>
>     Andy
>
>
>     -jim
>
>     *From:*Gauld, James
>     *Sent:* July-31-19 9:55 AM
>     *To:* Bailey, Henry Albert (Al); Anirudh Gupta;
>     starlingx-discuss at lists.starlingx.io
>     <mailto:starlingx-discuss at lists.starlingx.io>;
>     starlingx-announce at lists.starlingx.io
>     <mailto:starlingx-announce at lists.starlingx.io>
>     *Subject:* RE: [Starlingx-discuss] StarlingX R2.0 Issues against
>     Green Build dated 17Th July 2019
>
>     Is anyone having problems with openstack commands on recent build?
>
>     I installed a build from late last night, I did "system
>     application-apply stx-openstack" and that was successful, and
>     everything seems running.  I let it sit for several hours.  I
>     created the clouds.yaml as per usual old Wiki.   Then cannot
>     continue with the "Verify the cluster endpoints" step. I cannot do
>     "openstack endpoint list".
>
>     At first I was getting:
>
>     controller-0:~$ openstack endpoint list
>
>     The request you have made requires authentication. (HTTP 401)
>     (Request-ID: req-2e791341-d5e0-4064-9962-eeae6115121d)
>
>     Now I am getting :
>
>     controller-0:~# export OS_CLOUD=openstack_helm
>
>     controller-0:~# openstack endpoint list
>
>     The account is locked for user: 76aca3c3ce404f28a042b366cc2434cd.
>     (HTTP 401) (Request-ID: req-c3e92a3d-b9fa-4cce-92bb-a84d79ed79b0)
>
>     And logging out with fresh environment:
>
>     controller-0:~$ export OS_CLOUD=openstack_helm
>
>     controller-0:~$ openstack endpoint list
>
>     The account is locked for user: 76aca3c3ce404f28a042b366cc2434cd.
>     (HTTP 401) (Request-ID: req-ff102b9d-9afa-4fbc-b5c0-ec2fd46846bc)
>
>     The horizon openstack GUI won't allow me to login, message is
>     "invalid credentials".
>
>     -jim
>
>     *From:*Bailey, Henry Albert (Al) [mailto:Al.Bailey at windriver.com]
>     *Sent:* July-22-19 10:52 AM
>     *To:* Anirudh Gupta; starlingx-discuss at lists.starlingx.io
>     <mailto:starlingx-discuss at lists.starlingx.io>;
>     starlingx-announce at lists.starlingx.io
>     <mailto:starlingx-announce at lists.starlingx.io>
>     *Subject:* Re: [Starlingx-discuss] StarlingX R2.0 Issues against
>     Green Build dated 17Th July 2019
>
>     In order to see the endpoints for nova, neutron, etc.. you need
>      /etc/openstack/clouds.yaml file to be setup.
>
>     The steps you need are  referenced in this (deprecated) document.
>
>     https://wiki.openstack.org/wiki/StarlingX/Containers/Installation#Verify_the_cluster_endpoints
>
>     It will also show the appropriate commands for the provider/tenant
>     networking setup,  until  the official doc is synced with that wiki.
>
>     Al
>
>     *From:*Anirudh Gupta [mailto:Anirudh.Gupta at hsc.com]
>     *Sent:* Friday, July 19, 2019 12:13 AM
>     *To:* starlingx-discuss at lists.starlingx.io
>     <mailto:starlingx-discuss at lists.starlingx.io>;
>     starlingx-announce at lists.starlingx.io
>     <mailto:starlingx-announce at lists.starlingx.io>
>     *Subject:* [Starlingx-discuss] StarlingX R2.0 Issues against Green
>     Build dated 17Th July 2019
>
>     Hi Team,
>
>     I am following the below document to set up AIO-Simplex R2.0 with
>     the green build dated 17-July.
>
>     https://docs.starlingx.io/deploy_install_guides/upcoming/aio_simplex.html
>
>     I have successfully verified the endpoints, using the command
>
>     /openstack endpoint list/
>
>     *Issue 1 :- *
>
>     The endpoint list contains endpoint of the services
>     fm,patching,vim,smapi,keystone,barbacian and sysinv.
>
>     The other basic openstack services are visible if I run
>
>     /kubectl get services -n openstack/
>
>     But, there are no endpoints of nova,neutron,glance and all other
>     openstack services?
>
>     *Issue 2 :-*
>
>     I am unable to proceed further with the set up Provider/tenant
>     networking setup
>     <https://docs.starlingx.io/deploy_install_guides/upcoming/aio_simplex.html#id14>     <https://docs.starlingx.io/deploy_install_guides/upcoming/aio_simplex.html#provider-tenant-networking-setup>
>
>     [root at controller-0 sysadmin(keystone_admin)]# neutron
>     providernet-create ${PHYSNET0} --type vlan
>
>     neutron CLI is deprecated and will be removed in the future. Use
>     openstack CLI instead.
>
>     Unknown command [u'providernet-create', u'--type', u'vlan']
>
>     What could be the solution to proceed further?
>
>     Regards
>
>     Anirudh Gupta
>
>     DISCLAIMER: This electronic message and all of its contents,
>     contains information which is privileged, confidential or
>     otherwise protected from disclosure. The information contained in
>     this electronic mail transmission is intended for use only by the
>     individual or entity to which it is addressed. If you are not the
>     intended recipient or may have received this electronic mail
>     transmission in error, please notify the sender immediately and
>     delete / destroy all copies of this electronic mail transmission
>     without disclosing, copying, distributing, forwarding, printing or
>     retaining any part of it. Hughes Systique accepts no
>     responsibility for loss or damage arising from the use of the
>     information transmitted by this email including damage from virus.
>
>
>
>     _______________________________________________
>
>     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
>
>
>
>     -- 
>
>     Andy Ning
>
>     Cube: 3071
>
>     Tel: 613-9631408 (int: 4408)
>
>     Skype: andy.ning.wr
>
>
>
>     _______________________________________________
>
>     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
>
>
>
>     -- 
>
>     Andy Ning
>
>     Cube: 3071
>
>     Tel: 613-9631408 (int: 4408)
>
>     Skype: andy.ning.wr
>
>
>
>     _______________________________________________
>
>     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
>
>
>
> -- 
> Andy Ning
> Cube: 3071
> Tel: 613-9631408 (int: 4408)
> Skype: andy.ning.wr

-- 
Andy Ning
Cube: 3071
Tel: 613-9631408 (int: 4408)
Skype: andy.ning.wr

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20190731/139af2ba/attachment-0001.html>


More information about the Starlingx-discuss mailing list