Bug 1447811

I have exactly same issue on OSP10. Where can I find openstack-packstack-9.0.1-2.el7ost

Currently i have the following installed and yum update doesn't find any new updates
yum list installed *packstack*
Loaded plugins: product-id, search-disabled-repos, subscription-manager
Installed Packages
openstack-packstack.noarch                                    9.0.0-3.el7ost                             @rhel-7-server-openstack-10-devtools-rpms
openstack-packstack-puppet.noarch                             9.0.0-3.el7ost                             @rhel-7-server-openstack-10-devtools-rpms

(In reply to Prabhat from comment #3)
> I have exactly same issue on OSP10. Where can I find
> openstack-packstack-9.0.1-2.el7ost
> 
> Currently i have the following installed and yum update doesn't find any new
> updates
> yum list installed *packstack*
> Loaded plugins: product-id, search-disabled-repos, subscription-manager
> Installed Packages
> openstack-packstack.noarch                                    9.0.0-3.el7ost
> @rhel-7-server-openstack-10-devtools-rpms
> openstack-packstack-puppet.noarch                             9.0.0-3.el7ost
> @rhel-7-server-openstack-10-devtools-rpms

Did you found openstack-packstack-9.0.1-2.el7ost ? Can you share where you got it ?

I found the latest here....

$ sudo yum install -y https://www.rdoproject.org/repos/rdo-release.rpm
$ sudo yum install -y openstack-packstack

(In reply to Prabhat from comment #3)
> I have exactly same issue on OSP10. Where can I find
> openstack-packstack-9.0.1-2.el7ost
> 
> Currently i have the following installed and yum update doesn't find any new
> updates
> yum list installed *packstack*
> Loaded plugins: product-id, search-disabled-repos, subscription-manager
> Installed Packages
> openstack-packstack.noarch                                    9.0.0-3.el7ost
> @rhel-7-server-openstack-10-devtools-rpms
> openstack-packstack-puppet.noarch                             9.0.0-3.el7ost
> @rhel-7-server-openstack-10-devtools-rpms

Package openstack-packstack-9.0.1-2.el7ost is not available in OSP10 repositories yet.

Alfredo,

You know when it will be available? I would like to use OSP10 and nor RDO at the moment

> Package openstack-packstack-9.0.1-2.el7ost is not available in OSP10 repositories yet.

Wile waiting for the fixed package to release,

Comment out below lines in /usr/share/openstack-puppet/modules/packstack/manifests/nova/compute.pp manifest.

'libvirt/live_migration_uri': <--- line 32
value => hiera('CONFIG_NOVA_COMPUTE_MIGRATE_URL'); <--- line 33

and re-run packstack installation.

# vim /usr/share/openstack-puppet/modules/packstack/manifests/nova/compute.pp +32

 28 
 29     nova_config{
 30       'DEFAULT/volume_api_class':
 31         value => 'nova.volume.cinder.API';
 32 #      'libvirt/live_migration_uri':
 33 #        value => hiera('CONFIG_NOVA_COMPUTE_MIGRATE_URL');
 34     }
 35

Thanks, that worked

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:1588

I had nearly the same problem with OSP 14 but it's because I didn't run the:

yum update


ERROR : Error appeared during Puppet run: 192.168.43.110_controller.pp
Error: Evaluation Error: Error while evaluating a Resource Statement, Duplicate declaration: Class[Nova::Pci] is already declared; cannot redeclare at /var/tmp/packstack/09bc94d277bc4638866ed872ea2ce3c6/modules/packstack/manifests/nova/api.pp:37 at /var/tmp/packstack/09bc94d277bc4638866ed872ea2ce3c6/modules/packstack/manifests/nova/api.pp:37:5 on node amer.domain.com

apply again

yum install openstack-selinux --skip-broken
yum install python2* --skip-broken 
yum install *pyparsing* --skip-broken
yum install *urllib3* --skip-broken
yum install *chardet* --skip-broken
yum install *gnocchi* --skip-broken
yum install *puppet* --skip-broken
yum install -y mariadb-server-galera --skip-broken
yum install -y *openvswitch* --skip-broken
#yum install -y openstack.*   #saves time installing with packstack#yum install -y puppet hiera openssh-clients tar nc rubygem-json
yum install -y puppet hiera openssh-clients tar nc rubygem-json --skip-broken
yum install -y *rabbitmq* --skip-broken
yum install -y *ironic* --skip-broken
rpm -q --whatprovides rubygem-json   ###### rubygem-json-1.7.7-20.el7.x86_64


I reran the packstack installation it passed this error

after these commands I installed successfully

OK .. upgraded to 8GB vRAM , 8 cores vCPU, 1 TB vHDD ... because VM crashed at installation because of VCPU failure, and VMDK Error ... unexplainable ..

rebooted , I kept using 4 cores vCPU and upgraded after installation

changed the host to amer.domain.com

I had some problems installing with packstack

executed these lines to overcome:

yum -y install yum-plugin-priorities yum-utils

yum install openstack-selinux --skip-broken
yum install python2* --skip-broken
yum install *pyparsing* --skip-broken
yum install *urllib3* --skip-broken
yum install *chardet* --skip-broken
yum install *gnocchi* --skip-broken
yum install *puppet* --skip-broken
yum install -y mariadb-server-galera --skip-broken
yum install -y *openvswitch* --skip-broken
#yum install -y openstack.*   #saves time installing with packstack#yum install -y puppet hiera openssh-clients tar nc rubygem-json
yum install -y puppet hiera openssh-clients tar nc rubygem-json --skip-broken
yum install -y *rabbitmq* --skip-broken
yum install -y *ironic* --skip-broken
yum update

got this outcome

[amer@amer ~]$ su
Password:
[root@amer amer]#
[root@amer amer]#
[root@amer amer]#
[root@amer amer]# cd /root
[root@amer ~]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eno16777736: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 00:0c:29:37:19:1f brd ff:ff:ff:ff:ff:ff
    inet 192.168.43.110/24 brd 192.168.43.255 scope global eno16777736
       valid_lft forever preferred_lft forever
    inet6 fe80::20c:29ff:fe37:191f/64 scope link
       valid_lft forever preferred_lft forever
3: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 52:54:00:32:ff:42 brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
       valid_lft forever preferred_lft forever
4: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0 state DOWN group default qlen 1000
    link/ether 52:54:00:32:ff:42 brd ff:ff:ff:ff:ff:ff
[root@amer ~]# packstack --anwer-file=/root/answer.txt --timeout=9999999999999 --debug
Usage: packstack [options] [--help]

packstack: error: no such option: --anwer-file
[root@amer ~]# packstack --answer-file=/root/answer.txt --timeout=9999999999999 --debug
Welcome to the Packstack setup utility

The installation log file is available at: /var/tmp/packstack/20190125-234457-Crf41V/openstack-setup.log

Installing:
Clean Up                                             [ DONE ]
Discovering ip protocol version                      [ DONE ]
Setting up ssh keys                                  [ DONE ]
Preparing servers                                    [ DONE ]
Pre installing Puppet and discovering hosts' details [ DONE ]
Preparing pre-install entries                        [ DONE ]
Setting up CACERT                                    [ DONE ]
Preparing AMQP entries                               [ DONE ]
Preparing MariaDB entries                            [ DONE ]
Fixing Keystone LDAP config parameters to be undef if empty[ DONE ]
Preparing Keystone entries                           [ DONE ]
Preparing Glance entries                             [ DONE ]
Checking if the Cinder server has a cinder-volumes vg[ DONE ]
Preparing Cinder entries                             [ DONE ]
Preparing Ironic entries                             [ DONE ]
Preparing Nova API entries                           [ DONE ]
Creating ssh keys for Nova migration                 [ DONE ]
Gathering ssh host keys for Nova migration           [ DONE ]
Preparing Nova Compute entries                       [ DONE ]
Preparing Nova Scheduler entries                     [ DONE ]
Preparing Nova VNC Proxy entries                     [ DONE ]
Preparing OpenStack Network-related Nova entries     [ DONE ]
Preparing Nova Common entries                        [ DONE ]
Preparing Neutron LBaaS Agent entries                [ DONE ]
Preparing Neutron API entries                        [ DONE ]
Preparing Neutron L3 entries                         [ DONE ]
Preparing Neutron L2 Agent entries                   [ DONE ]
Preparing Neutron DHCP Agent entries                 [ DONE ]
Preparing Neutron Metering Agent entries             [ DONE ]
Checking if NetworkManager is enabled and running    [ DONE ]
Preparing OpenStack Client entries                   [ DONE ]
Preparing Horizon entries                            [ DONE ]
Preparing Swift builder entries                      [ DONE ]
Preparing Swift proxy entries                        [ DONE ]
Preparing Swift storage entries                      [ DONE ]
Preparing Heat entries                               [ DONE ]
Preparing Heat CloudFormation API entries            [ DONE ]
Preparing Gnocchi entries                            [ DONE ]
Preparing Redis entries                              [ DONE ]
Preparing Ceilometer entries                         [ DONE ]
Preparing Aodh entries                               [ DONE ]
Preparing Sahara entries                             [ DONE ]
Preparing Puppet manifests                           [ DONE ]
Copying Puppet modules and manifests                 [ DONE ]
Applying 192.168.43.110_controller.pp
192.168.43.110_controller.pp:                        [ DONE ]           
Applying 192.168.43.110_network.pp
192.168.43.110_network.pp:                           [ DONE ]       
Applying 192.168.43.110_compute.pp
192.168.43.110_compute.pp:                           [ DONE ]       
Applying Puppet manifests                            [ DONE ]
Finalizing                                           [ DONE ]

 **** Installation completed successfully ******

Additional information:
 * Time synchronization installation was skipped. Please note that unsynchronized time on server instances might be problem for some OpenStack components.
 * File /root/keystonerc_admin has been created on OpenStack client host 192.168.43.110. To use the command line tools you need to source the file.
 * NOTE : A certificate was generated to be used for ssl, You should change the ssl certificate configured in /etc/httpd/conf.d/ssl.conf on 192.168.43.110 to use a CA signed cert.
 * To access the OpenStack Dashboard browse to https://192.168.43.110/dashboard .
Please, find your login credentials stored in the keystonerc_admin in your home directory.
 * The installation log file is available at: /var/tmp/packstack/20190125-234457-Crf41V/openstack-setup.log
 * The generated manifests are available at: /var/tmp/packstack/20190125-234457-Crf41V/manifests
 * Note temporary directory /var/tmp/packstack/e0153a16b7e74386b4edb3be431d09ee on host 192.168.43.110 was not deleted for debugging purposes.

created the br-ex


I have to source this:

[root@amer ~]# [root@amer ~(keystone_admin)]# cat keystonerc_admin
unset OS_SERVICE_TOKEN
    export OS_USERNAME=admin
    export OS_PASSWORD='orient'
    export OS_AUTH_URL=http://192.168.43.110:5000/v3
    export PS1='[\u@\h \W(keystone_admin)]\$ '

export OS_PROJECT_NAME=admin
export OS_USER_DOMAIN_NAME=Default
export OS_PROJECT_DOMAIN_NAME=Default
export OS_IDENTITY_API_VERSION=3
    [root@amer ~(keystone_admin)]#

I created an External network, Internal network, router .. done

External Interface on the router 192.168.43.163 pingable from windows and VM
Internal Interface on the router 172.17.20.1

ip add route 172.17.0.0/16 via 192.168.43.163

[root@amer ~(keystone_admin)]# ping 192.168.43.163
PING 192.168.43.163 (192.168.43.163) 56(84) bytes of data.
64 bytes from 192.168.43.163: icmp_seq=1 ttl=64 time=1.07 ms
64 bytes from 192.168.43.163: icmp_seq=2 ttl=64 time=0.065 ms
64 bytes from 192.168.43.163: icmp_seq=3 ttl=64 time=0.161 ms
^C
--- 192.168.43.163 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 0.065/0.434/1.077/0.456 ms
[root@amer ~(keystone_admin)]# ping 172.17.20.1
PING 172.17.20.1 (172.17.20.1) 56(84) bytes of data.
64 bytes from 172.17.20.1: icmp_seq=1 ttl=64 time=0.096 ms
64 bytes from 172.17.20.1: icmp_seq=2 ttl=64 time=0.094 ms
64 bytes from 172.17.20.1: icmp_seq=3 ttl=64 time=0.153 ms
^C
--- 172.17.20.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 0.094/0.114/0.153/0.028 ms
[root@amer ~(keystone_admin)]# ping amer
PING amer (192.168.43.110) 56(84) bytes of data.
64 bytes from amer (192.168.43.110): icmp_seq=1 ttl=64 time=0.069 ms
64 bytes from amer (192.168.43.110): icmp_seq=2 ttl=64 time=0.077 ms
^C
--- amer ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 0.069/0.073/0.077/0.004 ms
[root@amer ~(keystone_admin)]#


now the Internal Interface is pingable from VM

created an image for installation ISO for RHEL 7.0,I'm going to use minimal installation for the instance

image created .. it took time uploading .. 3 GB ISO

and saving

Instance created RHEL 7.0 minimal installation

scheduling

Error: Failed to perform requested operation on instance "RHEL 7.0 minimal", the instance has an error status: Please try again later [Error: No valid host was found. ].

[root@amer ~(keystone_admin)]# openstack compute service list
+----+------------------+-----------------+----------+---------+-------+----------------------------+
| ID | Binary           | Host            | Zone     | Status  | State | Updated At                 |
+----+------------------+-----------------+----------+---------+-------+----------------------------+
|  3 | nova-conductor   | amer.domain.com | internal | enabled | up    | 2019-01-26T06:49:44.000000 |
|  4 | nova-scheduler   | amer.domain.com | internal | enabled | up    | 2019-01-26T06:49:43.000000 |
|  5 | nova-consoleauth | amer.domain.com | internal | enabled | up    | 2019-01-26T06:49:39.000000 |
|  6 | nova-compute     | amer.domain.com | nova     | enabled | up    | 2019-01-26T06:49:42.000000 |
+----+------------------+-----------------+----------+---------+-------+----------------------------+
[root@amer ~(keystone_admin)]#

maybe it's the scheduler
or
timeout not set
● openstack-swift-object.service - OpenStack Object Storage (swift) - Object Server
   Loaded: loaded (/usr/lib/systemd/system/openstack-swift-object.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Sat 2019-01-26 00:39:42 EST; 1h 11min ago
  Process: 10826 ExecStart=/usr/bin/swift-object-server /etc/swift/object-server.conf (code=exited, status=1/FAILURE)
 Main PID: 10826 (code=exited, status=1/FAILURE)

Jan 26 00:39:42 amer.domain.com swift-object-server[10826]: File "/usr/lib/python2.7/site-packages/swift/common/wsgi.py"...wsgi
Jan 26 00:39:42 amer.domain.com swift-object-server[10826]: error_msg = strategy.do_bind_ports()
Jan 26 00:39:42 amer.domain.com swift-object-server[10826]: File "/usr/lib/python2.7/site-packages/swift/common/wsgi.py"...orts
Jan 26 00:39:42 amer.domain.com swift-object-server[10826]: self.sock = get_socket(self.conf)
Jan 26 00:39:42 amer.domain.com swift-object-server[10826]: File "/usr/lib/python2.7/site-packages/swift/common/wsgi.py"...cket
Jan 26 00:39:42 amer.domain.com swift-object-server[10826]: 'timeout': bind_timeout})
Jan 26 00:39:42 amer.domain.com swift-object-server[10826]: Exception: Could not bind to 192.168.43.110:6000 after tryin...onds
Jan 26 00:39:42 amer.domain.com systemd[1]: openstack-swift-object.service: main process exited, code=exited, status=1/FAILURE
Jan 26 00:39:42 amer.domain.com systemd[1]: Unit openstack-swift-object.service entered failed state.
Jan 26 00:39:42 amer.domain.com systemd[1]: openstack-swift-object.service failed.

keystone logged out also


why it's not called time to live TTL instead of timeout ... or the nova has no cells for the hosts"