May 2019 - openstack-discuss - lists.openstack.org

stable/newton devstack installation is failing on ubuntu 14.04.6
by Ansari, Arshad 30 May '19

30 May '19

Hi, I am trying to install stable/newton devstack on Ubuntu 14.04.6 and getting below error:- 2019-05-20 05:21:05.321 | full installdeps: -chttps://git.openstack.org/cgit/openstack/requirements/plain/upper-constraints.txt, -r/opt/stack/tempest/requirements.txt 2019-05-20 05:21:06.347 | 2019-05-20 05:21:06.347 | =================================== log end ==================================== 2019-05-20 05:21:06.347 | ERROR: could not install deps [-chttps://git.openstack.org/cgit/openstack/requirements/plain/upper-constraints.txt, -r/opt/stack/tempest/requirements.txt]; v = InvocationError(u'/opt/stack/tempest/.tox/tempest/bin/pip install -chttps://git.openstack.org/cgit/openstack/requirements/plain/upper-constraints.txt -r/opt/stack/tempest/requirements.txt', 2) 2019-05-20 05:21:06.347 | ___________________________________ summary ____________________________________ 2019-05-20 05:21:06.347 | ERROR: full: could not install deps [-chttps://git.openstack.org/cgit/openstack/requirements/plain/upper-constraints.txt, -r/opt/stack/tempest/requirements.txt]; v = InvocationError(u'/opt/stack/tempest/.tox/tempest/bin/pip install -chttps://git.openstack.org/cgit/openstack/requirements/plain/upper-constraints.txt -r/opt/stack/tempest/requirements.txt', 2) SSLError: hostname 'git.openstack.org' doesn't match either of 'developer.openstack.org', 'www.developer.openstack.org' You are using pip version 8.1.2, however version 19.1.1 is available. Please let me know if other details are required. Thanks, Arshad Alam Ansari

3 3

[rally] Is there a way to log command printout in rally logs?
by Giuseppe Sannino 30 May '19

30 May '19

Hi all, I'm new in Rally, so please apologize in advance if the question is a no-sense. As per the subject, I wonder if there is a way in Rally to collect the printouts from the openstack command execution. For example, when I execute the "NovaHypervisors.list_and_get_hypervisors" scenario I'd like to see and inspect (in a file or on the screen) the actual result of the "nova hypervisor-list" command. Many thanks in advance BR /Giuseppe

1 0

[barbican] dev: Using Barbican for media box/center unattended cert, key (KEK) updates, etc.
by Hunter Nins 30 May '19

30 May '19

