December 2019 - openstack-discuss

[octavia][stein issue
by Ignazio Cassano 10 Dec '19

10 Dec '19

Hello, I've just installed stein on centos 7 with octavia. I created the amphora image based on centos , but when a load balance is created the amphora instance does note have any proces on port 9443 and the worker reports: 2019-12-10 08:40:14.456 3710 WARNING octavia.amphorae.drivers.haproxy.rest_api_driver [-] Could not connect to instance. Retrying.: ConnectTimeout: HTTPSConnectionPool(host='10.102.143.94', port=9443): Max retries exceeded with url: // (Caused by ConnectTimeoutError(<urllib3.connection.VerifiedHTTPSConnection object at 0x7f4a04de0d10>, 'Connection to 10.102.143.94 timed out. (connect timeout=10.0)')) Network connectivity and security groups are ok. I connected on the instance via ssh and I cannot see any listening 9443 port. Anyone can help me, please ? Ignazio

2 2

[sahara] Sahara meetings for the rest of 2019 - dates confirmed
by Jeremy Freudberg 10 Dec '19

10 Dec '19

The next Sahara meeting will be December 19, 2019 at 1400 UTC in #openstack-sahara. (There will be no Sahara meeting December 12, 2019 or December 26, 2019.)

1 0

[neutron][queens] dhcp issue
by Ignazio Cassano 10 Dec '19

10 Dec '19

Hello Everyone, I have an openstack queens installation based on centos 7. I created a shared vlan network and multiple subnet under it. When I start an instance on one of the subnet network it gets the correct ip based on its subnet but the gateway seems random (one of the subnet of the vlan). Any suggestion, please ? Ignazio

1 0

[cinder] weekly meeting change reminder
by Brian Rosmaita 10 Dec '19

10 Dec '19

(No, I'm not planning to send this out every week ... this will be the final reminder email.) This is a quick reminder that this week's Cinder meeting will be held as usual on Wednesday, but: new time: 1400 UTC new channel: #openstack-meeting-4 See you there! brian

1 0

[Image-Encryption] No meeting until January
by Josephine Seifert 10 Dec '19

10 Dec '19

Hello, I will have vacation until January, so the next meeting will take place at 6th of Januar. I wish you all nice holidays and a happy new year :)

1 0

[all] OpenStack V Release Naming Poll
by Sean McGinnis 10 Dec '19

10 Dec '19

Hey everyone, This is to officially announce the beginning of the CIVS poll to determine the "V" release name. Since the Train release, we use a public poll. This means that rather than having a unique voting URL for each person, all voting can be done using the following URL: https://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_13ccd49b66cfd1b4&akey=39d9… A public poll can mean that users behind NAT, proxy servers or firewalls may receive an error message saying that your vote has already been lodged. If this happens please try another IP. Voting will officially end December 16, 2019 at 23:59 UTC. The results of the voting will be shared soon afterwards, but keep in mind there will need to be a marketing and legal review of any selected names before it is finalized. Import Note On Name Review -------------------------- There are a couple steps that I am consolidating from our official process [0]. I believe this to be harmless, but if anyone has any concerns about this please do raise them and we can discuss and avoid any issues for future elections. I will be proposing some updates to clarify our election process either way. First, there is a discrete step for marketing review. I believe that can be done as part of the post-voting name review. Second is to consult with the TC to have names removed. I also believe that can be done as part of the post-voting review, but also think that due to past concerns about this process it is best to allow voting on all of the names first, then determine if something is not appropriate. I think this should be more efficient, but ultimately I determined this course of action due to not allowing enough time for step 6 of the process. For that I want to apologize to everyone sincerely. I do think (and hope) this will not be an issue, but again, please do not hesitate to raise concerns about this. Sean [0] https://governance.openstack.org/tc/reference/release-naming.html

4 7

[stein][octavia] api error
by Ignazio Cassano 10 Dec '19

10 Dec '19

Hello All, I've just installed octavia on centos 7 stein, but when I call the octavia command line, the octavia api.log reports: 2019-12-09 22:03:40.986 7925 WARNING keystonemiddleware.auth_token [req-1dea61b8-5c61-4b97-9be5-b1fd8c273984 - - - - -] Identity response: {"error":{"code":401,"message":"The request you have made requires authentication.","title":"Unauthorized"}} : Unauthorized: The request you have made requires authentication. (HTTP 401) (Request-ID: req-4264ea33-ad5c-46a7-99af-def5570e7e47) 2019-12-09 22:03:41.008 7925 WARNING keystonemiddleware.auth_token [req-1dea61b8-5c61-4b97-9be5-b1fd8c273984 - - - - -] Identity response: {"error":{"code":401,"message":"The request you have made requires authentication.","title":"Unauthorized"}} : Unauthorized: The request you have made requires authentication. (HTTP 401) (Request-ID: req-02b07d72-431b-421c-9735-3289228e7df1) 2019-12-09 22:03:41.008 7925 CRITICAL keystonemiddleware.auth_token [req-1dea61b8-5c61-4b97-9be5-b1fd8c273984 - - - - -] Unable to validate token: Identity server rejected authorization necessary to fetch token data: ServiceError: Identity server rejected authorization necessary to fetch token data Please, any help ? Regards Ignazio

1 1

Openstack CI Failing from Friday(6-Dec-2019)
by Sikka, Rishabh 09 Dec '19

09 Dec '19

Dear All , >From Saturday onwards our openstack CI is failing for ISCSI driver at very early stage of devstack setup and for FC driver it is getting queued. Please let us know if there is any changes are done from community end. >From the failure log and last success log we can conclude with below error -: Failure log -: http://54.201.44.218/53/696853/1/check/3par-iscsi-driver-master-client-pip-… + ./stack.sh:main:224 : [[ ! xenial =~ (bionic|stretch|jessie|f29|opensuse-15.0|opensuse-15.1|opensuse-tumbleweed|rhel7) ]] + ./stack.sh:main:225 : echo 'WARNING: this script has not been tested on xenial' WARNING: this script has not been tested on xenial + ./stack.sh:main:226 : [[ '' != \y\e\s ]] + ./stack.sh:main:227 : die 227 'If you wish to run this script anyway run with FORCE=yes' + functions-common:die:195 : local exitcode=0 + functions-common:die:196 : set +o xtrace [Call Trace] ./stack.sh:227:die [ERROR] ./stack.sh:227 If you wish to run this script anyway run with FORCE=yesnon-zero return code ################################## Success log-: http://54.201.44.218/14/685914/9/check/3par-iscsi-driver-master-client-pip-… + ./stack.sh:main:224 : [[ ! xenial =~ (xenial|artful|bionic|stretch|jessie|f29|opensuse-15.0|opensuse-15.1|opensuse-tumbleweed|rhel7) ]] + ./stack.sh:main:235 : export_proxy_variables + functions-common:export_proxy_variables:2154 : isset http_proxy + functions-common:isset:171 : [[ -v http_proxy ]] + functions-common:export_proxy_variables:2155 : export http_proxy=http://192.168.75.1:8118/ + functions-common:export_proxy_variables:2155 : http_proxy=http://192.168.75.1:8118/ + functions-common:export_proxy_variables:2157 : isset https_proxy + functions-common:isset:171 : [[ -v https_proxy ]]

2 1

Re: [sahara] Next Sahara meeting date
by Jeremy Freudberg 09 Dec '19

09 Dec '19

Oops, I meant to write in my original message that 19 Dec is also an option. I think I would also prefer 19 Dec for the date of the next meeting. Let's allow some time for thoughts from the rest of the team but likely I will announce an exceptional meeting for 19 Dec 1400UTC. Not sure if #openstack-meeting-3 is actually available or if we are even allowed to use it for an exceptional meeting. But we can figure that out later... On Mon, Dec 9, 2019 at 1:22 PM Luigi Toscano <ltoscano(a)redhat.com> wrote: > > On Monday, 9 December 2019 17:20:26 CET Jeremy Freudberg wrote: > > As a reminder, the Sahara team currently meets every two weeks. A > > meeting was not held 28 Nov due to the Thanksgiving holiday. A meeting > > will not be held 12 Dec as I am on PTO. > > > > In order to determine the next meeting date we need to answer two questions: > > - Is there desire to meet on 26 Dec, despite the nearby holidays? > > - Is a gap in meetings from 14 Nov to 9 Jan acceptable? > > > > Depending on those answers, the next Sahara meeting will either be on > > 26 Dec or 9 Jan. > > Uhm, could we exceptionally met on Dec 19 ? That would probably solve the > issue. > > I can't totally guarantee to be around on Dec 26, even though it shouldn't be > a big problem, so that's my emergency scenario. > > Ciao > -- > Luigi > >

1 0

[sahara] Next Sahara meeting date
by Jeremy Freudberg 09 Dec '19

09 Dec '19

As a reminder, the Sahara team currently meets every two weeks. A meeting was not held 28 Nov due to the Thanksgiving holiday. A meeting will not be held 12 Dec as I am on PTO. In order to determine the next meeting date we need to answer two questions: - Is there desire to meet on 26 Dec, despite the nearby holidays? - Is a gap in meetings from 14 Nov to 9 Jan acceptable? Depending on those answers, the next Sahara meeting will either be on 26 Dec or 9 Jan. Let me know. Thanks, Jeremy

1 0