https://bugzilla.novell.com/show_bug.cgi?id=838755 https://bugzilla.novell.com/show_bug.cgi?id=838755#c0 Summary: Request - Embed tests into OpenStack Quickstart Demo Setup script Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: tonysu@su-networking.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0 Unfortunately the OpenStack Quickstart Demo script has never worked for Folsom, and it now does not work for Grizzly releases. In both cases, it has been a "close, but still not working" problem related to some sort of authentication issue. I can only expect that the script works on SLES but obviously has never been really tested on openSUSE. Instead of asking for a specific fix for Grizzly (there is a bug I submitted for Folsom which has never been fixed), I am asking for a feature request to embed tests in the OpenStack Quickstart Demo Setup script so that as each significant command or function completes, the script <verifies> the functionality is working. This should be useful for a number of reasons: - Should help in properly documenting the flow and functionality of the script which could be useful not only for implementing in SLES and openSUSE but also if someone wished to adapt to another distro - Currently, breakage exists and is difficult to fix because the script sometimes just hangs silently. - Currently, it may be difficult to understand what is really breaking or not functioning properly, this is a request to improve debugging capability in a standardized way which can also be easily turned off by simply commenting out these additional checks if desired. Personally, since the Demo Setup should only be done once I have little objection to leaving such checks in place which would slow down execution in favor of making sure the installation is successful. Note that the script breaks the same way when installed in a KVM Guest and LXC container, both using Linux Bridge devices for networking. Although possibly related to this type of networking, my current guess is that this should not be the main problem because aside from the virtual isolation of the VM Guest and Containers, I also use non-standard device names (eg virbr2) so there should not be a conflict with standard installs which almost always assume that the first bridge device names (eg br0) is available. Reproducible: Always Steps to Reproduce: Running the Quickstart Demo Setup script fails running in a KVM/libvirt Guest VM, and in a LXC Container. Actual Results: Hangs after the following error # quantum -v net-create fixed --shared --provider:network_type flat --provider:physical_network root-bridge DEBUG: quantumclient.quantum.v2_0.network.CreateNetwork get_data(Namespace(admin_state_down=True, columns=[], formatter='table', name='fixed', prefix='', request_format='json', shared=True, tenant_id=None, variables=[])) DEBUG: quantumclient.client REQ: curl -i http://127.0.0.1:5000/v2.0/tokens -X POST -H "Content-Type: application/json" -H "Accept: application/json" -H "User-Agent: python-quantumclient" -d '{"auth": {"tenantName": "admin", "passwordCredentials": {"username": "admin", "password": "openstack"}}}' DEBUG: quantumclient.client RESP:{'status': '400', 'content-length': 30, 'content-type': 'text/plain'} [Errno 111] Connection refused ERROR: quantumclient.shell [Errno 111] Connection refused DEBUG: quantumclient.shell clean_up CreateNetwork DEBUG: quantumclient.shell got an error: [Errno 111] Connection refused Expected Results: Expect the Quickstart Demo Setup script to complete successfully Although I'm assigning this as a bug with "Major severity" because as long as this/these bug(s) exist in this script, it's totally unusable for both quick, simple setups and introductions on openSUSE, it's also as much a Feature Request for self-help and the future. My investigation suggests this might be related to the Folsom issue I identified related to improper configuration accessing GPG keys, but only because of the timing of the error. There is <no> current substantial evidence the errors are related, though. Note the earlier "Nova" related error <can> be related to the current "Quantum" error because apparently OpenStack transferred network configuration from Nova to Quantum setups. This issue should be easily repeatable, unfortunately I am currently far more obligated to another effort which would only optionally benefit from a working OpenStack so I have to be careful how much of my personal resources I can allocate to this OpenStack Quickstart Demo Setup, but if this feature request is implemented it would not only greatly allow me to troubleshoot this problem (if it isn't already addressed because of its implementation) it should greatly benefit the future evolution and increase its potential applicability to other distros. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.