I'm running into the following error when attempting to push a successfully built image. I just pulled from the development RHEL 6.1 repo yesterday. Any help on how to fix this is appreciated. I can connect via curl on the command line.
[root@cldmgr01 ~]# aeolus-image push --provider rhevm --id e4c702a2-ee72-4c08-8117-20f68d28c2b8
Provider Image: 0f453478-6f84-4295-874d-f6d25f64b4ac Image: e4c702a2-ee72-4c08-8117-20f68d28c2b8 Build: 12369482-95cb-4119-a69e-b516276e422f Status: PUSHING Percent Complete: 0
[root@cldmgr01 ~]# tail -f /var/log/imagefactory.log self.push_image_upload(target_image_id, provider, credentials) File "/usr/lib/python2.6/site-packages/imagefactory/builders/FedoraBuilder.py", line 1006, in push_image_upload self.rhevm_push_image_upload(target_image_id, provider, credentials) File "/usr/lib/python2.6/site-packages/imagefactory/builders/FedoraBuilder.py", line 981, in rhevm_push_image_upload raise ImageFactoryException("Failed to extract RHEV-M UUID from warehouse POST reponse: %s" % (response)) ImageFactoryException: Failed to extract RHEV-M UUID from warehouse POST reponse: failed ERROR curl failed GET url `https://rhevm.cloud.redhat.com:8543/rhevm-api-powershell/'
2011-07-28 03:53:39,817 DEBUG imagefactory.BuildJob.BuildAdaptor pid(2650) Message: Raising event with agent handler (<ImageFactoryAgent(Thread-1, initial)>), changed status from FAILED to FAILED
[root@cldmgr01 ~]# curl https://rhevm.cloud.redhat.com:8543/rhevm-api-powershell/ <html><head><title>JBoss Web/2.1.3.GA - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 401 - </h1><HR size="1" noshade="noshade"><p><b>type</b> Status report</p><p><b>message</b> <u></u></p><p><b>description</b> <u>This request requires HTTP authentication ().</u></p><HR size="1" noshade="noshade"><h3>JBoss Web/2.1.3.GA</h3></body></html>[root@cldm[root@cldmgr01 ~]#
-James
This message, "failed ERROR curl failed GET url `https://rhevm.cloud.redhat.com:8543/rhevm-api-powershell/'" is coming from iwhd but I cannot make out what the problem is. Maybe Jim or Pete can shed some light on what's going on here.
-steve
On Jul 28, 2011, at 8:09 AM, James Labocki wrote:
I'm running into the following error when attempting to push a successfully built image. I just pulled from the development RHEL 6.1 repo yesterday. Any help on how to fix this is appreciated. I can connect via curl on the command line.
[root@cldmgr01 ~]# aeolus-image push --provider rhevm --id e4c702a2-ee72-4c08-8117-20f68d28c2b8
Provider Image: 0f453478-6f84-4295-874d-f6d25f64b4ac Image: e4c702a2-ee72-4c08-8117-20f68d28c2b8 Build: 12369482-95cb-4119-a69e-b516276e422f Status: PUSHING Percent Complete: 0
[root@cldmgr01 ~]# tail -f /var/log/imagefactory.log self.push_image_upload(target_image_id, provider, credentials) File "/usr/lib/python2.6/site-packages/imagefactory/builders/FedoraBuilder.py", line 1006, in push_image_upload self.rhevm_push_image_upload(target_image_id, provider, credentials) File "/usr/lib/python2.6/site-packages/imagefactory/builders/FedoraBuilder.py", line 981, in rhevm_push_image_upload raise ImageFactoryException("Failed to extract RHEV-M UUID from warehouse POST reponse: %s" % (response)) ImageFactoryException: Failed to extract RHEV-M UUID from warehouse POST reponse: failed ERROR curl failed GET url `https://rhevm.cloud.redhat.com:8543/rhevm-api-powershell/'
2011-07-28 03:53:39,817 DEBUG imagefactory.BuildJob.BuildAdaptor pid(2650) Message: Raising event with agent handler (<ImageFactoryAgent(Thread-1, initial)>), changed status from FAILED to FAILED
[root@cldmgr01 ~]# curl https://rhevm.cloud.redhat.com:8543/rhevm-api-powershell/
<html><head><title>JBoss Web/2.1.3.GA - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 401 - </h1><HR size="1" noshade="noshade"><p><b>type</b> Status report</p><p><b>message</b> <u></u></p><p><b>description</b> <u>This request requires HTTP authentication ().</u></p><HR size="1" noshade="noshade"><h3>JBoss Web/2.1.3.GA</h3></body></html>[root@cldm[root@cldmgr01 ~]#
-James _______________________________________________ aeolus-devel mailing list aeolus-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/aeolus-devel
On Thu, 28 Jul 2011 09:05:11 -0500 Steve Loranz sloranz@redhat.com wrote:
On Jul 28, 2011, at 8:09 AM, James Labocki wrote:
I can connect via curl on the command line.
[root@cldmgr01 ~]# curl https://rhevm.cloud.redhat.com:8543/rhevm-api-powershell/
<html><head><title> <h1>HTTP Status 401 - </h1> <u>This request requires HTTP authentication ().</u> [root@cldm[root@cldmgr01 ~]#
Looks like RHEV password is incorrect. But please don't post it to aeolus-devel :-)
This message, "failed ERROR curl failed GET url `https://rhevm.cloud.redhat.com:8543/rhevm-api-powershell/'" is coming from iwhd but I cannot make out what the problem is.
James did exactly the right thing in the circumstances: tried the URL. But he did not go far enough. Next step is to copy credentials from the /etc/factory.conf (IIRC) and try with curl -u xxx@yyy:ppp, see how that goes.
-- Pete
----- Original Message -----
From: "Pete Zaitcev" zaitcev@redhat.com To: "Steve Loranz" sloranz@redhat.com Cc: "James Labocki" jlabocki@redhat.com, "Jim Meyering" jim@meyering.net, aeolus-devel@lists.fedorahosted.org, zaitcev@redhat.com Sent: Thursday, July 28, 2011 11:32:04 AM Subject: Re: aeolus-image push curl failed On Thu, 28 Jul 2011 09:05:11 -0500 Steve Loranz sloranz@redhat.com wrote:
On Jul 28, 2011, at 8:09 AM, James Labocki wrote:
I can connect via curl on the command line.
[root@cldmgr01 ~]# curl https://rhevm.cloud.redhat.com:8543/rhevm-api-powershell/
<html><head><title> <h1>HTTP Status 401 - </h1> <u>This request requires HTTP authentication ().</u> [root@cldm[root@cldmgr01 ~]#
Looks like RHEV password is incorrect. But please don't post it to aeolus-devel :-)
It's OK, it's only a lab environment and is completely disconnected from the network. :)
This message, "failed ERROR curl failed GET url `https://rhevm.cloud.redhat.com:8543/rhevm-api-powershell/'" is coming from iwhd but I cannot make out what the problem is.
James did exactly the right thing in the circumstances: tried the URL. But he did not go far enough. Next step is to copy credentials from the /etc/factory.conf (IIRC) and try with curl -u xxx@yyy:ppp, see how that goes.
My curl -u seems to work fine:
[root@cldmgr01 ~]# curl -u rhevadmin@cloud.redhat.com:password https://fqdn:8543/rhevm-api-powershell/ <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <api> <link rel="capabilities" href="/rhevm-api-powershell/capabilities"/> <link rel="clusters" href="/rhevm-api-powershell/clusters"/> <link rel="clusters/search" href="/rhevm-api-powershell/clusters?search={query}"/> .... etc etc
I can't seem to find /etc/factory.conf file. The closest thing I found was /etc/imagefactory.conf:
[root@cldmgr01 ~]# cat /etc/imagefactory.conf { "warehouse": "http://localhost:9090/", "image_bucket": "images", "build_bucket": "builds", "target_bucket": "target_images", "template_bucket": "templates", "icicle_bucket": "icicles", "provider_bucket": "provider_images", "imgdir": "/var/tmp", "ec2_build_style": "snapshot", "ec2_ami_type": "s3" }
-- Pete
On Thu, 28 Jul 2011 20:22:38 -0400 (EDT) James Labocki jlabocki@redhat.com wrote:
This message, "failed ERROR curl failed GET url `https://rhevm.cloud.redhat.com:8543/rhevm-api-powershell/'" is coming from iwhd but I cannot make out what the problem is.
James did exactly the right thing in the circumstances: tried the URL. But he did not go far enough. Next step is to copy credentials from
[root@cldmgr01 ~]# curl -u rhevadmin@cloud.redhat.com:password https://fqdn:8543/rhevm-api-powershell/
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<api> <link rel="capabilities" href="/rhevm-api-powershell/capabilities"/> <link rel="clusters" href="/rhevm-api-powershell/clusters"/> <link rel="clusters/search" href="/rhevm-api-powershell/clusters?search={query}"/> .... etc etc
This is good.
So, how does the Conductor know the parameters? I remember there was some sort of configuration file for it. Where did you enter the credentials and the URL that you used for the above test?
I can't seem to find /etc/factory.conf file. The closest thing I found was /etc/imagefactory.conf:
[root@cldmgr01 ~]# cat /etc/imagefactory.conf { "warehouse": "http://localhost:9090/", "image_bucket": "images",
Looks like this is not it, then.
-- Pete
James Labocki Solution Architect Red Hat m: 440.503.9996
----- Original Message -----
From: "Pete Zaitcev" zaitcev@redhat.com To: "James Labocki" jlabocki@redhat.com Cc: aeolus-devel@lists.fedorahosted.org, imcleod@redhat.com, "Jim Meyering" jim@meyering.net, "Steve Loranz" sloranz@redhat.com Sent: Thursday, July 28, 2011 9:26:17 PM Subject: Re: aeolus-image push curl failed On Thu, 28 Jul 2011 20:22:38 -0400 (EDT) James Labocki jlabocki@redhat.com wrote:
This message, "failed ERROR curl failed GET url `https://rhevm.cloud.redhat.com:8543/rhevm-api-powershell/'" is coming from iwhd but I cannot make out what the problem is.
James did exactly the right thing in the circumstances: tried the URL. But he did not go far enough. Next step is to copy credentials from
[root@cldmgr01 ~]# curl -u rhevadmin@cloud.redhat.com:password https://fqdn:8543/rhevm-api-powershell/
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<api> <link rel="capabilities" href="/rhevm-api-powershell/capabilities"/> <link rel="clusters" href="/rhevm-api-powershell/clusters"/> <link rel="clusters/search" href="/rhevm-api-powershell/clusters?search={query}"/> .... etc etc
This is good.
So, how does the Conductor know the parameters? I remember there was some sort of configuration file for it. Where did you enter the credentials and the URL that you used for the above test?
In /etc/aeolus-configure/nodes/default_configure I entered the following stanzas to enable rhevm support, including rhevm_deltacloud_password which contains the correct password (same on I tested in curl)
rhevm_nfs_server: nfsvm.cloud.redhat.com rhevm_nfs_export: /exportdomain rhevm_nfs_mount_point: /mnt/rhevm-nfs rhevm_deltacloud_port: 3005 rhevm_deltacloud_username: deltacloud@cloud.redhat.com rhevm_deltacloud_password: Password rhevm_deltacloud_powershell_url: https://fqdn:8543/rhevm-api-powershell
the /exportdomain is mounted successfull on /mnt/rhevm-nfs when `aeolus-configure` is run and the user can write to the directory.
I can't seem to find /etc/factory.conf file. The closest thing I found was /etc/imagefactory.conf:
[root@cldmgr01 ~]# cat /etc/imagefactory.conf { "warehouse": "http://localhost:9090/", "image_bucket": "images",
Looks like this is not it, then.
-- Pete _______________________________________________ aeolus-devel mailing list aeolus-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/aeolus-devel
----- Original Message -----
From: "James Labocki" jlabocki@redhat.com To: "Pete Zaitcev" zaitcev@redhat.com Cc: aeolus-devel@lists.fedorahosted.org, imcleod@redhat.com, "Jim Meyering" jim@meyering.net, "Steve Loranz" sloranz@redhat.com Sent: Friday, July 29, 2011 9:37:43 AM Subject: Re: aeolus-image push curl failed
----- Original Message -----
From: "Pete Zaitcev" zaitcev@redhat.com To: "James Labocki" jlabocki@redhat.com Cc: aeolus-devel@lists.fedorahosted.org, imcleod@redhat.com, "Jim Meyering" jim@meyering.net, "Steve Loranz" sloranz@redhat.com Sent: Thursday, July 28, 2011 9:26:17 PM Subject: Re: aeolus-image push curl failed On Thu, 28 Jul 2011 20:22:38 -0400 (EDT) James Labocki jlabocki@redhat.com wrote:
This message, "failed ERROR curl failed GET url `https://rhevm.cloud.redhat.com:8543/rhevm-api-powershell/'" is coming from iwhd but I cannot make out what the problem is.
James did exactly the right thing in the circumstances: tried the URL. But he did not go far enough. Next step is to copy credentials from
[root@cldmgr01 ~]# curl -u rhevadmin@cloud.redhat.com:password https://fqdn:8543/rhevm-api-powershell/
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<api> <link rel="capabilities" href="/rhevm-api-powershell/capabilities"/> <link rel="clusters" href="/rhevm-api-powershell/clusters"/> <link rel="clusters/search" href="/rhevm-api-powershell/clusters?search={query}"/> .... etc etc
This is good.
So, how does the Conductor know the parameters? I remember there was some sort of configuration file for it. Where did you enter the credentials and the URL that you used for the above test?
In /etc/aeolus-configure/nodes/default_configure I entered the following stanzas to enable rhevm support, including rhevm_deltacloud_password which contains the correct password (same on I tested in curl)
rhevm_nfs_server: nfsvm.cloud.redhat.com rhevm_nfs_export: /exportdomain rhevm_nfs_mount_point: /mnt/rhevm-nfs rhevm_deltacloud_port: 3005 rhevm_deltacloud_username: deltacloud@cloud.redhat.com rhevm_deltacloud_password: Password rhevm_deltacloud_powershell_url: https://fqdn:8543/rhevm-api-powershell
the /exportdomain is mounted successfull on /mnt/rhevm-nfs when `aeolus-configure` is run and the user can write to the directory.
FWIW, here is a listing of the image I am trying to push
# aeolus-image list --images IMAGE ID LASTEST PUSHED BUILD NAME TARGET OS OS VERSION ARCH DESCRIPTION e4c702a2-ee72-4c08-8117-20f68d28c2b8 tmpl1 rhevm Fedora 14 x86_64 Fedora 14 Template
Also, here is the full imagefactory.log output that results from `aeolus-image push --provider rhevm --id e4c702a2-ee72-4c08-8117-20f68d28c2b8`
2011-07-29 09:41:15,291 DEBUG imagefactory.qmfagent.ImageFactoryAgent.ImageFactoryAgent pid(8044) Message: Method called: name = push_image args = {'credentials': '*** REDACTED ***', 'image': 'e4c702a2-ee72-4c08-8117-20f68d28c2b8', 'build': '', 'providers': ['rhevm']} handle = <cqmf2.AgentEvent; proxy of <Swig Object of type 'qmf::AgentEvent *' at 0x1e139c0> > addr = redhat.com:imagefactory:1a87b75d-83f8-46c0-8249-a6af72e6ac11:image_factory subtypes = {} userId = anonymous 2011-07-29 09:41:15,293 DEBUG imagefactory.ImageWarehouse.ImageWarehouse pid(8044) Message: Getting metadata (['latest_unpushed']) from http://localhost:9090/images/e4c702a2-ee72-4c08-8117-20f68d28c2b8 2011-07-29 09:41:15,295 DEBUG imagefactory.ImageWarehouse.ImageWarehouse pid(8044) Message: Querying (http://localhost:9090/target_images/_query) with expression ($build == "12369482-95cb-4119-a69e-b516276e422f" && $target == "rhevm") 2011-07-29 09:41:15,297 DEBUG imagefactory.ImageWarehouse.ImageWarehouse pid(8044) Message: Getting metadata (['template']) from http://localhost:9090/target_images/35d99e8c-6a7e-40e6-9c24-d7c931b8332f 2011-07-29 09:41:15,298 DEBUG imagefactory.ImageWarehouse.ImageWarehouse pid(8044) Message: Created Image Warehouse instance http://localhost:9090 - buckets(target_images, templates, icicles, provider_images) 2011-07-29 09:41:15,301 DEBUG imagefactory.ImageWarehouse.ImageWarehouse pid(8044) Message: Created Image Warehouse instance http://localhost:9090 - buckets(target_images, templates, icicles, provider_images) 2011-07-29 09:41:15,304 DEBUG imagefactory.BuildJob.BuildAdaptor pid(8044) Message: Raising event with agent handler (<ImageFactoryAgent(Thread-1, initial)>), changed status from NEW to PUSHING 2011-07-29 09:41:15,304 DEBUG imagefactory.BuildJob.BuildAdaptor pid(8044) Message: Raising event with agent handler (<ImageFactoryAgent(Thread-1, initial)>), changed percent complete from 0 to 0 2011-07-29 09:41:15,479 DEBUG imagefactory.builders.BaseBuilder.FedoraBuilder pid(8044) Message: Exception caught in ImageFactory 2011-07-29 09:41:15,479 DEBUG imagefactory.builders.BaseBuilder.FedoraBuilder pid(8044) Message: Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/imagefactory/builders/FedoraBuilder.py", line 1006, in push_image_upload self.rhevm_push_image_upload(target_image_id, provider, credentials) File "/usr/lib/python2.6/site-packages/imagefactory/builders/FedoraBuilder.py", line 981, in rhevm_push_image_upload raise ImageFactoryException("Failed to extract RHEV-M UUID from warehouse POST reponse: %s" % (response)) ImageFactoryException: Failed to extract RHEV-M UUID from warehouse POST reponse: failed ERROR curl failed GET url `https://rhevm.cloud.redhat.com:8543/rhevm-api-powershell/'
2011-07-29 09:41:15,480 DEBUG imagefactory.BuildJob.BuildAdaptor pid(8044) Message: Raising event with agent handler (<ImageFactoryAgent(Thread-1, initial)>), changed status from PUSHING to FAILED 2011-07-29 09:41:15,480 DEBUG imagefactory.builders.BaseBuilder.FedoraBuilder pid(8044) Message: Exception caught in ImageFactory 2011-07-29 09:41:15,480 DEBUG imagefactory.builders.BaseBuilder.FedoraBuilder pid(8044) Message: Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/imagefactory/builders/FedoraBuilder.py", line 496, in push_image self.push_image_upload(target_image_id, provider, credentials) File "/usr/lib/python2.6/site-packages/imagefactory/builders/FedoraBuilder.py", line 1006, in push_image_upload self.rhevm_push_image_upload(target_image_id, provider, credentials) File "/usr/lib/python2.6/site-packages/imagefactory/builders/FedoraBuilder.py", line 981, in rhevm_push_image_upload raise ImageFactoryException("Failed to extract RHEV-M UUID from warehouse POST reponse: %s" % (response)) ImageFactoryException: Failed to extract RHEV-M UUID from warehouse POST reponse: failed ERROR curl failed GET url `https://rhevm.cloud.redhat.com:8543/rhevm-api-powershell/'
2011-07-29 09:41:15,480 DEBUG imagefactory.BuildJob.BuildAdaptor pid(8044) Message: Raising event with agent handler (<ImageFactoryAgent(Thread-1, initial)>), changed status from FAILED to FAILED
I can't seem to find /etc/factory.conf file. The closest thing I found was /etc/imagefactory.conf:
[root@cldmgr01 ~]# cat /etc/imagefactory.conf { "warehouse": "http://localhost:9090/", "image_bucket": "images",
Looks like this is not it, then.
-- Pete _______________________________________________ aeolus-devel mailing list aeolus-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/aeolus-devel
On Fri, 29 Jul 2011 09:43:54 -0400 (EDT) James Labocki jlabocki@redhat.com wrote:
[root@cldmgr01 ~]# curl -u rhevadmin@cloud.redhat.com:password https://fqdn:8543/rhevm-api-powershell/
rhevm_deltacloud_username: deltacloud@cloud.redhat.com rhevm_deltacloud_password: Password rhevm_deltacloud_powershell_url: https://fqdn:8543/rhevm-api-powershell
You tried with rhevadmin user, but iwhd is apparently configured to use "deltacloud" user. Please try deltacloud@, see how that works.
Since you are redacting more than just password before posting, and so I cannot see the true picture, it falls on you to be very careful comparing parameters of factory and curl.
ImageFactoryException: Failed to extract RHEV-M UUID from warehouse POST reponse: failed ERROR curl failed GET url `https://rhevm.cloud.redhat.com:8543/rhevm-api-powershell/'
Look, this is a simple thing. All those mounts and whatnot are immaterial at present juncture. The iwhd receives an error when it tries to access the root of the API, that's all it is. Unfortunately, libcurl does not tell us if it's 403, 404, or what it is. That is why you run CLI curl with the _same parameters_ on the same host, but with -v, which allows to determine what fails. Maybe it's just iptables or a typo in some configuration somewhere. The most surefire way to know would've been tcpdump, but alas, RHEV-2.2 forces SSL.
-- Pete
aeolus-devel@lists.fedorahosted.org