Ask Your Question

theora-rice's profile - activity

2015-01-20 07:57:21 -0500 received badge  Famous Question (source)
2015-01-14 01:24:09 -0500 received badge  Famous Question (source)
2015-01-13 18:10:17 -0500 received badge  Enthusiast
2015-01-13 10:22:31 -0500 received badge  Notable Question (source)
2015-01-09 17:42:57 -0500 received badge  Nice Question (source)
2015-01-09 17:42:55 -0500 received badge  Popular Question (source)
2015-01-08 15:23:33 -0500 asked a question Does anyone have Xenserver 6.5 and Openstack playing nicely?

Hello, My team and I are working on building a working Openstack environment using Xenserver 6.5, and have been running into a lot of issues. One of the most persistent is a problem launching instances using automatic partitioning due to “missing PV drivers,” despite the PV drivers being in place. If the image is deployed with manual partitioning, the problem does not crop up (though others sometimes do.) There are many other problems that have been plaguing us as well, mostly centered around networking. So my question is this, has anyone else working with Xenserver 6.5 and openstack encountered any similar problems? Has anyone gotten it working?

Thanks~

2014-10-13 04:58:17 -0500 received badge  Notable Question (source)
2014-10-06 20:05:46 -0500 answered a question Installing Devstack on Xenserver triggers a urllib3.connectionpool warning, followed by a 409 Conflict: Cannot upload to an unqueued image.

I believe I just fixed the problem. Apparently, the stack.sh script iterated multiple times through the last element of the IMAGE_URLS variable that I set in localrc. When I got rid of the comma in that list, and changed stack.sh to just read white space as the element separator of a list (as is the default), the script completed without further error.

To illustrate:

(In localrc) IMAGE_URLS="\ https://github.com/downloads/citrix-o... http://download.cirros-cloud.net/0.3.... (From the devstack/tools/xen/readme)

Became IMAGE_URLS="https://github.com/downloads/citrix-openstack/warehouse/cirros-0.3.0-x86_64-disk.vhd.tgz http://download.cirros-cloud.net/0.3....

(And in stack.sh) for image_url in ${IMAGE_URLS//,/ }; do

Became for image_url in ${IMAGE_URLS}; do

2014-10-03 17:29:04 -0500 received badge  Student (source)
2014-10-03 17:26:17 -0500 received badge  Famous Question (source)
2014-10-03 17:26:17 -0500 received badge  Notable Question (source)
2014-10-03 17:26:17 -0500 received badge  Popular Question (source)
2014-10-03 04:54:34 -0500 received badge  Popular Question (source)
2014-10-02 19:01:08 -0500 asked a question Devstack on Xenserver 6.5

Has anyone managed to get Devstack working on Xenserver 6.5 yet?

2014-10-02 18:50:47 -0500 asked a question Installing Devstack on Xenserver triggers a urllib3.connectionpool warning, followed by a 409 Conflict: Cannot upload to an unqueued image.

Hello. The project I am trying to execute involves installing devstack onto Xenserver 6.5. This seemed pretty straight forward, at least as described by https://github.com/openstack-dev/devs... . However I have had a number of errors. Most I have been able to fix through various forum posts, but this particular problem has eluded answers.

My configuration is XenServer 6.5 installed on a server, with the latest version of devstack downloaded on the host. As guided in the README, I trigger ./install_os_domU.sh, which creates the DevStackOSDomU vm (in this circumstance, IP: 192.168.2.230) that will run devstack. However, while stack.sh is running (as part of run.sh) on DevStackOSDomU, the following error occurs and shuts down the install:

+ [[ x86_64 == \p\p\c\6\4 ]]
+ '[' '' = bare ']'
+ local kernel_id= ramdisk_id=
+ '[' -n /opt/stack/devstack/files/images/cirros-0.3.2-x86_64-uec/cirros-0.3.2-x86_64-vmlinuz ']'
++ openstack --os-token b6269cdf2e154d0c94d130db522da200 --os-url http://192.168.2.230:9292 image create cirros-0.3.2-x86_64-uec-kernel --public --container-forma$
++ grep ' id '
++ get_field 2
++ local data field
++ read data
WARNING: urllib3.connectionpool HttpConnectionPool is full, discarding connection: 192.168.2.230
ERROR: openstack <html>
 <head>
  <title>409 Conflict</title>
 </head>
 <body>
  <h1>409 Conflict</h1>
  There was a conflict when trying to complete your request.<br /><br />
  Cannot upload to an unqueued image

 </body>
</html> (HTTP 409)
+ kernel_id=
+ '[' -n /opt/stack/devstack/files/images/cirros-0.3.2-x86_64-uec/cirros-0.3.2-x86_64-initrd ']'
++ openstack --os-token b6269cdf2e154d0c94d130db522da200 --os-url http://192.168.2.230:9292 image create cirros-0.3.2-x86_64-uec-ramdisk --public --container-form$
++ grep ' id '
++ get_field 2
++ local data field
++ read data
WARNING: urllib3.connectionpool HttpConnectionPool is full, discarding connection: 192.168.2.230
ERROR: openstack <html>
 <head>
 <title>409 Conflict</title>
 </head>
 <body>
  <h1>409 Conflict</h1>
  There was a conflict when trying to complete your request.<br /><br />
Cannot upload to an unqueued image

 </body>
</html> (HTTP 409)
+ ramdisk_id=
+ openstack --os-token b6269cdf2e154d0c94d130db522da200 --os-url http://192.168.2.230:9292 image create cirros-0.3.2-x86_64-uec --public --container-format ami --$
WARNING: urllib3.connectionpool HttpConnectionPool is full, discarding connection: 192.168.2.230
ERROR: openstack <html>
 <head>
  <title>409 Conflict</title>
 </head>
 <body>
  <h1>409 Conflict</h1>
  There was a conflict when trying to complete your request.<br /><br />
 Cannot upload to an unqueued image

 </body>
</html> (HTTP 409)
+ exit_trap
+ local r=1
++ jobs -p
+ jobs=
+ [[ -n '' ]]
+ kill_spinner
+ '[' '!' -z '' ']'
+ [[ 1 -ne 0 ]]
+ echo 'Error on exit'
Error on exit
+ [[ -z /opt/stack/logs ]]
+ /opt/stack/devstack/tools/worlddump.py -d /opt/stack/logs
+ exit 1

As you can see, the error repeats three times, then errors out. Devstack does not end up installing, and cannot be run. I can't seem to see why the HttpConnectionPool would be full from the logs of the process, and this doesn't seem to be a common error in installing devstack on Xenserver. I'm wondering if the warning is connected to the error. Has anyone run into this problem before, or understand a potential way to solve it?