From paul.sun at syniverse.com Wed Dec 4 10:35:07 2013 From: paul.sun at syniverse.com (Paul Sun) Date: Wed, 4 Dec 2013 10:35:07 +0000 Subject: [rhos-list] Problem on install packstack Message-ID: <61D7C199BADE404A8DB174EA3BEE0E903393E54B@HKMBX02.ad.syniverse.com> Hi I have a problem on installing Packstack on my environment. IN my setup, I have one controller and two compute node. While executing the packstack command, it has error as below. [root at controller01 network-scripts]# packstack --install-hosts=192.168.206.149,192.168.206.150,192.168.206.152 Welcome to Installer setup utility Installing: Clean Up... [ DONE ] OS support check... [ DONE ] Adding pre install manifest entries... [ DONE ] Setting up ssh keys... [ DONE ] Adding MySQL manifest entries... [ DONE ] Adding QPID manifest entries... [ DONE ] Adding Keystone manifest entries... [ DONE ] Adding Glance Keystone manifest entries... [ DONE ] Adding Glance manifest entries... [ DONE ] Adding Cinder Keystone manifest entries... [ DONE ] Installing dependencies for Cinder... [ DONE ] Checking if the Cinder server has a cinder-volumes vg...[ DONE ] Adding Cinder manifest entries... [ DONE ] Adding Nova API manifest entries... [ DONE ] Adding Nova Keystone manifest entries... [ DONE ] Adding Nova Cert manifest entries... [ DONE ] Adding Nova Conductor manifest entries... [ DONE ] Adding Nova Compute manifest entries... [ DONE ] Adding Nova Scheduler manifest entries... [ DONE ] Adding Nova VNC Proxy manifest entries... [ DONE ] Adding Nova Common manifest entries... [ DONE ] Adding Openstack Network-related Nova manifest entries...[ DONE ] Adding Quantum API manifest entries... [ DONE ] Adding Quantum Keystone manifest entries... [ DONE ] Adding Quantum L3 manifest entries... [ DONE ] Adding Quantum L2 Agent manifest entries... [ DONE ] Adding Quantum DHCP Agent manifest entries... [ DONE ] Adding Quantum Metadata Agent manifest entries... [ DONE ] Adding OpenStack Client manifest entries... [ DONE ] Adding Horizon manifest entries... [ DONE ] Preparing servers... [ DONE ] Adding post install manifest entries... [ DONE ] Installing Dependencies... [ DONE ] Copying Puppet modules and manifests... [ DONE ] Applying Puppet manifests... Applying 192.168.206.149_prescript.pp Applying 192.168.206.150_prescript.pp Applying 192.168.206.152_prescript.pp [ ERROR ] ERROR : Error during puppet run : Error: Command exceeded timeout Please check log file /var/tmp/packstack/20131204-180427-qi6VXM/openstack-setup.log for more information Additional information: * A new answerfile was created in: /root/packstack-answers-20131204-180427.txt * Time synchronization installation was skipped. Please note that unsynchronized time on server instances might be problem for some OpenStack components. * Did not create a cinder volume group, one already existed * To use the command line tools you need to source the file /root/keystonerc_admin created on 192.168.206.149 * To use the console, browse to http://192.168.206.149/dashboard By checking the opentstack-setup.log, it show dns problem, can advise what has been missing during the setup? 2013-12-04 18:25:52::ERROR::ospluginutils::143::root:: Error during remote puppet apply of /var/tmp/packstack/20131204-180427-qi6VXM/manifests/192.168.206.149_prescript.pp 2013-12-04 18:25:52::ERROR::ospluginutils::144::root:: dnsdomainname: Host name lookup failure dnsdomainname: Host name lookup failure dnsdomainname: Host name lookup failure dnsdomainname: Host name lookup failure dnsdomainname: Host name lookup failure dnsdomainname: Host name lookup failure ^[[1;31mWarning: Could not retrieve fact fqdn^[[0m dnsdomainname: Host name lookup failure dnsdomainname: Host name lookup failure dnsdomainname: Host name lookup failure ^[[1;31mError: Command exceeded timeout^[[0m Thanks - paul -------------- next part -------------- An HTML attachment was scrubbed... URL: From Scott.Patterson at solnetsolutions.co.nz Wed Dec 4 15:00:57 2013 From: Scott.Patterson at solnetsolutions.co.nz (Scott.Patterson at solnetsolutions.co.nz) Date: Thu, 5 Dec 2013 04:00:57 +1300 Subject: [rhos-list] AUTO: Scott Patterson is out of the office (returning Mon 09/12/2013) Message-ID: <15002_1386169266_529F43B2_15002_244_1_OF09D92EDD.906F66A1-ONCC257C37.00527C50-CC257C37.00527C50@solnetsolutions.co.nz> I am out of the office from Wed 04/12/2013 until Mon 09/12/2013. If your query is urgent please contact 0800 SOLNET for a response. Kind regards, Scott Patterson Note: This is an automated response to your message "rhos-list Digest, Vol 17, Issue 1" sent on 4/12/2013 11:35:21 p.m.. This is the only notification you will receive while this person is away. Attention: This email may contain information intended for the sole use of the original recipient. Please respect this when sharing or disclosing this email's contents with any third party. If you believe you have received this email in error, please delete it and notify the sender or postmaster at solnetsolutions.co.nz as soon as possible. The content of this email does not necessarily reflect the views of Solnet Solutions Ltd. From paul.sun at syniverse.com Thu Dec 5 06:07:27 2013 From: paul.sun at syniverse.com (Paul Sun) Date: Thu, 5 Dec 2013 06:07:27 +0000 Subject: [rhos-list] Problem on install packstack Message-ID: <61D7C199BADE404A8DB174EA3BEE0E903393EA45@HKMBX02.ad.syniverse.com> Hi Below is the details error when I tried to reun again just now. 2013-12-05 13:56:04::INFO::run_setup::359::root:: Comparing pre- conditions, value: 'yes', and match: 'yes' 2013-12-05 14:01:44::ERROR::ospluginutils::143::root:: Error during remote puppet apply of /var/tmp/packstack/20131205-135604-1v2JP_/manifests/192.168.206.152_prescript.pp 2013-12-05 14:01:44::ERROR::ospluginutils::144::root:: dnsdomainname: Host name lookup failure dnsdomainname: Host name lookup failure dnsdomainname: Host name lookup failure dnsdomainname: Host name lookup failure dnsdomainname: Host name lookup failure dnsdomainname: Host name lookup failure Warning: Could not retrieve fact fqdn dnsdomainname: Host name lookup failure dnsdomainname: Host name lookup failure dnsdomainname: Host name lookup failure Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns: Loaded plugins: priorities, product-id, refresh-packagekit, security, Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns: : subscription-manager Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns: This system is receiving updates from Red Hat Subscription Management. Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns: https://cdn.redhat.com/content/dist/rhel/server/6/6Server/x86_64/rhev-agent/3/os/repodata/repomd.xml: [Errno 14] problem making ssl connection Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns: Trying other mirror. Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns: Error: Cannot retrieve repository metadata (repomd.xml) for repository: rhel-6-server-rhev-agent-rpms. Please verify its path and try again Error: yum update -y kernel iputils iproute returned 1 instead of one of [0] Error: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns: change from notrun to 0 failed: yum update -y kernel iputils iproute returned 1 instead of one of [0] Notice: /Stage[main]/Packstack::Netns/Notify[packstack_info]: Dependency Exec[netns_dependecy_install] has failures: true Warning: /Stage[main]/Packstack::Netns/Notify[packstack_info]: Skipping because of failed dependencies Notice: Finished catalog run in 69.87 seconds 2013-12-05 14:01:44::ERROR::run_setup::912::root:: Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/packstack/installer/run_setup.py", line 896, in main single_step_install(options) File "/usr/lib/python2.6/site-packages/packstack/installer/run_setup.py", line 696, in single_step_install _main(answerfilepath) File "/usr/lib/python2.6/site-packages/packstack/installer/run_setup.py", line 577, in _main runSequences() File "/usr/lib/python2.6/site-packages/packstack/installer/run_setup.py", line 554, in runSequences controller.runAllSequences() File "/usr/lib/python2.6/site-packages/packstack/installer/setup_controller.py", line 90, in runAllSequences sequence.run(self.CONF) File "/usr/lib/python2.6/site-packages/packstack/installer/core/sequences.py", line 105, in run step.run(config=config) File "/usr/lib/python2.6/site-packages/packstack/installer/core/sequences.py", line 52, in run raise SequenceError(str(ex)) SequenceError: Error during puppet run : Notice: /Stage[main]/Packstack::Netns/Exec[netns_dependecy_install]/returns: Error: Cannot retrieve repository metadata (repomd.xml) for repository: rhel-6-server-rhev-agent-rpms. Please verify its path and try again 2013-12-05 14:01:44::INFO::run_setup::598::root:: Removing /var/tmp/packstack/0a18ea8d055a4c8cb938d471d4b8dbf6 on 192.168.206.149 (if it is a remote host) 2013-12-05 14:01:44::INFO::run_setup::598::root:: Removing /var/tmp/packstack/ca850496ab4d4232a1c9cc71a421ff57 on 192.168.206.152 (if it is a remote host) 2013-12-05 14:01:44::INFO::run_setup::598::root:: Removing /var/tmp/packstack/c5408292b58e4092922e4e2744ed9a2e on 192.168.206.150 (if it is a remote host) 2013-12-05 14:01:47::INFO::run_setup::532::root:: * A new answerfile was created in: /root/packstack-answers-20131205-135604.txt 2013-12-05 14:01:47::INFO::run_setup::532::root:: * Time synchronization installation was skipped. Please note that unsynchronized time on server instances might be problem for some OpenStack components. 2013-12-05 14:01:47::INFO::run_setup::532::root:: * Did not create a cinder volume group, one already existed 2013-12-05 14:01:47::INFO::run_setup::532::root:: * To use the command line tools you need to source the file /root/keystonerc_admin created on 192.168.206.149 2013-12-05 14:01:47::INFO::run_setup::532::root:: * To use the console, browse to http://192.168.206.149/dashboard From: Paul Sun Sent: Wednesday, December 04, 2013 6:35 PM To: 'rhos-list at redhat.com' Subject: Problem on install packstack Hi I have a problem on installing Packstack on my environment. IN my setup, I have one controller and two compute node. While executing the packstack command, it has error as below. [root at controller01 network-scripts]# packstack --install-hosts=192.168.206.149,192.168.206.150,192.168.206.152 Welcome to Installer setup utility Installing: Clean Up... [ DONE ] OS support check... [ DONE ] Adding pre install manifest entries... [ DONE ] Setting up ssh keys... [ DONE ] Adding MySQL manifest entries... [ DONE ] Adding QPID manifest entries... [ DONE ] Adding Keystone manifest entries... [ DONE ] Adding Glance Keystone manifest entries... [ DONE ] Adding Glance manifest entries... [ DONE ] Adding Cinder Keystone manifest entries... [ DONE ] Installing dependencies for Cinder... [ DONE ] Checking if the Cinder server has a cinder-volumes vg...[ DONE ] Adding Cinder manifest entries... [ DONE ] Adding Nova API manifest entries... [ DONE ] Adding Nova Keystone manifest entries... [ DONE ] Adding Nova Cert manifest entries... [ DONE ] Adding Nova Conductor manifest entries... [ DONE ] Adding Nova Compute manifest entries... [ DONE ] Adding Nova Scheduler manifest entries... [ DONE ] Adding Nova VNC Proxy manifest entries... [ DONE ] Adding Nova Common manifest entries... [ DONE ] Adding Openstack Network-related Nova manifest entries...[ DONE ] Adding Quantum API manifest entries... [ DONE ] Adding Quantum Keystone manifest entries... [ DONE ] Adding Quantum L3 manifest entries... [ DONE ] Adding Quantum L2 Agent manifest entries... [ DONE ] Adding Quantum DHCP Agent manifest entries... [ DONE ] Adding Quantum Metadata Agent manifest entries... [ DONE ] Adding OpenStack Client manifest entries... [ DONE ] Adding Horizon manifest entries... [ DONE ] Preparing servers... [ DONE ] Adding post install manifest entries... [ DONE ] Installing Dependencies... [ DONE ] Copying Puppet modules and manifests... [ DONE ] Applying Puppet manifests... Applying 192.168.206.149_prescript.pp Applying 192.168.206.150_prescript.pp Applying 192.168.206.152_prescript.pp [ ERROR ] ERROR : Error during puppet run : Error: Command exceeded timeout Please check log file /var/tmp/packstack/20131204-180427-qi6VXM/openstack-setup.log for more information Additional information: * A new answerfile was created in: /root/packstack-answers-20131204-180427.txt * Time synchronization installation was skipped. Please note that unsynchronized time on server instances might be problem for some OpenStack components. * Did not create a cinder volume group, one already existed * To use the command line tools you need to source the file /root/keystonerc_admin created on 192.168.206.149 * To use the console, browse to http://192.168.206.149/dashboard By checking the opentstack-setup.log, it show dns problem, can advise what has been missing during the setup? 2013-12-04 18:25:52::ERROR::ospluginutils::143::root:: Error during remote puppet apply of /var/tmp/packstack/20131204-180427-qi6VXM/manifests/192.168.206.149_prescript.pp 2013-12-04 18:25:52::ERROR::ospluginutils::144::root:: dnsdomainname: Host name lookup failure dnsdomainname: Host name lookup failure dnsdomainname: Host name lookup failure dnsdomainname: Host name lookup failure dnsdomainname: Host name lookup failure dnsdomainname: Host name lookup failure ^[[1;31mWarning: Could not retrieve fact fqdn^[[0m dnsdomainname: Host name lookup failure dnsdomainname: Host name lookup failure dnsdomainname: Host name lookup failure ^[[1;31mError: Command exceeded timeout^[[0m Thanks - paul -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdake at redhat.com Fri Dec 6 18:06:24 2013 From: sdake at redhat.com (Steven Dake) Date: Fri, 06 Dec 2013 11:06:24 -0700 Subject: [rhos-list] Problem on install packstack In-Reply-To: <61D7C199BADE404A8DB174EA3BEE0E903393E54B@HKMBX02.ad.syniverse.com> References: <61D7C199BADE404A8DB174EA3BEE0E903393E54B@HKMBX02.ad.syniverse.com> Message-ID: <52A21220.3090608@redhat.com> On 12/04/2013 03:35 AM, Paul Sun wrote: > > Hi > > I have a problem on installing Packstack on my environment. IN my > setup, I have one controller and two compute node. > > While executing the packstack command, it has error as below. > > [root at controller01 network-scripts]# packstack > --install-hosts=192.168.206.149,192.168.206.150,192.168.206.152 > > Welcome to Installer setup utility > > Installing: > > Clean Up... [ DONE ] > > OS support check... [ DONE ] > > Adding pre install manifest entries... [ DONE ] > > Setting up ssh keys... [ DONE ] > > Adding MySQL manifest entries... [ DONE ] > > Adding QPID manifest entries... [ DONE ] > > Adding Keystone manifest entries... [ DONE ] > > Adding Glance Keystone manifest entries... [ DONE ] > > Adding Glance manifest entries... [ DONE ] > > Adding Cinder Keystone manifest entries... [ DONE ] > > Installing dependencies for Cinder... [ DONE ] > > Checking if the Cinder server has a cinder-volumes vg...[ DONE ] > > Adding Cinder manifest entries... [ DONE ] > > Adding Nova API manifest entries... [ DONE ] > > Adding Nova Keystone manifest entries... [ DONE ] > > Adding Nova Cert manifest entries... [ DONE ] > > Adding Nova Conductor manifest entries... [ DONE ] > > Adding Nova Compute manifest entries... [ DONE ] > > Adding Nova Scheduler manifest entries... [ DONE ] > > Adding Nova VNC Proxy manifest entries... [ DONE ] > > Adding Nova Common manifest entries... [ DONE ] > > Adding Openstack Network-related Nova manifest entries...[ DONE ] > > Adding Quantum API manifest entries... [ DONE ] > > Adding Quantum Keystone manifest entries... [ DONE ] > > Adding Quantum L3 manifest entries... [ DONE ] > > Adding Quantum L2 Agent manifest entries... [ DONE ] > > Adding Quantum DHCP Agent manifest entries... [ DONE ] > > Adding Quantum Metadata Agent manifest entries... [ DONE ] > > Adding OpenStack Client manifest entries... [ DONE ] > > Adding Horizon manifest entries... [ DONE ] > > Preparing servers... [ DONE ] > > Adding post install manifest entries... [ DONE ] > > Installing Dependencies... [ DONE ] > > Copying Puppet modules and manifests... [ DONE ] > > Applying Puppet manifests... > > Applying 192.168.206.149_prescript.pp > > Applying 192.168.206.150_prescript.pp > > Applying 192.168.206.152_prescript.pp > > [ ERROR ] > > ERROR : Error during puppet run : Error: Command exceeded timeout > > Please check log file > /var/tmp/packstack/20131204-180427-qi6VXM/openstack-setup.log for more > information > > Additional information: > > * A new answerfile was created in: > /root/packstack-answers-20131204-180427.txt > > * Time synchronization installation was skipped. Please note that > unsynchronized time on server instances might be problem for some > OpenStack components. > > * Did not create a cinder volume group, one already existed > > * To use the command line tools you need to source the file > /root/keystonerc_admin created on 192.168.206.149 > > * To use the console, browse to http://192.168.206.149/dashboard > > By checking the opentstack-setup.log, it show dns problem, can advise > what has been missing during the setup? > > 2013-12-04 18:25:52::ERROR::ospluginutils::143::root:: Error during > remote puppet apply of > /var/tmp/packstack/20131204-180427-qi6VXM/manifests/192.168.206.149_prescript.pp > > 2013-12-04 18:25:52::ERROR::ospluginutils::144::root:: dnsdomainname: > Host name lookup failure > > dnsdomainname: Host name lookup failure > > dnsdomainname: Host name lookup failure > > dnsdomainname: Host name lookup failure > > dnsdomainname: Host name lookup failure > > dnsdomainname: Host name lookup failure > > ^[[1;31mWarning: Could not retrieve fact fqdn^[[0m > > dnsdomainname: Host name lookup failure > > dnsdomainname: Host name lookup failure > > dnsdomainname: Host name lookup failure > > ^[[1;31mError: Command exceeded timeout^[[0m > Paul, My first guess is /etc/resolv.conf is not properly configured to point to your DNS servers. Try the following on the machine that is failing: wget http://openstack.redhat.com This should store the web page at the above address on your installed machine. If this wget operation doesn't complete, try root causing your DNS issues first by looking at resolv.conf then checking your network. Regards -steve > Thanks > > -paul > > > > _______________________________________________ > rhos-list mailing list > rhos-list at redhat.com > https://www.redhat.com/mailman/listinfo/rhos-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From rohara at redhat.com Sun Dec 8 22:09:04 2013 From: rohara at redhat.com (Ryan O'Hara) Date: Sun, 8 Dec 2013 16:09:04 -0600 Subject: [rhos-list] Problem on install packstack In-Reply-To: <52A21220.3090608@redhat.com> References: <61D7C199BADE404A8DB174EA3BEE0E903393E54B@HKMBX02.ad.syniverse.com> <52A21220.3090608@redhat.com> Message-ID: <20131208220904.GB1559@redhat.com> On Fri, Dec 06, 2013 at 11:06:24AM -0700, Steven Dake wrote: > On 12/04/2013 03:35 AM, Paul Sun wrote: > > > >Hi > > > >I have a problem on installing Packstack on my environment. IN my > >setup, I have one controller and two compute node. > > > >While executing the packstack command, it has error as below. > > > >[root at controller01 network-scripts]# packstack > >--install-hosts=192.168.206.149,192.168.206.150,192.168.206.152 > > > >Welcome to Installer setup utility > > > >Installing: > > > >Clean Up... [ DONE ] > > > >OS support check... [ DONE ] > > > >Adding pre install manifest entries... [ DONE ] > > > >Setting up ssh keys... [ DONE ] > > > >Adding MySQL manifest entries... [ DONE ] > > > >Adding QPID manifest entries... [ DONE ] > > > >Adding Keystone manifest entries... [ DONE ] > > > >Adding Glance Keystone manifest entries... [ DONE ] > > > >Adding Glance manifest entries... [ DONE ] > > > >Adding Cinder Keystone manifest entries... [ DONE ] > > > >Installing dependencies for Cinder... [ DONE ] > > > >Checking if the Cinder server has a cinder-volumes vg...[ DONE ] > > > >Adding Cinder manifest entries... [ DONE ] > > > >Adding Nova API manifest entries... [ DONE ] > > > >Adding Nova Keystone manifest entries... [ DONE ] > > > >Adding Nova Cert manifest entries... [ DONE ] > > > >Adding Nova Conductor manifest entries... [ DONE ] > > > >Adding Nova Compute manifest entries... [ DONE ] > > > >Adding Nova Scheduler manifest entries... [ DONE ] > > > >Adding Nova VNC Proxy manifest entries... [ DONE ] > > > >Adding Nova Common manifest entries... [ DONE ] > > > >Adding Openstack Network-related Nova manifest entries...[ DONE ] > > > >Adding Quantum API manifest entries... [ DONE ] > > > >Adding Quantum Keystone manifest entries... [ DONE ] > > > >Adding Quantum L3 manifest entries... [ DONE ] > > > >Adding Quantum L2 Agent manifest entries... [ DONE ] > > > >Adding Quantum DHCP Agent manifest entries... [ DONE ] > > > >Adding Quantum Metadata Agent manifest entries... [ DONE ] > > > >Adding OpenStack Client manifest entries... [ DONE ] > > > >Adding Horizon manifest entries... [ DONE ] > > > >Preparing servers... [ DONE ] > > > >Adding post install manifest entries... [ DONE ] > > > >Installing Dependencies... [ DONE ] > > > >Copying Puppet modules and manifests... [ DONE ] > > > >Applying Puppet manifests... > > > >Applying 192.168.206.149_prescript.pp > > > >Applying 192.168.206.150_prescript.pp > > > >Applying 192.168.206.152_prescript.pp > > > >[ ERROR ] > > > >ERROR : Error during puppet run : Error: Command exceeded timeout > > > >Please check log file > >/var/tmp/packstack/20131204-180427-qi6VXM/openstack-setup.log for > >more information > > > >Additional information: > > > >* A new answerfile was created in: > >/root/packstack-answers-20131204-180427.txt > > > >* Time synchronization installation was skipped. Please note that > >unsynchronized time on server instances might be problem for some > >OpenStack components. > > > >* Did not create a cinder volume group, one already existed > > > >* To use the command line tools you need to source the file > >/root/keystonerc_admin created on 192.168.206.149 > > > >* To use the console, browse to http://192.168.206.149/dashboard > > > >By checking the opentstack-setup.log, it show dns problem, can > >advise what has been missing during the setup? > > > >2013-12-04 18:25:52::ERROR::ospluginutils::143::root:: Error > >during remote puppet apply of /var/tmp/packstack/20131204-180427-qi6VXM/manifests/192.168.206.149_prescript.pp > > > >2013-12-04 18:25:52::ERROR::ospluginutils::144::root:: > >dnsdomainname: Host name lookup failure > > > >dnsdomainname: Host name lookup failure > > > >dnsdomainname: Host name lookup failure > > > >dnsdomainname: Host name lookup failure > > > >dnsdomainname: Host name lookup failure > > > >dnsdomainname: Host name lookup failure > > > >^[[1;31mWarning: Could not retrieve fact fqdn^[[0m > > > >dnsdomainname: Host name lookup failure > > > >dnsdomainname: Host name lookup failure > > > >dnsdomainname: Host name lookup failure > > > >^[[1;31mError: Command exceeded timeout^[[0m > > Run 'hostname --fqdn' on each node and be sure that you are actually getting an fqdn for the nodes. Also run 'facter fqdn' and make sure the output is not blank. Although you are using packstack, this same problem can arise when using foreman. There is a bit of documentation on this issue on the Foreman doc on the RDO wiki: http://openstack.redhat.com/Virtualized_Foreman_Dev_Setup#Hostname_and_FQDN Ryan > Paul, > > My first guess is /etc/resolv.conf is not properly configured to > point to your DNS servers. Try the following on the machine that is > failing: > > wget http://openstack.redhat.com > > This should store the web page at the above address on your > installed machine. If this wget operation doesn't complete, try > root causing your DNS issues first by looking at resolv.conf then > checking your network. > > Regards > -steve > > >Thanks > > > >-paul > > > > > > > >_______________________________________________ > >rhos-list mailing list > >rhos-list at redhat.com > >https://www.redhat.com/mailman/listinfo/rhos-list > > _______________________________________________ > rhos-list mailing list > rhos-list at redhat.com > https://www.redhat.com/mailman/listinfo/rhos-list From paul.sun at syniverse.com Mon Dec 9 01:15:07 2013 From: paul.sun at syniverse.com (Paul Sun) Date: Mon, 9 Dec 2013 01:15:07 +0000 Subject: [rhos-list] Problem on install packstack In-Reply-To: <20131208220904.GB1559@redhat.com> References: <61D7C199BADE404A8DB174EA3BEE0E903393E54B@HKMBX02.ad.syniverse.com> <52A21220.3090608@redhat.com> <20131208220904.GB1559@redhat.com> Message-ID: <61D7C199BADE404A8DB174EA3BEE0E903393FEC1@HKMBX02.ad.syniverse.com> Hi The problem is fixed by putting the servers to DMZ. In previous setup the server is behinf DMZ and ICMP is not allowed, I believed the software thought the cdn.redhat.com is unreachable. I suggested we should add notes in the documentation. -----Original Message----- From: Ryan O'Hara [mailto:rohara at redhat.com] Sent: Monday, December 09, 2013 6:09 AM To: Steven Dake Cc: Paul Sun; rhos-list at redhat.com Subject: Re: [rhos-list] Problem on install packstack On Fri, Dec 06, 2013 at 11:06:24AM -0700, Steven Dake wrote: > On 12/04/2013 03:35 AM, Paul Sun wrote: > > > >Hi > > > >I have a problem on installing Packstack on my environment. IN my > >setup, I have one controller and two compute node. > > > >While executing the packstack command, it has error as below. > > > >[root at controller01 network-scripts]# packstack > >--install-hosts=192.168.206.149,192.168.206.150,192.168.206.152 > > > >Welcome to Installer setup utility > > > >Installing: > > > >Clean Up... [ DONE ] > > > >OS support check... [ DONE ] > > > >Adding pre install manifest entries... [ DONE ] > > > >Setting up ssh keys... [ DONE ] > > > >Adding MySQL manifest entries... [ DONE ] > > > >Adding QPID manifest entries... [ DONE ] > > > >Adding Keystone manifest entries... [ DONE ] > > > >Adding Glance Keystone manifest entries... [ DONE ] > > > >Adding Glance manifest entries... [ DONE ] > > > >Adding Cinder Keystone manifest entries... [ DONE ] > > > >Installing dependencies for Cinder... [ DONE ] > > > >Checking if the Cinder server has a cinder-volumes vg...[ DONE ] > > > >Adding Cinder manifest entries... [ DONE ] > > > >Adding Nova API manifest entries... [ DONE ] > > > >Adding Nova Keystone manifest entries... [ DONE ] > > > >Adding Nova Cert manifest entries... [ DONE ] > > > >Adding Nova Conductor manifest entries... [ DONE ] > > > >Adding Nova Compute manifest entries... [ DONE ] > > > >Adding Nova Scheduler manifest entries... [ DONE ] > > > >Adding Nova VNC Proxy manifest entries... [ DONE ] > > > >Adding Nova Common manifest entries... [ DONE ] > > > >Adding Openstack Network-related Nova manifest entries...[ DONE ] > > > >Adding Quantum API manifest entries... [ DONE ] > > > >Adding Quantum Keystone manifest entries... [ DONE ] > > > >Adding Quantum L3 manifest entries... [ DONE ] > > > >Adding Quantum L2 Agent manifest entries... [ DONE ] > > > >Adding Quantum DHCP Agent manifest entries... [ DONE ] > > > >Adding Quantum Metadata Agent manifest entries... [ DONE ] > > > >Adding OpenStack Client manifest entries... [ DONE ] > > > >Adding Horizon manifest entries... [ DONE ] > > > >Preparing servers... [ DONE ] > > > >Adding post install manifest entries... [ DONE ] > > > >Installing Dependencies... [ DONE ] > > > >Copying Puppet modules and manifests... [ DONE ] > > > >Applying Puppet manifests... > > > >Applying 192.168.206.149_prescript.pp > > > >Applying 192.168.206.150_prescript.pp > > > >Applying 192.168.206.152_prescript.pp > > > >[ ERROR ] > > > >ERROR : Error during puppet run : Error: Command exceeded timeout > > > >Please check log file > >/var/tmp/packstack/20131204-180427-qi6VXM/openstack-setup.log for > >more information > > > >Additional information: > > > >* A new answerfile was created in: > >/root/packstack-answers-20131204-180427.txt > > > >* Time synchronization installation was skipped. Please note that > >unsynchronized time on server instances might be problem for some > >OpenStack components. > > > >* Did not create a cinder volume group, one already existed > > > >* To use the command line tools you need to source the file > >/root/keystonerc_admin created on 192.168.206.149 > > > >* To use the console, browse to http://192.168.206.149/dashboard > > > >By checking the opentstack-setup.log, it show dns problem, can advise > >what has been missing during the setup? > > > >2013-12-04 18:25:52::ERROR::ospluginutils::143::root:: Error during > >remote puppet apply of > >/var/tmp/packstack/20131204-180427-qi6VXM/manifests/192.168.206.149_p > >rescript.pp > > > >2013-12-04 18:25:52::ERROR::ospluginutils::144::root:: > >dnsdomainname: Host name lookup failure > > > >dnsdomainname: Host name lookup failure > > > >dnsdomainname: Host name lookup failure > > > >dnsdomainname: Host name lookup failure > > > >dnsdomainname: Host name lookup failure > > > >dnsdomainname: Host name lookup failure > > > >^[[1;31mWarning: Could not retrieve fact fqdn^[[0m > > > >dnsdomainname: Host name lookup failure > > > >dnsdomainname: Host name lookup failure > > > >dnsdomainname: Host name lookup failure > > > >^[[1;31mError: Command exceeded timeout^[[0m > > Run 'hostname --fqdn' on each node and be sure that you are actually getting an fqdn for the nodes. Also run 'facter fqdn' and make sure the output is not blank. Although you are using packstack, this same problem can arise when using foreman. There is a bit of documentation on this issue on the Foreman doc on the RDO wiki: http://openstack.redhat.com/Virtualized_Foreman_Dev_Setup#Hostname_and_FQDN Ryan > Paul, > > My first guess is /etc/resolv.conf is not properly configured to point > to your DNS servers. Try the following on the machine that is > failing: > > wget http://openstack.redhat.com > > This should store the web page at the above address on your installed > machine. If this wget operation doesn't complete, try root causing > your DNS issues first by looking at resolv.conf then checking your > network. > > Regards > -steve > > >Thanks > > > >-paul > > > > > > > >_______________________________________________ > >rhos-list mailing list > >rhos-list at redhat.com > >https://www.redhat.com/mailman/listinfo/rhos-list > > _______________________________________________ > rhos-list mailing list > rhos-list at redhat.com > https://www.redhat.com/mailman/listinfo/rhos-list From paul.sun at syniverse.com Mon Dec 9 06:16:24 2013 From: paul.sun at syniverse.com (Paul Sun) Date: Mon, 9 Dec 2013 06:16:24 +0000 Subject: [rhos-list] Problem on creating an instance in PackStack Message-ID: <61D7C199BADE404A8DB174EA3BEE0E9033940137@HKMBX02.ad.syniverse.com> Hi I have problem on creating an instance. By following the "Getting Started Guide" Section 6.5, the instance is kept at state=Build, task=Spawning. Tried to check the "Log" and "Console", I obtained "Unable to get log for instance "1e9aaaa4-242e-4da5-b9cb-3deb33246f24"." and "console is currently unavailable. Please try again later." Status respectively. Any idea? From paul.sun at syniverse.com Mon Dec 9 06:45:18 2013 From: paul.sun at syniverse.com (Paul Sun) Date: Mon, 9 Dec 2013 06:45:18 +0000 Subject: [rhos-list] Request correct procedure to create network Message-ID: <61D7C199BADE404A8DB174EA3BEE0E903394018B@HKMBX02.ad.syniverse.com> Hi What is the correct procedure to create Network in Packstack. Referring to section 6.4 in Red Hat OpenStack - Getting Started Guide, we need to create network, however, it doesn't really mentioned what I should do. IN my setup, I have three interfaces, one is used for remote access and running packstack command, how I should configure the other two? One should be external and the other one should be internal, rite? Do I need to pre-configure the interface in OS level beforehand? -------------- next part -------------- An HTML attachment was scrubbed... URL: From hateya at redhat.com Mon Dec 9 19:27:12 2013 From: hateya at redhat.com (Haim Ateya) Date: Mon, 9 Dec 2013 14:27:12 -0500 (EST) Subject: [rhos-list] Problem on creating an instance in PackStack In-Reply-To: <61D7C199BADE404A8DB174EA3BEE0E9033940137@HKMBX02.ad.syniverse.com> References: <61D7C199BADE404A8DB174EA3BEE0E9033940137@HKMBX02.ad.syniverse.com> Message-ID: <7E54A8FB-6446-4881-B185-E54EFC05BD2C@redhat.com> Packstack or openstack? It could very (lots can go wrong there ..,) we must get the logs in order to determine what happened. Could you please archive all nova related logs and attach? Haim > On Dec 9, 2013, at 8:16, Paul Sun wrote: > > Hi > > I have problem on creating an instance. By following the "Getting Started Guide" Section 6.5, the instance is kept at state=Build, task=Spawning. Tried to check the "Log" and "Console", I obtained "Unable to get log for instance "1e9aaaa4-242e-4da5-b9cb-3deb33246f24"." and "console is currently unavailable. Please try again later." Status respectively. > > Any idea? > > _______________________________________________ > rhos-list mailing list > rhos-list at redhat.com > https://www.redhat.com/mailman/listinfo/rhos-list From paul.sun at syniverse.com Tue Dec 10 00:56:59 2013 From: paul.sun at syniverse.com (Paul Sun) Date: Tue, 10 Dec 2013 00:56:59 +0000 Subject: [rhos-list] Problem on creating an instance in PackStack In-Reply-To: <7E54A8FB-6446-4881-B185-E54EFC05BD2C@redhat.com> References: <61D7C199BADE404A8DB174EA3BEE0E9033940137@HKMBX02.ad.syniverse.com> <7E54A8FB-6446-4881-B185-E54EFC05BD2C@redhat.com> Message-ID: <61D7C199BADE404A8DB174EA3BEE0E903394056D@HKMBX02.ad.syniverse.com> Hi The instance can be started as active, but I am failed to connect it using ssh. I am really not sure how to setup the network. In my setup, I run the Packstack on VM with one controller and two compute nodes. I use the quick start installation method to create the system. After finished the network setup in the dashboard, I tried to create the instance, and the instance status is active with IP assigned, but I am not able to connect it. Should I needed to create bridge interface and assign IP address beforehand? -----Original Message----- From: Haim Ateya [mailto:hateya at redhat.com] Sent: Tuesday, December 10, 2013 3:27 AM To: Paul Sun Cc: rhos-list at redhat.com Subject: Re: [rhos-list] Problem on creating an instance in PackStack Packstack or openstack? It could very (lots can go wrong there ..,) we must get the logs in order to determine what happened. Could you please archive all nova related logs and attach? Haim > On Dec 9, 2013, at 8:16, Paul Sun wrote: > > Hi > > I have problem on creating an instance. By following the "Getting Started Guide" Section 6.5, the instance is kept at state=Build, task=Spawning. Tried to check the "Log" and "Console", I obtained "Unable to get log for instance "1e9aaaa4-242e-4da5-b9cb-3deb33246f24"." and "console is currently unavailable. Please try again later." Status respectively. > > Any idea? > > _______________________________________________ > rhos-list mailing list > rhos-list at redhat.com > https://www.redhat.com/mailman/listinfo/rhos-list From paul.sun at syniverse.com Tue Dec 10 03:00:49 2013 From: paul.sun at syniverse.com (Paul Sun) Date: Tue, 10 Dec 2013 03:00:49 +0000 Subject: [rhos-list] Problem on creating an instance in PackStack In-Reply-To: <61D7C199BADE404A8DB174EA3BEE0E903394056D@HKMBX02.ad.syniverse.com> References: <61D7C199BADE404A8DB174EA3BEE0E9033940137@HKMBX02.ad.syniverse.com> <7E54A8FB-6446-4881-B185-E54EFC05BD2C@redhat.com> <61D7C199BADE404A8DB174EA3BEE0E903394056D@HKMBX02.ad.syniverse.com> Message-ID: <61D7C199BADE404A8DB174EA3BEE0E9033940612@HKMBX02.ad.syniverse.com> HI This is the log from dashboard. Any idea? NET: Registered protocol family 10 lo: Disabled Privacy Extensions Bringing up loopback interface: [60G[[0;32m OK [0;39m] Bringing up interface eth0: Determining IP information for eth0... done. [60G[[0;32m OK [0;39m] Starting system logger: [60G[[0;32m OK [0;39m] Starting rpcbind: [60G[[0;32m OK [0;39m] Starting NFS statd: [60G[[0;32m OK [0;39m] Mounting filesystems: [60G[[0;32m OK [0;39m] Starting acpi daemon: [60G[[0;32m OK [0;39m] Retrigger failed udev events[60G[[0;32m OK [0;39m] Starting cloud-init: Cloud-init v. 0.7.2 running 'init-local' at Tue, 10 Dec 2013 07:58:49 +0000. Up 420.73 seconds. Starting cloud-init: Cloud-init v. 0.7.2 running 'init' at Tue, 10 Dec 2013 07:59:16 +0000. Up 447.65 seconds. ci-info: +++++++++++++++++++++++Net device info+++++++++++++++++++++++ ci-info: +--------+------+-----------+-----------+-------------------+ ci-info: | Device | Up | Address | Mask | Hw-Address | ci-info: +--------+------+-----------+-----------+-------------------+ ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | . | ci-info: | eth0 | True | . | . | fa:16:3e:35:a5:d9 | ci-info: +--------+------+-----------+-----------+-------------------+ ci-info: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Route info failed!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 2013-12-10 02:59:29,661 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [0/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:30,797 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [1/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:31,892 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [2/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:33,011 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [3/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:34,084 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [5/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:35,149 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [6/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:37,216 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [8/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:39,289 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [10/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:41,351 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [12/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:43,419 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [14/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:45,484 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [16/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:48,579 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [19/120s]: request error [[Errno 101] Network is unreachable] -----Original Message----- From: rhos-list-bounces at redhat.com [mailto:rhos-list-bounces at redhat.com] On Behalf Of Paul Sun Sent: Tuesday, December 10, 2013 8:57 AM To: Haim Ateya; rhos-list at redhat.com Subject: Re: [rhos-list] Problem on creating an instance in PackStack Hi The instance can be started as active, but I am failed to connect it using ssh. I am really not sure how to setup the network. In my setup, I run the Packstack on VM with one controller and two compute nodes. I use the quick start installation method to create the system. After finished the network setup in the dashboard, I tried to create the instance, and the instance status is active with IP assigned, but I am not able to connect it. Should I needed to create bridge interface and assign IP address beforehand? -----Original Message----- From: Haim Ateya [mailto:hateya at redhat.com] Sent: Tuesday, December 10, 2013 3:27 AM To: Paul Sun Cc: rhos-list at redhat.com Subject: Re: [rhos-list] Problem on creating an instance in PackStack Packstack or openstack? It could very (lots can go wrong there ..,) we must get the logs in order to determine what happened. Could you please archive all nova related logs and attach? Haim > On Dec 9, 2013, at 8:16, Paul Sun wrote: > > Hi > > I have problem on creating an instance. By following the "Getting Started Guide" Section 6.5, the instance is kept at state=Build, task=Spawning. Tried to check the "Log" and "Console", I obtained "Unable to get log for instance "1e9aaaa4-242e-4da5-b9cb-3deb33246f24"." and "console is currently unavailable. Please try again later." Status respectively. > > Any idea? > > _______________________________________________ > rhos-list mailing list > rhos-list at redhat.com > https://www.redhat.com/mailman/listinfo/rhos-list _______________________________________________ rhos-list mailing list rhos-list at redhat.com https://www.redhat.com/mailman/listinfo/rhos-list From paul.sun at syniverse.com Wed Dec 11 00:53:20 2013 From: paul.sun at syniverse.com (Paul Sun) Date: Wed, 11 Dec 2013 00:53:20 +0000 Subject: [rhos-list] Problem on creating an instance in PackStack In-Reply-To: <61D7C199BADE404A8DB174EA3BEE0E9033940612@HKMBX02.ad.syniverse.com> References: <61D7C199BADE404A8DB174EA3BEE0E9033940137@HKMBX02.ad.syniverse.com> <7E54A8FB-6446-4881-B185-E54EFC05BD2C@redhat.com> <61D7C199BADE404A8DB174EA3BEE0E903394056D@HKMBX02.ad.syniverse.com> <61D7C199BADE404A8DB174EA3BEE0E9033940612@HKMBX02.ad.syniverse.com> Message-ID: <61D7C199BADE404A8DB174EA3BEE0E9033940E1A@HKMBX02.ad.syniverse.com> Hi Is there anyone can help? -----Original Message----- From: Paul Sun Sent: Tuesday, December 10, 2013 11:01 AM To: Paul Sun; Haim Ateya; rhos-list at redhat.com Subject: RE: [rhos-list] Problem on creating an instance in PackStack HI This is the log from dashboard. Any idea? NET: Registered protocol family 10 lo: Disabled Privacy Extensions Bringing up loopback interface: [60G[[0;32m OK [0;39m] Bringing up interface eth0: Determining IP information for eth0... done. [60G[[0;32m OK [0;39m] Starting system logger: [60G[[0;32m OK [0;39m] Starting rpcbind: [60G[[0;32m OK [0;39m] Starting NFS statd: [60G[[0;32m OK [0;39m] Mounting filesystems: [60G[[0;32m OK [0;39m] Starting acpi daemon: [60G[[0;32m OK [0;39m] Retrigger failed udev events[60G[[0;32m OK [0;39m] Starting cloud-init: Cloud-init v. 0.7.2 running 'init-local' at Tue, 10 Dec 2013 07:58:49 +0000. Up 420.73 seconds. Starting cloud-init: Cloud-init v. 0.7.2 running 'init' at Tue, 10 Dec 2013 07:59:16 +0000. Up 447.65 seconds. ci-info: +++++++++++++++++++++++Net device info+++++++++++++++++++++++ ci-info: +--------+------+-----------+-----------+-------------------+ ci-info: | Device | Up | Address | Mask | Hw-Address | ci-info: +--------+------+-----------+-----------+-------------------+ ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | . | ci-info: | eth0 | True | . | . | fa:16:3e:35:a5:d9 | ci-info: +--------+------+-----------+-----------+-------------------+ ci-info: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Route info failed!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 2013-12-10 02:59:29,661 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [0/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:30,797 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [1/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:31,892 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [2/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:33,011 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [3/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:34,084 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [5/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:35,149 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [6/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:37,216 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [8/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:39,289 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [10/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:41,351 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [12/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:43,419 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [14/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:45,484 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [16/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:48,579 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [19/120s]: request error [[Errno 101] Network is unreachable] -----Original Message----- From: rhos-list-bounces at redhat.com [mailto:rhos-list-bounces at redhat.com] On Behalf Of Paul Sun Sent: Tuesday, December 10, 2013 8:57 AM To: Haim Ateya; rhos-list at redhat.com Subject: Re: [rhos-list] Problem on creating an instance in PackStack Hi The instance can be started as active, but I am failed to connect it using ssh. I am really not sure how to setup the network. In my setup, I run the Packstack on VM with one controller and two compute nodes. I use the quick start installation method to create the system. After finished the network setup in the dashboard, I tried to create the instance, and the instance status is active with IP assigned, but I am not able to connect it. Should I needed to create bridge interface and assign IP address beforehand? -----Original Message----- From: Haim Ateya [mailto:hateya at redhat.com] Sent: Tuesday, December 10, 2013 3:27 AM To: Paul Sun Cc: rhos-list at redhat.com Subject: Re: [rhos-list] Problem on creating an instance in PackStack Packstack or openstack? It could very (lots can go wrong there ..,) we must get the logs in order to determine what happened. Could you please archive all nova related logs and attach? Haim > On Dec 9, 2013, at 8:16, Paul Sun wrote: > > Hi > > I have problem on creating an instance. By following the "Getting Started Guide" Section 6.5, the instance is kept at state=Build, task=Spawning. Tried to check the "Log" and "Console", I obtained "Unable to get log for instance "1e9aaaa4-242e-4da5-b9cb-3deb33246f24"." and "console is currently unavailable. Please try again later." Status respectively. > > Any idea? > > _______________________________________________ > rhos-list mailing list > rhos-list at redhat.com > https://www.redhat.com/mailman/listinfo/rhos-list _______________________________________________ rhos-list mailing list rhos-list at redhat.com https://www.redhat.com/mailman/listinfo/rhos-list From jon at rosslug.org.uk Wed Dec 11 11:19:26 2013 From: jon at rosslug.org.uk (Jonathan Archer) Date: Wed, 11 Dec 2013 11:19:26 +0000 Subject: [rhos-list] Problem on creating an instance in PackStack In-Reply-To: <61D7C199BADE404A8DB174EA3BEE0E9033940E1A@HKMBX02.ad.syniverse.com> References: <61D7C199BADE404A8DB174EA3BEE0E9033940137@HKMBX02.ad.syniverse.com> <7E54A8FB-6446-4881-B185-E54EFC05BD2C@redhat.com> <61D7C199BADE404A8DB174EA3BEE0E903394056D@HKMBX02.ad.syniverse.com> <61D7C199BADE404A8DB174EA3BEE0E9033940612@HKMBX02.ad.syniverse.com> <61D7C199BADE404A8DB174EA3BEE0E9033940E1A@HKMBX02.ad.syniverse.com> Message-ID: <56e897623aad5b3f59539e31cb797ce6@home.bravo20.co.uk> Hi Paul, I take it you are trying to connect from a client on an existing (physical?) network? Have you setup your public network to extend an existing network? similar to this? http://openstack.redhat.com/Neutron_with_existing_external_network [3] or are you using a new subnet? if new have you got a route to this? and set the firewall up as in the quickstart guides? are you spawning instances logged in as the admin user? if so try logging in with the demo user. >From the error messages you post it looks like there is a problem with your networking side of things. Hope this helps some? or at least starts the ball rolling. Cheers Jon On 2013-12-11 00:53, Paul Sun wrote: > Hi > > Is there anyone can help? > > -----Original Message----- > From: Paul Sun > Sent: Tuesday, December 10, 2013 11:01 AM > To: Paul Sun; Haim Ateya; rhos-list at redhat.com > Subject: RE: [rhos-list] Problem on creating an instance in PackStack > > HI > > This is the log from dashboard. Any idea? > > NET: Registered protocol family 10 > lo: Disabled Privacy Extensions > Bringing up loopback interface: [60G[[0;32m OK [0;39m] Bringing up interface eth0: > Determining IP information for eth0... done. > [60G[[0;32m OK [0;39m] > Starting system logger: [60G[[0;32m OK [0;39m] Starting rpcbind: [60G[[0;32m OK [0;39m] Starting NFS statd: [60G[[0;32m OK [0;39m] Mounting filesystems: [60G[[0;32m OK [0;39m] Starting acpi daemon: [60G[[0;32m OK [0;39m] Retrigger failed udev events[60G[[0;32m OK [0;39m] Starting cloud-init: Cloud-init v. 0.7.2 running 'init-local' at Tue, 10 Dec 2013 07:58:49 +0000. Up 420.73 seconds. > Starting cloud-init: Cloud-init v. 0.7.2 running 'init' at Tue, 10 Dec 2013 07:59:16 +0000. Up 447.65 seconds. > ci-info: +++++++++++++++++++++++Net device info+++++++++++++++++++++++ > ci-info: +--------+------+-----------+-----------+-------------------+ > ci-info: | Device | Up | Address | Mask | Hw-Address | > ci-info: +--------+------+-----------+-----------+-------------------+ > ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | . | > ci-info: | eth0 | True | . | . | fa:16:3e:35:a5:d9 | > ci-info: +--------+------+-----------+-----------+-------------------+ > ci-info: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Route info failed!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > 2013-12-10 02:59:29,661 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [2]' failed [0/120s]: request error [[Errno 101] Network is unreachable] > 2013-12-10 02:59:30,797 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [2]' failed [1/120s]: request error [[Errno 101] Network is unreachable] > 2013-12-10 02:59:31,892 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [2]' failed [2/120s]: request error [[Errno 101] Network is unreachable] > 2013-12-10 02:59:33,011 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [2]' failed [3/120s]: request error [[Errno 101] Network is unreachable] > 2013-12-10 02:59:34,084 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [2]' failed [5/120s]: request error [[Errno 101] Network is unreachable] > 2013-12-10 02:59:35,149 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [2]' failed [6/120s]: request error [[Errno 101] Network is unreachable] > 2013-12-10 02:59:37,216 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [2]' failed [8/120s]: request error [[Errno 101] Network is unreachable] > 2013-12-10 02:59:39,289 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [2]' failed [10/120s]: request error [[Errno 101] Network is unreachable] > 2013-12-10 02:59:41,351 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [2]' failed [12/120s]: request error [[Errno 101] Network is unreachable] > 2013-12-10 02:59:43,419 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [2]' failed [14/120s]: request error [[Errno 101] Network is unreachable] > 2013-12-10 02:59:45,484 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [2]' failed [16/120s]: request error [[Errno 101] Network is unreachable] > 2013-12-10 02:59:48,579 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [2]' failed [19/120s]: request error [[Errno 101] Network is unreachable] > > -----Original Message----- > From: rhos-list-bounces at redhat.com [mailto:rhos-list-bounces at redhat.com] On Behalf Of Paul Sun > Sent: Tuesday, December 10, 2013 8:57 AM > To: Haim Ateya; rhos-list at redhat.com > Subject: Re: [rhos-list] Problem on creating an instance in PackStack > > Hi > > The instance can be started as active, but I am failed to connect it using ssh. I am really not sure how to setup the network. > > In my setup, I run the Packstack on VM with one controller and two compute nodes. I use the quick start installation method to create the system. > > After finished the network setup in the dashboard, I tried to create the instance, and the instance status is active with IP assigned, but I am not able to connect it. > > Should I needed to create bridge interface and assign IP address beforehand? > > -----Original Message----- > From: Haim Ateya [mailto:hateya at redhat.com] > Sent: Tuesday, December 10, 2013 3:27 AM > To: Paul Sun > Cc: rhos-list at redhat.comSubject: Re: [rhos-list] Problem on creating an instance in PackStack > > Packstack or openstack? It could very (lots can go wrong there ..,) we must get the logs in order to determine what happened. > > Could you please archive all nova related logs and attach? > > Haim > >> On Dec 9, 2013, at 8:16, Paul Sun wrote: Hi I have problem on creating an instance. By following the "Getting Started Guide" Section 6.5, the instance is kept at state=Build, task=Spawning. Tried to check the "Log" and "Console", I obtained "Unable to get log for instance "1e9aaaa4-242e-4da5-b9cb-3deb33246f24"." and "console is currently unavailable. Please try again later." Status respectively. Any idea? _______________________________________________ rhos-list mailing list rhos-list at redhat.com https://www.redhat.com/mailman/listinfo/rhos-list [1] > > _______________________________________________ > rhos-list mailing list > rhos-list at redhat.com > https://www.redhat.com/mailman/listinfo/rhos-list [1] > > _______________________________________________ > rhos-list mailing list > rhos-list at redhat.com > https://www.redhat.com/mailman/listinfo/rhos-list [1] Links: ------ [1] https://www.redhat.com/mailman/listinfo/rhos-list [2] http://169.254.169.254/2009-04-04/meta-data/instance-id [3] http://openstack.redhat.com/Neutron_with_existing_external_network -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.sun at syniverse.com Thu Dec 12 01:22:08 2013 From: paul.sun at syniverse.com (Paul Sun) Date: Thu, 12 Dec 2013 01:22:08 +0000 Subject: [rhos-list] Problem on creating an instance in PackStack In-Reply-To: <56e897623aad5b3f59539e31cb797ce6@home.bravo20.co.uk> References: <61D7C199BADE404A8DB174EA3BEE0E9033940137@HKMBX02.ad.syniverse.com> <7E54A8FB-6446-4881-B185-E54EFC05BD2C@redhat.com> <61D7C199BADE404A8DB174EA3BEE0E903394056D@HKMBX02.ad.syniverse.com> <61D7C199BADE404A8DB174EA3BEE0E9033940612@HKMBX02.ad.syniverse.com> <61D7C199BADE404A8DB174EA3BEE0E9033940E1A@HKMBX02.ad.syniverse.com> <56e897623aad5b3f59539e31cb797ce6@home.bravo20.co.uk> Message-ID: <61D7C199BADE404A8DB174EA3BEE0E9033941441@HKMBX02.ad.syniverse.com> Hi Jon Thank for your reply. My setup is a new setup, and I run the PackStack on Esxi machine. There are totally having three nodes, one of them as a controller. There are three interfaces on each node. From your information, it seems that we need to prepare the interface to serve as bridge interface, I would like to give a try later. The documentation from Packstack never instruct user to prepare this, so I am wondering this is required or not. From: rhos-list-bounces at redhat.com [mailto:rhos-list-bounces at redhat.com] On Behalf Of Jonathan Archer Sent: Wednesday, December 11, 2013 7:19 PM To: rhos-list at redhat.com Subject: Re: [rhos-list] Problem on creating an instance in PackStack Hi Paul, I take it you are trying to connect from a client on an existing (physical?) network? Have you setup your public network to extend an existing network? similar to this? http://openstack.redhat.com/Neutron_with_existing_external_network or are you using a new subnet? if new have you got a route to this? and set the firewall up as in the quickstart guides? are you spawning instances logged in as the admin user? if so try logging in with the demo user. From the error messages you post it looks like there is a problem with your networking side of things. Hope this helps some? or at least starts the ball rolling. Cheers Jon On 2013-12-11 00:53, Paul Sun wrote: Hi Is there anyone can help? -----Original Message----- From: Paul Sun Sent: Tuesday, December 10, 2013 11:01 AM To: Paul Sun; Haim Ateya; rhos-list at redhat.com Subject: RE: [rhos-list] Problem on creating an instance in PackStack HI This is the log from dashboard. Any idea? NET: Registered protocol family 10 lo: Disabled Privacy Extensions Bringing up loopback interface: [60G[[0;32m OK [0;39m] Bringing up interface eth0: Determining IP information for eth0... done. [60G[[0;32m OK [0;39m] Starting system logger: [60G[[0;32m OK [0;39m] Starting rpcbind: [60G[[0;32m OK [0;39m] Starting NFS statd: [60G[[0;32m OK [0;39m] Mounting filesystems: [60G[[0;32m OK [0;39m] Starting acpi daemon: [60G[[0;32m OK [0;39m] Retrigger failed udev events[60G[[0;32m OK [0;39m] Starting cloud-init: Cloud-init v. 0.7.2 running 'init-local' at Tue, 10 Dec 2013 07:58:49 +0000. Up 420.73 seconds. Starting cloud-init: Cloud-init v. 0.7.2 running 'init' at Tue, 10 Dec 2013 07:59:16 +0000. Up 447.65 seconds. ci-info: +++++++++++++++++++++++Net device info+++++++++++++++++++++++ ci-info: +--------+------+-----------+-----------+-------------------+ ci-info: | Device | Up | Address | Mask | Hw-Address | ci-info: +--------+------+-----------+-----------+-------------------+ ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | . | ci-info: | eth0 | True | . | . | fa:16:3e:35:a5:d9 | ci-info: +--------+------+-----------+-----------+-------------------+ ci-info: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Route info failed!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 2013-12-10 02:59:29,661 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [0/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:30,797 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [1/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:31,892 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [2/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:33,011 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [3/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:34,084 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [5/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:35,149 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [6/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:37,216 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [8/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:39,289 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [10/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:41,351 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [12/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:43,419 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [14/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:45,484 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [16/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:48,579 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [19/120s]: request error [[Errno 101] Network is unreachable] -----Original Message----- From: rhos-list-bounces at redhat.com [mailto:rhos-list-bounces at redhat.com] On Behalf Of Paul Sun Sent: Tuesday, December 10, 2013 8:57 AM To: Haim Ateya; rhos-list at redhat.com Subject: Re: [rhos-list] Problem on creating an instance in PackStack Hi The instance can be started as active, but I am failed to connect it using ssh. I am really not sure how to setup the network. In my setup, I run the Packstack on VM with one controller and two compute nodes. I use the quick start installation method to create the system. After finished the network setup in the dashboard, I tried to create the instance, and the instance status is active with IP assigned, but I am not able to connect it. Should I needed to create bridge interface and assign IP address beforehand? -----Original Message----- From: Haim Ateya [mailto:hateya at redhat.com] Sent: Tuesday, December 10, 2013 3:27 AM To: Paul Sun Cc: rhos-list at redhat.comSubject: Re: [rhos-list] Problem on creating an instance in PackStack Packstack or openstack? It could very (lots can go wrong there ..,) we must get the logs in order to determine what happened. Could you please archive all nova related logs and attach? Haim On Dec 9, 2013, at 8:16, Paul Sun > wrote: Hi I have problem on creating an instance. By following the "Getting Started Guide" Section 6.5, the instance is kept at state=Build, task=Spawning. Tried to check the "Log" and "Console", I obtained "Unable to get log for instance "1e9aaaa4-242e-4da5-b9cb-3deb33246f24"." and "console is currently unavailable. Please try again later." Status respectively. Any idea? _______________________________________________ rhos-list mailing list rhos-list at redhat.com https://www.redhat.com/mailman/listinfo/rhos-list _______________________________________________ rhos-list mailing list rhos-list at redhat.com https://www.redhat.com/mailman/listinfo/rhos-list _______________________________________________ rhos-list mailing list rhos-list at redhat.com https://www.redhat.com/mailman/listinfo/rhos-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.sun at syniverse.com Thu Dec 12 01:29:46 2013 From: paul.sun at syniverse.com (Paul Sun) Date: Thu, 12 Dec 2013 01:29:46 +0000 Subject: [rhos-list] Problem on creating an instance in PackStack In-Reply-To: <61D7C199BADE404A8DB174EA3BEE0E9033941441@HKMBX02.ad.syniverse.com> References: <61D7C199BADE404A8DB174EA3BEE0E9033940137@HKMBX02.ad.syniverse.com> <7E54A8FB-6446-4881-B185-E54EFC05BD2C@redhat.com> <61D7C199BADE404A8DB174EA3BEE0E903394056D@HKMBX02.ad.syniverse.com> <61D7C199BADE404A8DB174EA3BEE0E9033940612@HKMBX02.ad.syniverse.com> <61D7C199BADE404A8DB174EA3BEE0E9033940E1A@HKMBX02.ad.syniverse.com> <56e897623aad5b3f59539e31cb797ce6@home.bravo20.co.uk> <61D7C199BADE404A8DB174EA3BEE0E9033941441@HKMBX02.ad.syniverse.com> Message-ID: <61D7C199BADE404A8DB174EA3BEE0E903394146E@HKMBX02.ad.syniverse.com> But one serious question, in my installation, neutron is not installed from the packstack command. Why? From: rhos-list-bounces at redhat.com [mailto:rhos-list-bounces at redhat.com] On Behalf Of Paul Sun Sent: Thursday, December 12, 2013 9:22 AM To: jon at rosslug.org.uk; rhos-list at redhat.com Subject: Re: [rhos-list] Problem on creating an instance in PackStack Hi Jon Thank for your reply. My setup is a new setup, and I run the PackStack on Esxi machine. There are totally having three nodes, one of them as a controller. There are three interfaces on each node. From your information, it seems that we need to prepare the interface to serve as bridge interface, I would like to give a try later. The documentation from Packstack never instruct user to prepare this, so I am wondering this is required or not. From: rhos-list-bounces at redhat.com [mailto:rhos-list-bounces at redhat.com] On Behalf Of Jonathan Archer Sent: Wednesday, December 11, 2013 7:19 PM To: rhos-list at redhat.com Subject: Re: [rhos-list] Problem on creating an instance in PackStack Hi Paul, I take it you are trying to connect from a client on an existing (physical?) network? Have you setup your public network to extend an existing network? similar to this? http://openstack.redhat.com/Neutron_with_existing_external_network or are you using a new subnet? if new have you got a route to this? and set the firewall up as in the quickstart guides? are you spawning instances logged in as the admin user? if so try logging in with the demo user. From the error messages you post it looks like there is a problem with your networking side of things. Hope this helps some? or at least starts the ball rolling. Cheers Jon On 2013-12-11 00:53, Paul Sun wrote: Hi Is there anyone can help? -----Original Message----- From: Paul Sun Sent: Tuesday, December 10, 2013 11:01 AM To: Paul Sun; Haim Ateya; rhos-list at redhat.com Subject: RE: [rhos-list] Problem on creating an instance in PackStack HI This is the log from dashboard. Any idea? NET: Registered protocol family 10 lo: Disabled Privacy Extensions Bringing up loopback interface: [60G[[0;32m OK [0;39m] Bringing up interface eth0: Determining IP information for eth0... done. [60G[[0;32m OK [0;39m] Starting system logger: [60G[[0;32m OK [0;39m] Starting rpcbind: [60G[[0;32m OK [0;39m] Starting NFS statd: [60G[[0;32m OK [0;39m] Mounting filesystems: [60G[[0;32m OK [0;39m] Starting acpi daemon: [60G[[0;32m OK [0;39m] Retrigger failed udev events[60G[[0;32m OK [0;39m] Starting cloud-init: Cloud-init v. 0.7.2 running 'init-local' at Tue, 10 Dec 2013 07:58:49 +0000. Up 420.73 seconds. Starting cloud-init: Cloud-init v. 0.7.2 running 'init' at Tue, 10 Dec 2013 07:59:16 +0000. Up 447.65 seconds. ci-info: +++++++++++++++++++++++Net device info+++++++++++++++++++++++ ci-info: +--------+------+-----------+-----------+-------------------+ ci-info: | Device | Up | Address | Mask | Hw-Address | ci-info: +--------+------+-----------+-----------+-------------------+ ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | . | ci-info: | eth0 | True | . | . | fa:16:3e:35:a5:d9 | ci-info: +--------+------+-----------+-----------+-------------------+ ci-info: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Route info failed!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 2013-12-10 02:59:29,661 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [0/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:30,797 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [1/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:31,892 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [2/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:33,011 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [3/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:34,084 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [5/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:35,149 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [6/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:37,216 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [8/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:39,289 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [10/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:41,351 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [12/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:43,419 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [14/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:45,484 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [16/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:48,579 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [19/120s]: request error [[Errno 101] Network is unreachable] -----Original Message----- From: rhos-list-bounces at redhat.com [mailto:rhos-list-bounces at redhat.com] On Behalf Of Paul Sun Sent: Tuesday, December 10, 2013 8:57 AM To: Haim Ateya; rhos-list at redhat.com Subject: Re: [rhos-list] Problem on creating an instance in PackStack Hi The instance can be started as active, but I am failed to connect it using ssh. I am really not sure how to setup the network. In my setup, I run the Packstack on VM with one controller and two compute nodes. I use the quick start installation method to create the system. After finished the network setup in the dashboard, I tried to create the instance, and the instance status is active with IP assigned, but I am not able to connect it. Should I needed to create bridge interface and assign IP address beforehand? -----Original Message----- From: Haim Ateya [mailto:hateya at redhat.com] Sent: Tuesday, December 10, 2013 3:27 AM To: Paul Sun Cc: rhos-list at redhat.comSubject: Re: [rhos-list] Problem on creating an instance in PackStack Packstack or openstack? It could very (lots can go wrong there ..,) we must get the logs in order to determine what happened. Could you please archive all nova related logs and attach? Haim On Dec 9, 2013, at 8:16, Paul Sun > wrote: Hi I have problem on creating an instance. By following the "Getting Started Guide" Section 6.5, the instance is kept at state=Build, task=Spawning. Tried to check the "Log" and "Console", I obtained "Unable to get log for instance "1e9aaaa4-242e-4da5-b9cb-3deb33246f24"." and "console is currently unavailable. Please try again later." Status respectively. Any idea? _______________________________________________ rhos-list mailing list rhos-list at redhat.com https://www.redhat.com/mailman/listinfo/rhos-list _______________________________________________ rhos-list mailing list rhos-list at redhat.com https://www.redhat.com/mailman/listinfo/rhos-list _______________________________________________ rhos-list mailing list rhos-list at redhat.com https://www.redhat.com/mailman/listinfo/rhos-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From jon at rosslug.org.uk Thu Dec 12 02:05:22 2013 From: jon at rosslug.org.uk (Jonathan Archer) Date: Thu, 12 Dec 2013 02:05:22 +0000 Subject: [rhos-list] Problem on creating an instance in PackStack In-Reply-To: <61D7C199BADE404A8DB174EA3BEE0E9033941441@HKMBX02.ad.syniverse.com> References: <61D7C199BADE404A8DB174EA3BEE0E9033940137@HKMBX02.ad.syniverse.com> <7E54A8FB-6446-4881-B185-E54EFC05BD2C@redhat.com> <61D7C199BADE404A8DB174EA3BEE0E903394056D@HKMBX02.ad.syniverse.com> <61D7C199BADE404A8DB174EA3BEE0E9033940612@HKMBX02.ad.syniverse.com> <61D7C199BADE404A8DB174EA3BEE0E9033940E1A@HKMBX02.ad.syniverse.com> <56e897623aad5b3f59539e31cb797ce6@home.bravo20.co.uk> <61D7C199BADE404A8DB174EA3BEE0E9033941441@HKMBX02.ad.syniverse.com> Message-ID: <159676cd2c2bccc11d18ecbfc01f4d60@127.0.0.1> Paul, are you using ESXi hosts as openstack hypervisors or are you using virtual machines on the ESXi host as openstack hypervisors (I'm also doing the latter in a test env) As for the bridge interface, I followed exactly what was specified in that link I sent earlier to make use of my existing subnet (physical) for my public subnet. I'm guessing for each node you will need to add each of the 3 (if you are using them) interfaces as slaves to the br-ex bridge... Not too sure how that works as I'm only using a single interface at the moment, but do plan to increase. It works a treat. Jon On 12/12/2013 01:22, Paul Sun wrote: > Hi Jon > > Thank for your reply. > > My setup is a new setup, and I run the PackStack on Esxi machine. There are totally having three nodes, one of them as a controller. > > There are three interfaces on each node. From your information, it seems that we need to prepare the interface to serve as bridge interface, I would like to give a try later. > > The documentation from Packstack never instruct user to prepare this, so I am wondering this is required or not. > > FROM: rhos-list-bounces at redhat.com [mailto:rhos-list-bounces at redhat.com] ON BEHALF OF Jonathan Archer > SENT: Wednesday, December 11, 2013 7:19 PM > TO: rhos-list at redhat.com > SUBJECT: Re: [rhos-list] Problem on creating an instance in PackStack > > Hi Paul, > > I take it you are trying to connect from a client on an existing (physical?) network? > > Have you setup your public network to extend an existing network? similar to this? > > http://openstack.redhat.com/Neutron_with_existing_external_network [3] > > or are you using a new subnet? if new have you got a route to this? and set the firewall up as in the quickstart guides? > > are you spawning instances logged in as the admin user? if so try logging in with the demo user. > > From the error messages you post it looks like there is a problem with your networking side of things. > > Hope this helps some? or at least starts the ball rolling. > > Cheers > > Jon > > On 2013-12-11 00:53, Paul Sun wrote: > > Hi > > Is there anyone can help? > > -----Original Message----- > > From: Paul Sun > > Sent: Tuesday, December 10, 2013 11:01 AM > > To: Paul Sun; Haim Ateya; rhos-list at redhat.com > > Subject: RE: [rhos-list] Problem on creating an instance in PackStack > > HI > > This is the log from dashboard. Any idea? > > NET: Registered protocol family 10 > > lo: Disabled Privacy Extensions > > Bringing up loopback interface: [60G[[0;32m OK [0;39m] Bringing up interface eth0: > > Determining IP information for eth0... done. > > [60G[[0;32m OK [0;39m] > > Starting system logger: [60G[[0;32m OK [0;39m] Starting rpcbind: [60G[[0;32m OK [0;39m] Starting NFS statd: [60G[[0;32m OK [0;39m] Mounting filesystems: [60G[[0;32m OK [0;39m] Starting acpi daemon: [60G[[0;32m OK [0;39m] Retrigger failed udev events[60G[[0;32m OK [0;39m] Starting cloud-init: Cloud-init v. 0.7.2 running 'init-local' at Tue, 10 Dec 2013 07:58:49 +0000. Up 420.73 seconds. > > Starting cloud-init: Cloud-init v. 0.7.2 running 'init' at Tue, 10 Dec 2013 07:59:16 +0000. Up 447.65 seconds. > > ci-info: +++++++++++++++++++++++Net device info+++++++++++++++++++++++ > > ci-info: +--------+------+-----------+-----------+-------------------+ > > ci-info: | Device | Up | Address | Mask | Hw-Address | > > ci-info: +--------+------+-----------+-----------+-------------------+ > > ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | . | > > ci-info: | eth0 | True | . | . | fa:16:3e:35:a5:d9 | > > ci-info: +--------+------+-----------+-----------+-------------------+ > > ci-info: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Route info failed!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > > 2013-12-10 02:59:29,661 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [1]' failed [0/120s]: request error [[Errno 101] Network is unreachable] > > 2013-12-10 02:59:30,797 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [1]' failed [1/120s]: request error [[Errno 101] Network is unreachable] > > 2013-12-10 02:59:31,892 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [1]' failed [2/120s]: request error [[Errno 101] Network is unreachable] > > 2013-12-10 02:59:33,011 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [1]' failed [3/120s]: request error [[Errno 101] Network is unreachable] > > 2013-12-10 02:59:34,084 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [1]' failed [5/120s]: request error [[Errno 101] Network is unreachable] > > 2013-12-10 02:59:35,149 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [1]' failed [6/120s]: request error [[Errno 101] Network is unreachable] > > 2013-12-10 02:59:37,216 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [1]' failed [8/120s]: request error [[Errno 101] Network is unreachable] > > 2013-12-10 02:59:39,289 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [1]' failed [10/120s]: request error [[Errno 101] Network is unreachable] > > 2013-12-10 02:59:41,351 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [1]' failed [12/120s]: request error [[Errno 101] Network is unreachable] > > 2013-12-10 02:59:43,419 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [1]' failed [14/120s]: request error [[Errno 101] Network is unreachable] > > 2013-12-10 02:59:45,484 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [1]' failed [16/120s]: request error [[Errno 101] Network is unreachable] > > 2013-12-10 02:59:48,579 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [1]' failed [19/120s]: request error [[Errno 101] Network is unreachable] > > -----Original Message----- > > From: rhos-list-bounces at redhat.com [mailto:rhos-list-bounces at redhat.com] On Behalf Of Paul Sun > > Sent: Tuesday, December 10, 2013 8:57 AM > > To: Haim Ateya; rhos-list at redhat.com > > Subject: Re: [rhos-list] Problem on creating an instance in PackStack > > Hi > > The instance can be started as active, but I am failed to connect it using ssh. I am really not sure how to setup the network. > > In my setup, I run the Packstack on VM with one controller and two compute nodes. I use the quick start installation method to create the system. > > After finished the network setup in the dashboard, I tried to create the instance, and the instance status is active with IP assigned, but I am not able to connect it. > > Should I needed to create bridge interface and assign IP address beforehand? > > -----Original Message----- > > From: Haim Ateya [mailto:hateya at redhat.com] > > Sent: Tuesday, December 10, 2013 3:27 AM > > To: Paul Sun > > Cc: rhos-list at redhat.comSubject: Re: [rhos-list] Problem on creating an instance in PackStack > > Packstack or openstack? It could very (lots can go wrong there ..,) we must get the logs in order to determine what happened. > > Could you please archive all nova related logs and attach? > > Haim > > On Dec 9, 2013, at 8:16, Paul Sun wrote: Hi I have problem on creating an instance. By following the "Getting Started Guide" Section 6.5, the instance is kept at state=Build, task=Spawning. Tried to check the "Log" and "Console", I obtained "Unable to get log for instance "1e9aaaa4-242e-4da5-b9cb-3deb33246f24"." and "console is currently unavailable. Please try again later." Status respectively. Any idea? _______________________________________________ rhos-list mailing list rhos-list at redhat.com https://www.redhat.com/mailman/listinfo/rhos-list [2] > > _______________________________________________ > > rhos-list mailing list > > rhos-list at redhat.com > > https://www.redhat.com/mailman/listinfo/rhos-list [2] > > _______________________________________________ > > rhos-list mailing list > > rhos-list at redhat.com > > https://www.redhat.com/mailman/listinfo/rhos-list [2] Links: ------ [1] http://169.254.169.254/2009-04-04/meta-data/instance-id [2] https://www.redhat.com/mailman/listinfo/rhos-list [3] http://openstack.redhat.com/Neutron_with_existing_external_network -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.sun at syniverse.com Thu Dec 12 02:11:04 2013 From: paul.sun at syniverse.com (Paul Sun) Date: Thu, 12 Dec 2013 02:11:04 +0000 Subject: [rhos-list] Problem on creating an instance in PackStack In-Reply-To: <159676cd2c2bccc11d18ecbfc01f4d60@127.0.0.1> References: <61D7C199BADE404A8DB174EA3BEE0E9033940137@HKMBX02.ad.syniverse.com> <7E54A8FB-6446-4881-B185-E54EFC05BD2C@redhat.com> <61D7C199BADE404A8DB174EA3BEE0E903394056D@HKMBX02.ad.syniverse.com> <61D7C199BADE404A8DB174EA3BEE0E9033940612@HKMBX02.ad.syniverse.com> <61D7C199BADE404A8DB174EA3BEE0E9033940E1A@HKMBX02.ad.syniverse.com> <56e897623aad5b3f59539e31cb797ce6@home.bravo20.co.uk> <61D7C199BADE404A8DB174EA3BEE0E9033941441@HKMBX02.ad.syniverse.com> <159676cd2c2bccc11d18ecbfc01f4d60@127.0.0.1> Message-ID: <61D7C199BADE404A8DB174EA3BEE0E90339414D2@HKMBX02.ad.syniverse.com> Jon Not success. From the time being, I will change back to use OpenStack, as it seems we can get more support on it. From: rhos-list-bounces at redhat.com [mailto:rhos-list-bounces at redhat.com] On Behalf Of Jonathan Archer Sent: Thursday, December 12, 2013 10:05 AM To: rhos-list at redhat.com Subject: Re: [rhos-list] Problem on creating an instance in PackStack Paul, are you using ESXi hosts as openstack hypervisors or are you using virtual machines on the ESXi host as openstack hypervisors (I'm also doing the latter in a test env) As for the bridge interface, I followed exactly what was specified in that link I sent earlier to make use of my existing subnet (physical) for my public subnet. I'm guessing for each node you will need to add each of the 3 (if you are using them) interfaces as slaves to the br-ex bridge... Not too sure how that works as I'm only using a single interface at the moment, but do plan to increase. It works a treat. Jon On 12/12/2013 01:22, Paul Sun wrote: Hi Jon Thank for your reply. My setup is a new setup, and I run the PackStack on Esxi machine. There are totally having three nodes, one of them as a controller. There are three interfaces on each node. From your information, it seems that we need to prepare the interface to serve as bridge interface, I would like to give a try later. The documentation from Packstack never instruct user to prepare this, so I am wondering this is required or not. From: rhos-list-bounces at redhat.com [mailto:rhos-list-bounces at redhat.com] On Behalf Of Jonathan Archer Sent: Wednesday, December 11, 2013 7:19 PM To: rhos-list at redhat.com Subject: Re: [rhos-list] Problem on creating an instance in PackStack Hi Paul, I take it you are trying to connect from a client on an existing (physical?) network? Have you setup your public network to extend an existing network? similar to this? http://openstack.redhat.com/Neutron_with_existing_external_network or are you using a new subnet? if new have you got a route to this? and set the firewall up as in the quickstart guides? are you spawning instances logged in as the admin user? if so try logging in with the demo user. From the error messages you post it looks like there is a problem with your networking side of things. Hope this helps some? or at least starts the ball rolling. Cheers Jon On 2013-12-11 00:53, Paul Sun wrote: Hi Is there anyone can help? -----Original Message----- From: Paul Sun Sent: Tuesday, December 10, 2013 11:01 AM To: Paul Sun; Haim Ateya; rhos-list at redhat.com Subject: RE: [rhos-list] Problem on creating an instance in PackStack HI This is the log from dashboard. Any idea? NET: Registered protocol family 10 lo: Disabled Privacy Extensions Bringing up loopback interface: [60G[[0;32m OK [0;39m] Bringing up interface eth0: Determining IP information for eth0... done. [60G[[0;32m OK [0;39m] Starting system logger: [60G[[0;32m OK [0;39m] Starting rpcbind: [60G[[0;32m OK [0;39m] Starting NFS statd: [60G[[0;32m OK [0;39m] Mounting filesystems: [60G[[0;32m OK [0;39m] Starting acpi daemon: [60G[[0;32m OK [0;39m] Retrigger failed udev events[60G[[0;32m OK [0;39m] Starting cloud-init: Cloud-init v. 0.7.2 running 'init-local' at Tue, 10 Dec 2013 07:58:49 +0000. Up 420.73 seconds. Starting cloud-init: Cloud-init v. 0.7.2 running 'init' at Tue, 10 Dec 2013 07:59:16 +0000. Up 447.65 seconds. ci-info: +++++++++++++++++++++++Net device info+++++++++++++++++++++++ ci-info: +--------+------+-----------+-----------+-------------------+ ci-info: | Device | Up | Address | Mask | Hw-Address | ci-info: +--------+------+-----------+-----------+-------------------+ ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | . | ci-info: | eth0 | True | . | . | fa:16:3e:35:a5:d9 | ci-info: +--------+------+-----------+-----------+-------------------+ ci-info: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Route info failed!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 2013-12-10 02:59:29,661 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [0/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:30,797 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [1/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:31,892 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [2/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:33,011 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [3/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:34,084 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [5/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:35,149 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [6/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:37,216 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [8/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:39,289 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [10/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:41,351 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [12/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:43,419 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [14/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:45,484 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [16/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:48,579 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [19/120s]: request error [[Errno 101] Network is unreachable] -----Original Message----- From: rhos-list-bounces at redhat.com [mailto:rhos-list-bounces at redhat.com] On Behalf Of Paul Sun Sent: Tuesday, December 10, 2013 8:57 AM To: Haim Ateya; rhos-list at redhat.com Subject: Re: [rhos-list] Problem on creating an instance in PackStack Hi The instance can be started as active, but I am failed to connect it using ssh. I am really not sure how to setup the network. In my setup, I run the Packstack on VM with one controller and two compute nodes. I use the quick start installation method to create the system. After finished the network setup in the dashboard, I tried to create the instance, and the instance status is active with IP assigned, but I am not able to connect it. Should I needed to create bridge interface and assign IP address beforehand? -----Original Message----- From: Haim Ateya [mailto:hateya at redhat.com] Sent: Tuesday, December 10, 2013 3:27 AM To: Paul Sun Cc: rhos-list at redhat.comSubject: Re: [rhos-list] Problem on creating an instance in PackStack Packstack or openstack? It could very (lots can go wrong there ..,) we must get the logs in order to determine what happened. Could you please archive all nova related logs and attach? Haim On Dec 9, 2013, at 8:16, Paul Sun > wrote: Hi I have problem on creating an instance. By following the "Getting Started Guide" Section 6.5, the instance is kept at state=Build, task=Spawning. Tried to check the "Log" and "Console", I obtained "Unable to get log for instance "1e9aaaa4-242e-4da5-b9cb-3deb33246f24"." and "console is currently unavailable. Please try again later." Status respectively. Any idea? _______________________________________________ rhos-list mailing list rhos-list at redhat.com https://www.redhat.com/mailman/listinfo/rhos-list _______________________________________________ rhos-list mailing list rhos-list at redhat.com https://www.redhat.com/mailman/listinfo/rhos-list _______________________________________________ rhos-list mailing list rhos-list at redhat.com https://www.redhat.com/mailman/listinfo/rhos-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From jon at rosslug.org.uk Thu Dec 12 02:12:44 2013 From: jon at rosslug.org.uk (Jonathan Archer) Date: Thu, 12 Dec 2013 02:12:44 +0000 Subject: [rhos-list] Problem on creating an instance in PackStack In-Reply-To: <61D7C199BADE404A8DB174EA3BEE0E903394146E@HKMBX02.ad.syniverse.com> References: <61D7C199BADE404A8DB174EA3BEE0E9033940137@HKMBX02.ad.syniverse.com> <7E54A8FB-6446-4881-B185-E54EFC05BD2C@redhat.com> <61D7C199BADE404A8DB174EA3BEE0E903394056D@HKMBX02.ad.syniverse.com> <61D7C199BADE404A8DB174EA3BEE0E9033940612@HKMBX02.ad.syniverse.com> <61D7C199BADE404A8DB174EA3BEE0E9033940E1A@HKMBX02.ad.syniverse.com> <56e897623aad5b3f59539e31cb797ce6@home.bravo20.co.uk> <61D7C199BADE404A8DB174EA3BEE0E9033941441@HKMBX02.ad.syniverse.com> <61D7C199BADE404A8DB174EA3BEE0E903394146E@HKMBX02.ad.syniverse.com> Message-ID: <07fb36d140af5720b1418ee78410e45e@127.0.0.1> Are you sure it isn't? if you installed from the quickstart guide recently then it should be. from a command line source the demo config: . ./keystone_demo then run neutron subnet-list and see what returns. Jon On 12/12/2013 01:29, Paul Sun wrote: > But one serious question, in my installation, neutron is not installed from the packstack command. Why? > > FROM: rhos-list-bounces at redhat.com [mailto:rhos-list-bounces at redhat.com] ON BEHALF OF Paul Sun > SENT: Thursday, December 12, 2013 9:22 AM > TO: jon at rosslug.org.uk; rhos-list at redhat.com > SUBJECT: Re: [rhos-list] Problem on creating an instance in PackStack > > Hi Jon > > Thank for your reply. > > My setup is a new setup, and I run the PackStack on Esxi machine. There are totally having three nodes, one of them as a controller. > > There are three interfaces on each node. From your information, it seems that we need to prepare the interface to serve as bridge interface, I would like to give a try later. > > The documentation from Packstack never instruct user to prepare this, so I am wondering this is required or not. > > FROM: rhos-list-bounces at redhat.com [mailto:rhos-list-bounces at redhat.com] ON BEHALF OF Jonathan Archer > SENT: Wednesday, December 11, 2013 7:19 PM > TO: rhos-list at redhat.com > SUBJECT: Re: [rhos-list] Problem on creating an instance in PackStack > > Hi Paul, > > I take it you are trying to connect from a client on an existing (physical?) network? > > Have you setup your public network to extend an existing network? similar to this? > > http://openstack.redhat.com/Neutron_with_existing_external_network [3] > > or are you using a new subnet? if new have you got a route to this? and set the firewall up as in the quickstart guides? > > are you spawning instances logged in as the admin user? if so try logging in with the demo user. > > From the error messages you post it looks like there is a problem with your networking side of things. > > Hope this helps some? or at least starts the ball rolling. > > Cheers > > Jon > > On 2013-12-11 00:53, Paul Sun wrote: > > Hi > > Is there anyone can help? > > -----Original Message----- > > From: Paul Sun > > Sent: Tuesday, December 10, 2013 11:01 AM > > To: Paul Sun; Haim Ateya; rhos-list at redhat.com > > Subject: RE: [rhos-list] Problem on creating an instance in PackStack > > HI > > This is the log from dashboard. Any idea? > > NET: Registered protocol family 10 > > lo: Disabled Privacy Extensions > > Bringing up loopback interface: [60G[[0;32m OK [0;39m] Bringing up interface eth0: > > Determining IP information for eth0... done. > > [60G[[0;32m OK [0;39m] > > Starting system logger: [60G[[0;32m OK [0;39m] Starting rpcbind: [60G[[0;32m OK [0;39m] Starting NFS statd: [60G[[0;32m OK [0;39m] Mounting filesystems: [60G[[0;32m OK [0;39m] Starting acpi daemon: [60G[[0;32m OK [0;39m] Retrigger failed udev events[60G[[0;32m OK [0;39m] Starting cloud-init: Cloud-init v. 0.7.2 running 'init-local' at Tue, 10 Dec 2013 07:58:49 +0000. Up 420.73 seconds. > > Starting cloud-init: Cloud-init v. 0.7.2 running 'init' at Tue, 10 Dec 2013 07:59:16 +0000. Up 447.65 seconds. > > ci-info: +++++++++++++++++++++++Net device info+++++++++++++++++++++++ > > ci-info: +--------+------+-----------+-----------+-------------------+ > > ci-info: | Device | Up | Address | Mask | Hw-Address | > > ci-info: +--------+------+-----------+-----------+-------------------+ > > ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | . | > > ci-info: | eth0 | True | . | . | fa:16:3e:35:a5:d9 | > > ci-info: +--------+------+-----------+-----------+-------------------+ > > ci-info: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Route info failed!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > > 2013-12-10 02:59:29,661 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [1]' failed [0/120s]: request error [[Errno 101] Network is unreachable] > > 2013-12-10 02:59:30,797 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [1]' failed [1/120s]: request error [[Errno 101] Network is unreachable] > > 2013-12-10 02:59:31,892 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [1]' failed [2/120s]: request error [[Errno 101] Network is unreachable] > > 2013-12-10 02:59:33,011 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [1]' failed [3/120s]: request error [[Errno 101] Network is unreachable] > > 2013-12-10 02:59:34,084 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [1]' failed [5/120s]: request error [[Errno 101] Network is unreachable] > > 2013-12-10 02:59:35,149 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [1]' failed [6/120s]: request error [[Errno 101] Network is unreachable] > > 2013-12-10 02:59:37,216 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [1]' failed [8/120s]: request error [[Errno 101] Network is unreachable] > > 2013-12-10 02:59:39,289 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [1]' failed [10/120s]: request error [[Errno 101] Network is unreachable] > > 2013-12-10 02:59:41,351 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [1]' failed [12/120s]: request error [[Errno 101] Network is unreachable] > > 2013-12-10 02:59:43,419 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [1]' failed [14/120s]: request error [[Errno 101] Network is unreachable] > > 2013-12-10 02:59:45,484 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [1]' failed [16/120s]: request error [[Errno 101] Network is unreachable] > > 2013-12-10 02:59:48,579 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [1]' failed [19/120s]: request error [[Errno 101] Network is unreachable] > > -----Original Message----- > > From: rhos-list-bounces at redhat.com [mailto:rhos-list-bounces at redhat.com] On Behalf Of Paul Sun > > Sent: Tuesday, December 10, 2013 8:57 AM > > To: Haim Ateya; rhos-list at redhat.com > > Subject: Re: [rhos-list] Problem on creating an instance in PackStack > > Hi > > The instance can be started as active, but I am failed to connect it using ssh. I am really not sure how to setup the network. > > In my setup, I run the Packstack on VM with one controller and two compute nodes. I use the quick start installation method to create the system. > > After finished the network setup in the dashboard, I tried to create the instance, and the instance status is active with IP assigned, but I am not able to connect it. > > Should I needed to create bridge interface and assign IP address beforehand? > > -----Original Message----- > > From: Haim Ateya [mailto:hateya at redhat.com] > > Sent: Tuesday, December 10, 2013 3:27 AM > > To: Paul Sun > > Cc: rhos-list at redhat.comSubject: Re: [rhos-list] Problem on creating an instance in PackStack > > Packstack or openstack? It could very (lots can go wrong there ..,) we must get the logs in order to determine what happened. > > Could you please archive all nova related logs and attach? > > Haim > > On Dec 9, 2013, at 8:16, Paul Sun wrote: Hi I have problem on creating an instance. By following the "Getting Started Guide" Section 6.5, the instance is kept at state=Build, task=Spawning. Tried to check the "Log" and "Console", I obtained "Unable to get log for instance "1e9aaaa4-242e-4da5-b9cb-3deb33246f24"." and "console is currently unavailable. Please try again later." Status respectively. Any idea? _______________________________________________ rhos-list mailing list rhos-list at redhat.com https://www.redhat.com/mailman/listinfo/rhos-list [2] > > _______________________________________________ > > rhos-list mailing list > > rhos-list at redhat.com > > https://www.redhat.com/mailman/listinfo/rhos-list [2] > > _______________________________________________ > > rhos-list mailing list > > rhos-list at redhat.com > > https://www.redhat.com/mailman/listinfo/rhos-list [2] Links: ------ [1] http://169.254.169.254/2009-04-04/meta-data/instance-id [2] https://www.redhat.com/mailman/listinfo/rhos-list [3] http://openstack.redhat.com/Neutron_with_existing_external_network -------------- next part -------------- An HTML attachment was scrubbed... URL: From jon at rosslug.org.uk Thu Dec 12 02:14:41 2013 From: jon at rosslug.org.uk (Jonathan Archer) Date: Thu, 12 Dec 2013 02:14:41 +0000 Subject: [rhos-list] Problem on creating an instance in PackStack In-Reply-To: <61D7C199BADE404A8DB174EA3BEE0E90339414D2@HKMBX02.ad.syniverse.com> References: <61D7C199BADE404A8DB174EA3BEE0E9033940137@HKMBX02.ad.syniverse.com> <7E54A8FB-6446-4881-B185-E54EFC05BD2C@redhat.com> <61D7C199BADE404A8DB174EA3BEE0E903394056D@HKMBX02.ad.syniverse.com> <61D7C199BADE404A8DB174EA3BEE0E9033940612@HKMBX02.ad.syniverse.com> <61D7C199BADE404A8DB174EA3BEE0E9033940E1A@HKMBX02.ad.syniverse.com> <56e897623aad5b3f59539e31cb797ce6@home.bravo20.co.uk> <61D7C199BADE404A8DB174EA3BEE0E9033941441@HKMBX02.ad.syniverse.com> <159676cd2c2bccc11d18ecbfc01f4d60@127.0.0.1> <61D7C199BADE404A8DB174EA3BEE0E90339414D2@HKMBX02.ad.syniverse.com> Message-ID: Paul, not sure what you mean by change back to openstack, this is openstack... Packstack is just an installation method for it. Jon On 12/12/2013 02:11, Paul Sun wrote: > Jon > > Not success. From the time being, I will change back to use OpenStack, as it seems we can get more support on it. > > FROM: rhos-list-bounces at redhat.com [mailto:rhos-list-bounces at redhat.com] ON BEHALF OF Jonathan Archer > SENT: Thursday, December 12, 2013 10:05 AM > TO: rhos-list at redhat.com > SUBJECT: Re: [rhos-list] Problem on creating an instance in PackStack > > Paul, > > are you using ESXi hosts as openstack hypervisors or are you using virtual machines on the ESXi host as openstack hypervisors (I'm also doing the latter in a test env) > > As for the bridge interface, I followed exactly what was specified in that link I sent earlier to make use of my existing subnet (physical) for my public subnet. > I'm guessing for each node you will need to add each of the 3 (if you are using them) interfaces as slaves to the br-ex bridge... Not too sure how that works as I'm only using a single interface at the moment, but do plan to increase. > > It works a treat. > > Jon > > On 12/12/2013 01:22, Paul Sun wrote: > > Hi Jon > > Thank for your reply. > > My setup is a new setup, and I run the PackStack on Esxi machine. There are totally having three nodes, one of them as a controller. > > There are three interfaces on each node. From your information, it seems that we need to prepare the interface to serve as bridge interface, I would like to give a try later. > > The documentation from Packstack never instruct user to prepare this, so I am wondering this is required or not. > > FROM: rhos-list-bounces at redhat.com [mailto:rhos-list-bounces at redhat.com] ON BEHALF OF Jonathan Archer > SENT: Wednesday, December 11, 2013 7:19 PM > TO: rhos-list at redhat.com > SUBJECT: Re: [rhos-list] Problem on creating an instance in PackStack > > Hi Paul, > > I take it you are trying to connect from a client on an existing (physical?) network? > > Have you setup your public network to extend an existing network? similar to this? > > http://openstack.redhat.com/Neutron_with_existing_external_network [3] > > or are you using a new subnet? if new have you got a route to this? and set the firewall up as in the quickstart guides? > > are you spawning instances logged in as the admin user? if so try logging in with the demo user. > > From the error messages you post it looks like there is a problem with your networking side of things. > > Hope this helps some? or at least starts the ball rolling. > > Cheers > > Jon > > On 2013-12-11 00:53, Paul Sun wrote: > > Hi > > Is there anyone can help? > > -----Original Message----- > > From: Paul Sun > > Sent: Tuesday, December 10, 2013 11:01 AM > > To: Paul Sun; Haim Ateya; rhos-list at redhat.com > > Subject: RE: [rhos-list] Problem on creating an instance in PackStack > > HI > > This is the log from dashboard. Any idea? > > NET: Registered protocol family 10 > > lo: Disabled Privacy Extensions > > Bringing up loopback interface: [60G[[0;32m OK [0;39m] Bringing up interface eth0: > > Determining IP information for eth0... done. > > [60G[[0;32m OK [0;39m] > > Starting system logger: [60G[[0;32m OK [0;39m] Starting rpcbind: [60G[[0;32m OK [0;39m] Starting NFS statd: [60G[[0;32m OK [0;39m] Mounting filesystems: [60G[[0;32m OK [0;39m] Starting acpi daemon: [60G[[0;32m OK [0;39m] Retrigger failed udev events[60G[[0;32m OK [0;39m] Starting cloud-init: Cloud-init v. 0.7.2 running 'init-local' at Tue, 10 Dec 2013 07:58:49 +0000. Up 420.73 seconds. > > Starting cloud-init: Cloud-init v. 0.7.2 running 'init' at Tue, 10 Dec 2013 07:59:16 +0000. Up 447.65 seconds. > > ci-info: +++++++++++++++++++++++Net device info+++++++++++++++++++++++ > > ci-info: +--------+------+-----------+-----------+-------------------+ > > ci-info: | Device | Up | Address | Mask | Hw-Address | > > ci-info: +--------+------+-----------+-----------+-------------------+ > > ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | . | > > ci-info: | eth0 | True | . | . | fa:16:3e:35:a5:d9 | > > ci-info: +--------+------+-----------+-----------+-------------------+ > > ci-info: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Route info failed!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > > 2013-12-10 02:59:29,661 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [1]' failed [0/120s]: request error [[Errno 101] Network is unreachable] > > 2013-12-10 02:59:30,797 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [1]' failed [1/120s]: request error [[Errno 101] Network is unreachable] > > 2013-12-10 02:59:31,892 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [1]' failed [2/120s]: request error [[Errno 101] Network is unreachable] > > 2013-12-10 02:59:33,011 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [1]' failed [3/120s]: request error [[Errno 101] Network is unreachable] > > 2013-12-10 02:59:34,084 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [1]' failed [5/120s]: request error [[Errno 101] Network is unreachable] > > 2013-12-10 02:59:35,149 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [1]' failed [6/120s]: request error [[Errno 101] Network is unreachable] > > 2013-12-10 02:59:37,216 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [1]' failed [8/120s]: request error [[Errno 101] Network is unreachable] > > 2013-12-10 02:59:39,289 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [1]' failed [10/120s]: request error [[Errno 101] Network is unreachable] > > 2013-12-10 02:59:41,351 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [1]' failed [12/120s]: request error [[Errno 101] Network is unreachable] > > 2013-12-10 02:59:43,419 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [1]' failed [14/120s]: request error [[Errno 101] Network is unreachable] > > 2013-12-10 02:59:45,484 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [1]' failed [16/120s]: request error [[Errno 101] Network is unreachable] > > 2013-12-10 02:59:48,579 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id [1]' failed [19/120s]: request error [[Errno 101] Network is unreachable] > > -----Original Message----- > > From: rhos-list-bounces at redhat.com [mailto:rhos-list-bounces at redhat.com] On Behalf Of Paul Sun > > Sent: Tuesday, December 10, 2013 8:57 AM > > To: Haim Ateya; rhos-list at redhat.com > > Subject: Re: [rhos-list] Problem on creating an instance in PackStack > > Hi > > The instance can be started as active, but I am failed to connect it using ssh. I am really not sure how to setup the network. > > In my setup, I run the Packstack on VM with one controller and two compute nodes. I use the quick start installation method to create the system. > > After finished the network setup in the dashboard, I tried to create the instance, and the instance status is active with IP assigned, but I am not able to connect it. > > Should I needed to create bridge interface and assign IP address beforehand? > > -----Original Message----- > > From: Haim Ateya [mailto:hateya at redhat.com] > > Sent: Tuesday, December 10, 2013 3:27 AM > > To: Paul Sun > > Cc: rhos-list at redhat.comSubject: Re: [rhos-list] Problem on creating an instance in PackStack > > Packstack or openstack? It could very (lots can go wrong there ..,) we must get the logs in order to determine what happened. > > Could you please archive all nova related logs and attach? > > Haim > > On Dec 9, 2013, at 8:16, Paul Sun wrote: Hi I have problem on creating an instance. By following the "Getting Started Guide" Section 6.5, the instance is kept at state=Build, task=Spawning. Tried to check the "Log" and "Console", I obtained "Unable to get log for instance "1e9aaaa4-242e-4da5-b9cb-3deb33246f24"." and "console is currently unavailable. Please try again later." Status respectively. Any idea? _______________________________________________ rhos-list mailing list rhos-list at redhat.com https://www.redhat.com/mailman/listinfo/rhos-list [2] > > _______________________________________________ > > rhos-list mailing list > > rhos-list at redhat.com > > https://www.redhat.com/mailman/listinfo/rhos-list [2] > > _______________________________________________ > > rhos-list mailing list > > rhos-list at redhat.com > > https://www.redhat.com/mailman/listinfo/rhos-list [2] Links: ------ [1] http://169.254.169.254/2009-04-04/meta-data/instance-id [2] https://www.redhat.com/mailman/listinfo/rhos-list [3] http://openstack.redhat.com/Neutron_with_existing_external_network -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.sun at syniverse.com Thu Dec 12 02:14:52 2013 From: paul.sun at syniverse.com (Paul Sun) Date: Thu, 12 Dec 2013 02:14:52 +0000 Subject: [rhos-list] Problem on creating an instance in PackStack In-Reply-To: <07fb36d140af5720b1418ee78410e45e@127.0.0.1> References: <61D7C199BADE404A8DB174EA3BEE0E9033940137@HKMBX02.ad.syniverse.com> <7E54A8FB-6446-4881-B185-E54EFC05BD2C@redhat.com> <61D7C199BADE404A8DB174EA3BEE0E903394056D@HKMBX02.ad.syniverse.com> <61D7C199BADE404A8DB174EA3BEE0E9033940612@HKMBX02.ad.syniverse.com> <61D7C199BADE404A8DB174EA3BEE0E9033940E1A@HKMBX02.ad.syniverse.com> <56e897623aad5b3f59539e31cb797ce6@home.bravo20.co.uk> <61D7C199BADE404A8DB174EA3BEE0E9033941441@HKMBX02.ad.syniverse.com> <61D7C199BADE404A8DB174EA3BEE0E903394146E@HKMBX02.ad.syniverse.com> <07fb36d140af5720b1418ee78410e45e@127.0.0.1> Message-ID: <61D7C199BADE404A8DB174EA3BEE0E9033941503@HKMBX02.ad.syniverse.com> Due to lack of support, I have removed the VM, and on the way to install Openstack. I may try PackStack again later. From: Jonathan Archer [mailto:jon at rosslug.org.uk] Sent: Thursday, December 12, 2013 10:13 AM To: Paul Sun Cc: rhos-list at redhat.com Subject: RE: [rhos-list] Problem on creating an instance in PackStack Are you sure it isn't? if you installed from the quickstart guide recently then it should be. from a command line source the demo config: . ./keystone_demo then run neutron subnet-list and see what returns. Jon On 12/12/2013 01:29, Paul Sun wrote: But one serious question, in my installation, neutron is not installed from the packstack command. Why? From: rhos-list-bounces at redhat.com [mailto:rhos-list-bounces at redhat.com] On Behalf Of Paul Sun Sent: Thursday, December 12, 2013 9:22 AM To: jon at rosslug.org.uk; rhos-list at redhat.com Subject: Re: [rhos-list] Problem on creating an instance in PackStack Hi Jon Thank for your reply. My setup is a new setup, and I run the PackStack on Esxi machine. There are totally having three nodes, one of them as a controller. There are three interfaces on each node. From your information, it seems that we need to prepare the interface to serve as bridge interface, I would like to give a try later. The documentation from Packstack never instruct user to prepare this, so I am wondering this is required or not. From: rhos-list-bounces at redhat.com [mailto:rhos-list-bounces at redhat.com] On Behalf Of Jonathan Archer Sent: Wednesday, December 11, 2013 7:19 PM To: rhos-list at redhat.com Subject: Re: [rhos-list] Problem on creating an instance in PackStack Hi Paul, I take it you are trying to connect from a client on an existing (physical?) network? Have you setup your public network to extend an existing network? similar to this? http://openstack.redhat.com/Neutron_with_existing_external_network or are you using a new subnet? if new have you got a route to this? and set the firewall up as in the quickstart guides? are you spawning instances logged in as the admin user? if so try logging in with the demo user. From the error messages you post it looks like there is a problem with your networking side of things. Hope this helps some? or at least starts the ball rolling. Cheers Jon On 2013-12-11 00:53, Paul Sun wrote: Hi Is there anyone can help? -----Original Message----- From: Paul Sun Sent: Tuesday, December 10, 2013 11:01 AM To: Paul Sun; Haim Ateya; rhos-list at redhat.com Subject: RE: [rhos-list] Problem on creating an instance in PackStack HI This is the log from dashboard. Any idea? NET: Registered protocol family 10 lo: Disabled Privacy Extensions Bringing up loopback interface: [60G[[0;32m OK [0;39m] Bringing up interface eth0: Determining IP information for eth0... done. [60G[[0;32m OK [0;39m] Starting system logger: [60G[[0;32m OK [0;39m] Starting rpcbind: [60G[[0;32m OK [0;39m] Starting NFS statd: [60G[[0;32m OK [0;39m] Mounting filesystems: [60G[[0;32m OK [0;39m] Starting acpi daemon: [60G[[0;32m OK [0;39m] Retrigger failed udev events[60G[[0;32m OK [0;39m] Starting cloud-init: Cloud-init v. 0.7.2 running 'init-local' at Tue, 10 Dec 2013 07:58:49 +0000. Up 420.73 seconds. Starting cloud-init: Cloud-init v. 0.7.2 running 'init' at Tue, 10 Dec 2013 07:59:16 +0000. Up 447.65 seconds. ci-info: +++++++++++++++++++++++Net device info+++++++++++++++++++++++ ci-info: +--------+------+-----------+-----------+-------------------+ ci-info: | Device | Up | Address | Mask | Hw-Address | ci-info: +--------+------+-----------+-----------+-------------------+ ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | . | ci-info: | eth0 | True | . | . | fa:16:3e:35:a5:d9 | ci-info: +--------+------+-----------+-----------+-------------------+ ci-info: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Route info failed!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 2013-12-10 02:59:29,661 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [0/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:30,797 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [1/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:31,892 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [2/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:33,011 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [3/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:34,084 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [5/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:35,149 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [6/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:37,216 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [8/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:39,289 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [10/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:41,351 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [12/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:43,419 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [14/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:45,484 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [16/120s]: request error [[Errno 101] Network is unreachable] 2013-12-10 02:59:48,579 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [19/120s]: request error [[Errno 101] Network is unreachable] -----Original Message----- From: rhos-list-bounces at redhat.com [mailto:rhos-list-bounces at redhat.com] On Behalf Of Paul Sun Sent: Tuesday, December 10, 2013 8:57 AM To: Haim Ateya; rhos-list at redhat.com Subject: Re: [rhos-list] Problem on creating an instance in PackStack Hi The instance can be started as active, but I am failed to connect it using ssh. I am really not sure how to setup the network. In my setup, I run the Packstack on VM with one controller and two compute nodes. I use the quick start installation method to create the system. After finished the network setup in the dashboard, I tried to create the instance, and the instance status is active with IP assigned, but I am not able to connect it. Should I needed to create bridge interface and assign IP address beforehand? -----Original Message----- From: Haim Ateya [mailto:hateya at redhat.com] Sent: Tuesday, December 10, 2013 3:27 AM To: Paul Sun Cc: rhos-list at redhat.comSubject: Re: [rhos-list] Problem on creating an instance in PackStack Packstack or openstack? It could very (lots can go wrong there ..,) we must get the logs in order to determine what happened. Could you please archive all nova related logs and attach? Haim On Dec 9, 2013, at 8:16, Paul Sun > wrote: Hi I have problem on creating an instance. By following the "Getting Started Guide" Section 6.5, the instance is kept at state=Build, task=Spawning. Tried to check the "Log" and "Console", I obtained "Unable to get log for instance "1e9aaaa4-242e-4da5-b9cb-3deb33246f24"." and "console is currently unavailable. Please try again later." Status respectively. Any idea? _______________________________________________ rhos-list mailing list rhos-list at redhat.com https://www.redhat.com/mailman/listinfo/rhos-list _______________________________________________ rhos-list mailing list rhos-list at redhat.com https://www.redhat.com/mailman/listinfo/rhos-list _______________________________________________ rhos-list mailing list rhos-list at redhat.com https://www.redhat.com/mailman/listinfo/rhos-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From pmyers at redhat.com Thu Dec 12 14:55:03 2013 From: pmyers at redhat.com (Perry Myers) Date: Thu, 12 Dec 2013 09:55:03 -0500 Subject: [rhos-list] Problem on creating an instance in PackStack In-Reply-To: <61D7C199BADE404A8DB174EA3BEE0E90339414D2@HKMBX02.ad.syniverse.com> References: <61D7C199BADE404A8DB174EA3BEE0E9033940137@HKMBX02.ad.syniverse.com> <7E54A8FB-6446-4881-B185-E54EFC05BD2C@redhat.com> <61D7C199BADE404A8DB174EA3BEE0E903394056D@HKMBX02.ad.syniverse.com> <61D7C199BADE404A8DB174EA3BEE0E9033940612@HKMBX02.ad.syniverse.com> <61D7C199BADE404A8DB174EA3BEE0E9033940E1A@HKMBX02.ad.syniverse.com> <56e897623aad5b3f59539e31cb797ce6@home.bravo20.co.uk> <61D7C199BADE404A8DB174EA3BEE0E9033941441@HKMBX02.ad.syniverse.com> <159676cd2c2bccc11d18ecbfc01f4d60@127.0.0.1> <61D7C199BADE404A8DB174EA3BEE0E90339414D2@HKMBX02.ad.syniverse.com> Message-ID: <52A9CE47.4050503@redhat.com> On 12/11/2013 09:11 PM, Paul Sun wrote: > Jon > > > > Not success. From the time being, I will change back to use OpenStack, > as it seems we can get more support on it. Re: lack of support, are you just using an eval version of the RHOS software? Or are you (and your company) participating in our early adopters program? rhos-list isn't a way to get support, but if you are interested in support, we have ways to provide that. I've cc'd some folks who may be able to help (Jan, Dave, Brian) Perry From liugya at cn.ibm.com Thu Dec 19 07:03:30 2013 From: liugya at cn.ibm.com (Guang Ya GY Liu) Date: Thu, 19 Dec 2013 15:03:30 +0800 Subject: [rhos-list] RDO problem Message-ID: Hi, I was following this install guide to install OpenStack with RDO: http://openstack.redhat.com/Quickstart After install and OpenStack start, every time I boot a new instance, there will be a new nova-compute start up, after I create two instance, there are three nova-compute, do you know why the instance create caused new nova-compute start? [root at db03b04 network-scripts(keystone_admin)]# ps -ef | grep nova-com nova 5174 6099 0 01:07 ? 00:00:00 /usr/bin/python /usr/bin/nova-compute --logfile /var/log/nova/compute.log <<<<<<<<<< Why? nova 6099 1 0 Dec18 ? 00:07:47 /usr/bin/python /usr/bin/nova-compute --logfile /var/log/nova/compute.log nova 6553 6099 0 Dec18 ? 00:00:00 /usr/bin/python /usr/bin/nova-compute --logfile /var/log/nova/compute.log <<<<<<<<<< Why? Thanks, Guangya -------------- next part -------------- An HTML attachment was scrubbed... URL: From pmyers at redhat.com Thu Dec 19 12:46:44 2013 From: pmyers at redhat.com (Perry Myers) Date: Thu, 19 Dec 2013 07:46:44 -0500 Subject: [rhos-list] RDO problem In-Reply-To: References: Message-ID: <52B2EAB4.7070901@redhat.com> Thread moved to rdo-list here: https://www.redhat.com/archives/rdo-list/2013-December/msg00034.html On 12/19/2013 02:03 AM, Guang Ya GY Liu wrote: > Hi, > > I was following this install guide to install OpenStack with RDO: > http://openstack.redhat.com/Quickstart > > After install and OpenStack start, every time I boot a new instance, > there will be a new nova-compute start up, after I create two instance, > there are three nova-compute, do you know why the instance create caused > new nova-compute start? > > [root at db03b04 network-scripts(keystone_admin)]# ps -ef | grep nova-com > nova 5174 6099 0 01:07 ? 00:00:00 /usr/bin/python > /usr/bin/nova-compute --logfile /var/log/nova/compute.log <<<<<<<<<< Why? > nova 6099 1 0 Dec18 ? 00:07:47 /usr/bin/python > /usr/bin/nova-compute --logfile /var/log/nova/compute.log > nova 6553 6099 0 Dec18 ? 00:00:00 /usr/bin/python > /usr/bin/nova-compute --logfile /var/log/nova/compute.log <<<<<<<<<< Why? > > Thanks, > > Guangya > > > _______________________________________________ > rhos-list mailing list > rhos-list at redhat.com > https://www.redhat.com/mailman/listinfo/rhos-list >