Hello, Pardon: the first attempt was html-formatted. I am currently working on a customized media center/box product for my employer. It's basically a Raspberry Pi 3b+ running Raspian, configured to auto-update periodically via `apt`. The device accesses binaries for proprietary applications via a private, secured `apt` repo, using a pre-installed certificate on the device. Right now, the certificate on the device is set to never expire, but going forward, we'd like to configure the certificate to expire every 4 months. We also plan to deploy a unique certificate per device we ship, so the certs can be revoked if the tamper mechanism is triggered (i.e. if the customer rips open the box, it blows a fuse that is attached to a ADC chip, and the device reports in s/w that the sensor has been tripped). Finally, we anticipate some customers leaving the device offline, and only updating once every year (allowing for time for the cert to expire). Is there a way I could use Barbican to: * Update the certs for apt-repo access on the device periodically. * Setup key-encryption-keys (KEK) on the device, if we need the device to be able to download sensitive data, such as an in-memory cached copy of customer info. * Provide a mechanism for a new key to be deployed on the device if the currently-used key has expired (i.e. the user hasn't connected the device to the internet for more than 4 months). * Allow keys to be tracked, revoked, and de-commissioned. Thank you for your time and assistance.

2 3

[Glance] Deprecation and removal of sheepdog store
by Erno Kuvaja 30 May '19

30 May '19

Hola, Due to the stopped development and maintenance of sheepdog [0] we made the call to deprecate the store driver for removal. As the sheepdog job has not been working and there has been no interest to fix it and sheepdog upstream development has dried out as well, we are looking to remove the Glance driver for it at early U. This means that if there is someone who is using the sheepdog store for images, Train will be the last release to fix the driver and fork it for your own repo for your own maintenance. We are also looking into killing the failing test job for the same reason [1] [0] http://lists.wpkg.org/pipermail/sheepdog/2019-March/068451.html [1] https://review.opendev.org/#/c/660450/ Best, Erno "jokke" Kuvaja

1 0

How to migrate a vm to a different project?
by Manuel Sopena Ballesteros 30 May '19

30 May '19

Dear Openstack community, I have one vm under the admin project I would like to migrate to migrate to a different project. Reason is the vm user wants to manage it himself. I have created a project and a user/password for that user and now I need to migrate the vm. I have not been able to find a way to do this, so I was thinking in doing this: Create an image from the vm Shelve the vm (I don't have more hosts to run it because it has a x4 GPUs attached to it and don't have spare host with free resources) Create a new vm based on image as the new user/project Destroy the shelved vm Would this work? Please correct me if there is an easier/safer way of doing this. Thank you very much Manuel Sopena Ballesteros Big Data Engineer | Kinghorn Centre for Clinical Genomics [cid:image001.png@01D4C835.ED3C2230] <https://www.garvan.org.au/> a: 384 Victoria Street, Darlinghurst NSW 2010 p: +61 2 9355 5760 | +61 4 12 123 123 e: manuel.sb(a)garvan.org.au<mailto:manuel.sb@garvan.org.au> Like us on Facebook<http://www.facebook.com/garvaninstitute> | Follow us on Twitter<http://twitter.com/GarvanInstitute> and LinkedIn<http://www.linkedin.com/company/garvan-institute-of-medical-research> NOTICE Please consider the environment before printing this email. This message and any attachments are intended for the addressee named and may contain legally privileged/confidential/copyright information. If you are not the intended recipient, you should not read, use, disclose, copy or distribute this communication. If you have received this message in error please notify us at once by return email and then delete both messages. We accept no liability for the distribution of viruses or similar in electronic communications. This notice should not be removed.

2 1

[monasca] Proposing Akhil Jain for Monasca core team
by Witek Bedyk 30 May '19

30 May '19

Hello team, I would like to propose Akhil Jain to join the Monasca core team. Akhil has added authenticated webhook notification support [1] and worked on integrating Monasca with Congress, where he's also the core reviewer. His work has been presented at the last Open Infrastructure Summit in Denver [2]. Akhil has good understanding of Monasca and OpenStack architecture and constantly helps us in providing sensible reviews. I'm sure Monasca project will benefit from this nomination. Cheers Witek [1] https://storyboard.openstack.org/#!/story/2003105 [2] https://www.openstack.org/summit/denver-2019/summit-schedule/events/23261/p…

4 3

PowerVM-CI is failing while stacking devstack
by Aman Kumar Sinha26 30 May '19

30 May '19

2 1

[nova] Should we have a known issue reno for bug 1829062 in 19.0.1 (stein)?
by Matt Riedemann 29 May '19

29 May '19

I've got a release request for stein 19.0.1 [1] but am holding it up to figure out if we should have a known issue release note for the nova-api + wsgi + eventlet monkey patch bug(s) [2][3]. [4] contains a workaround to disable the eventlet monkeypatching which it sounds like StarlingX is using for now, but is not really something we're recommending for production (setting OS_NOVA_DISABLE_EVENTLET_PATCHING=1). Sean Mooney has another workaround [5]. Should we try to clean that up for a known issue before we release 19.0.1 given it's the first release since the Stein GA? I tend to think "yes". [1] https://review.opendev.org/#/c/661376/ [2] https://bugs.launchpad.net/nova/+bug/1829062 [3] https://bugs.launchpad.net/nova/+bug/1825584 [4] https://review.opendev.org/#/c/647310/ [5] https://bugs.launchpad.net/nova/+bug/1829062/comments/7 -- Thanks, Matt

2 2

OPENSTACK-HELM : INGRESS CONTROLLER PODS STUCK IN PENDING
by Akki yadav 29 May '19

29 May '19

Hello team, I am running the following command in order to deploy the ingress controller: - ./tools/deployment/multinode/020-ingress.sh It makes two pods ingress-error-pages-899888c7-pnxhv and ingress-error-pages-899888c7-w5d5b which remains in pending state and the script ends after 900 seconds stating in "kubectl describe" that : - Warning FailedScheduling 60s (x3 over 2m12s) default-scheduler 0/3 nodes are available: 3 node(s) didn't match node selector. As only default labels are associated with the cluster nodes, do i need to add any specific one ? If yes, Please tell me where and how to add the same. Please guide me how to resolve this issue. Thanks in advance. Regards, Akshay

3 2

[kolla][magnum] Cluster creation failed due to "Waiting for Kubernetes API..."
by Giuseppe Sannino 29 May '19

29 May '19

Hi all, need an help. I deployed an AIO via Kolla on a baremetal node. Here some information about the deployment: --------------- kolla-ansible: 7.0.1 openstack_release: Rocky kolla_base_distro: centos kolla_install_type: source TLS: disabled --------------- VMs spawn without issue but I can't make the "Kubernetes cluster creation" successfully. It fails due to "Time out" I managed to log into Kuber Master and from the cloud-init-output.log I can see: + echo 'Waiting for Kubernetes API...' Waiting for Kubernetes API... ++ curl --silent http://127.0.0.1:8080/healthz + '[' ok = '' ']' + sleep 5 Checking via systemctl and journalctl I see: [fedora@kube-clsuter-qamdealetlbi-master-0 log]$ systemctl status kube-apiserver ● kube-apiserver.service - kubernetes-apiserver Loaded: loaded (/etc/systemd/system/kube-apiserver.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2019-02-19 15:31:41 UTC; 45min ago Process: 3796 ExecStart=/usr/bin/runc --systemd-cgroup run kube-apiserver (code=exited, status=1/FAILURE) Main PID: 3796 (code=exited, status=1/FAILURE) Feb 19 15:31:40 kube-clsuter-qamdealetlbi-master-0.novalocal systemd[1]: kube-apiserver.service: Main process exited, code=exited, status=1/FAILURE Feb 19 15:31:40 kube-clsuter-qamdealetlbi-master-0.novalocal systemd[1]: kube-apiserver.service: Failed with result 'exit-code'. Feb 19 15:31:41 kube-clsuter-qamdealetlbi-master-0.novalocal systemd[1]: kube-apiserver.service: Service RestartSec=100ms expired, scheduling restart. Feb 19 15:31:41 kube-clsuter-qamdealetlbi-master-0.novalocal systemd[1]: kube-apiserver.service: Scheduled restart job, restart counter is at 6. Feb 19 15:31:41 kube-clsuter-qamdealetlbi-master-0.novalocal systemd[1]: Stopped kubernetes-apiserver. Feb 19 15:31:41 kube-clsuter-qamdealetlbi-master-0.novalocal systemd[1]: kube-apiserver.service: Start request repeated too quickly. Feb 19 15:31:41 kube-clsuter-qamdealetlbi-master-0.novalocal systemd[1]: kube-apiserver.service: Failed with result 'exit-code'. Feb 19 15:31:41 kube-clsuter-qamdealetlbi-master-0.novalocal systemd[1]: Failed to start kubernetes-apiserver. [fedora@kube-clsuter-qamdealetlbi-master-0 log]$ sudo journalctl -u kube-apiserver -- Logs begin at Tue 2019-02-19 15:21:36 UTC, end at Tue 2019-02-19 16:17:00 UTC. -- Feb 19 15:31:33 kube-clsuter-qamdealetlbi-master-0.novalocal systemd[1]: Started kubernetes-apiserver. Feb 19 15:31:34 kube-clsuter-qamdealetlbi-master-0.novalocal runc[2794]: Flag --insecure-bind-address has been deprecated, This flag will be removed in a future version. Feb 19 15:31:34 kube-clsuter-qamdealetlbi-master-0.novalocal runc[2794]: Flag --insecure-port has been deprecated, This flag will be removed in a future version. Feb 19 15:31:35 kube-clsuter-qamdealetlbi-master-0.novalocal runc[2794]: Error: error creating self-signed certificates: open /var/run/kubernetes/apiserver.crt: permission denied : : : Feb 19 15:31:35 kube-clsuter-qamdealetlbi-master-0.novalocal runc[2794]: error: error creating self-signed certificates: open /var/run/kubernetes/apiserver.crt: permission denied Feb 19 15:31:35 kube-clsuter-qamdealetlbi-master-0.novalocal systemd[1]: kube-apiserver.service: Main process exited, code=exited, status=1/FAILURE Feb 19 15:31:35 kube-clsuter-qamdealetlbi-master-0.novalocal systemd[1]: kube-apiserver.service: Failed with result 'exit-code'. Feb 19 15:31:35 kube-clsuter-qamdealetlbi-master-0.novalocal systemd[1]: kube-apiserver.service: Service RestartSec=100ms expired, scheduling restart. Feb 19 15:31:35 kube-clsuter-qamdealetlbi-master-0.novalocal systemd[1]: kube-apiserver.service: Scheduled restart job, restart counter is at 1. May I ask for an help on this ? Many thanks /Giuseppe

5 11