Bug 916330

working on this one

Andre Dietisheim <adietish> made a comment on jira JBIDE-13666

reopening this issue after changing the description.

Andre Dietisheim <adietish> updated the status of jira JBIDE-13666 to Reopened

Andre Dietisheim <adietish> made a comment on jira JBIDE-13666

This is a WATCHER/TRACKER issue. This is an issue on the OpenShift platform. There's nothing we can do about it.

I believe this was an issue with trying to read the parent domain pending_op from secondary within 500ms of the domain pending op being created. Perhaps not enough time for things to have been synced to secondary on a loaded mongo.

This has now been fixed to read from the primary.

Verified on the env that migrate from devenv_stage_312 to devenv_2888
1.Create domain
curl -k --user "qgong+1:111111" -H "Accept: application/xml" https://ec2-23-22-110-226.compute-1.amazonaws.com/broker/rest/domains/ -X POST --form id=bingobongo

2.Create jbossas-7 application
curl -k --user "qgong+1:111111" -H "Accept: application/xml" https://ec2-23-22-110-226.compute-1.amazonaws.com/broker/rest/domains/bingobongo/applications/ -X POST -v --form name=as --form cartridge=jbossas-7

3.update domain
[qgong@dhcp-8-169 python1]$ curl -k --user "qgong+1:111111" -H "Accept: application/xml" https://ec2-23-22-110-226.compute-1.amazonaws.com/broker/rest/domains/bingobongo -X PUT --form id=honkabonka -v
* About to connect() to proxy file.rdu.redhat.com port 3128 (#0)
*   Trying 10.11.255.147... connected
* Connected to file.rdu.redhat.com (10.11.255.147) port 3128 (#0)
* Establish HTTP proxy tunnel to ec2-23-22-110-226.compute-1.amazonaws.com:443
* Server auth using Basic with user 'qgong+1'
> CONNECT ec2-23-22-110-226.compute-1.amazonaws.com:443 HTTP/1.1
> Host: ec2-23-22-110-226.compute-1.amazonaws.com:443
> User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.13.1.0 zlib/1.2.3 libidn/1.18 libssh2/1.2.2
> Proxy-Connection: Keep-Alive
> Accept: application/xml
> 
< HTTP/1.0 200 Connection established
< 
* Proxy replied OK to CONNECT request
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* warning: ignoring value of ssl.verifyhost
* skipping SSL peer certificate verification
* SSL connection using TLS_DHE_RSA_WITH_AES_256_CBC_SHA
* Server certificate:
* 	subject: E=root@ip-10-98-59-17,CN=ip-10-98-59-17,OU=SomeOrganizationalUnit,O=SomeOrganization,L=SomeCity,ST=SomeState,C=--
* 	start date: Feb 27 05:30:45 2013 GMT
* 	expire date: Feb 27 05:30:45 2014 GMT
* 	common name: ip-10-98-59-17
* 	issuer: E=root@ip-10-98-59-17,CN=ip-10-98-59-17,OU=SomeOrganizationalUnit,O=SomeOrganization,L=SomeCity,ST=SomeState,C=--
* Server auth using Basic with user 'qgong+1'
> PUT /broker/rest/domains/bingobongo HTTP/1.1
> Authorization: Basic cWdvbmcrMUByZWRoYXQuY29tOjExMTExMQ==
> User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.13.1.0 zlib/1.2.3 libidn/1.18 libssh2/1.2.2
> Host: ec2-23-22-110-226.compute-1.amazonaws.com
> Accept: application/xml
> Content-Length: 147
> Expect: 100-continue
> Content-Type: multipart/form-data; boundary=----------------------------7f17e29ca364
> 
< HTTP/1.1 100 Continue
< HTTP/1.1 100 Continue
< HTTP/1.1 200 
< Date: Mon, 04 Mar 2013 05:13:54 GMT
< Server: Apache/2.2.15 (Red Hat)
< X-Powered-By: Phusion Passenger (mod_rails/mod_rack) 3.0.17
< X-OpenShift-Identity: qgong+1
< X-OAuth-Scopes: session
< X-UA-Compatible: IE=Edge
< ETag: "7ccc1fa5dc458dd7c96aad299de6d3ea"
< Cache-Control: max-age=0, private, must-revalidate
< X-Request-Id: 6e664d41d3b15a951d6a96066326fc11
< X-Runtime: 10.374310
< X-Rack-Cache: invalidate, pass
< Status: 200
< Content-Length: 11047
< Content-Type: application/xml; charset=utf-8
< Vary: Accept-Encoding,User-Agent
< Strict-Transport-Security: max-age=15768000
< ProxyTime: D=11017145
< 
<?xml version="1.0" encoding="UTF-8"?>
<response>
  <status>ok</status>
  <type>domain</type>
  <data>
    <domain>
      <id>honkabonka</id>
      <suffix>dev.rhcloud.com</suffix>
      <links>
        <link>
          <rel>Get domain</rel>
          <method>GET</method>
          <href>https://ec2-23-22-110-226.compute-1.amazonaws.com/broker/rest/domains/honkabonka</href>
          <required-params/>
          <optional-params/>
        </link>
        <link>
          <rel>List applications</rel>
          <method>GET</method>
          <href>https://ec2-23-22-110-226.compute-1.amazonaws.com/broker/rest/domains/honkabonka/applications</href>
          <required-params/>
          <optional-params/>
        </link>
        <link>
          <rel>Create new application</rel>
          <method>POST</method>
          <href>https://ec2-23-22-110-226.compute-1.amazonaws.com/broker/rest/domains/honkabonka/applications</href>
          <required-params>
            <param>
              <name>name</name>
              <type>string</type>
              <description>Name of the application</description>
              <valid-options/>
....

Andre Dietisheim <adietish> made a comment on jira JBIDE-13666

verified on PROD (which was freshly deployed today) and could not reproduce it. Thus resolving this issue.

Andre Dietisheim <adietish> updated the status of jira JBIDE-13666 to Resolved

Stefan Bunciak <sbunciak> updated the status of jira JBIDE-13666 to Closed

Stefan Bunciak <sbunciak> made a comment on jira JBIDE-13666

Verified in JBoss Developer Studio

Version: 7.0.0.Alpha2
Build id: Alpha2-v20130407-2320-B135
Build date: 20130407-2320