On Jan 14, 2014, at 3:48 PM, Santhosh Edukulla <santhosh.eduku...@citrix.com> wrote:
> Sebastian, > > 1. As such the profile issue mentioned in the bug is fixed( submitted a > patch, not yet applied ), instead of using the same bug for other issue > related to simulator, may be we can log a separate bug. > The reason being the issues reported are different and this new issue > reported is inside the simulator code if any but nothing to do with marvin > though? Let me know. > not note fixed yet, I will post additional comments/logs in your review > > Regards, > Santhosh > ________________________________________ > From: sebgoa [run...@gmail.com] > Sent: Tuesday, January 14, 2014 9:10 AM > To: Santhosh Edukulla > Cc: dev@cloudstack.apache.org; gir...@clogeny.com; Prasanna Santhanam > Subject: Re: [ACS 4.3] RC update > > On Jan 14, 2014, at 2:28 PM, Santhosh Edukulla <santhosh.eduku...@citrix.com> > wrote: > >> Hi Sebastian, >> >> Note1 : The nose command you are running is right ( Just use nosetests-2.7 >> ), I just ran the simulator using the below mentioned commands followed by >> deployDataCenter, on 4.2 and 4.3 separately, there were no errors reported >> on 4.2. I could see that templates were available, displayed and >> deployDataCenter worked fine on 4.2 but not on 4.3 and its throwing the >> error you mentioned. We will look in to it. >> > > ok thanks, this is important. If we want to remove the maven profile then we > need to make sure the nosetests way of configuring the DC works. > >> Note2: Regarding the templates not available in UI, we need to register the >> template to work with simulator post deploy for testing ( atleast with 4.2.1 >> or later ), this behavior i believe was due to some issue in simulator code >> in later code and i was told to register and proceed with tests then. >> >> Note3: Profile issue, i fixed and submitted a review. >> > > I tested it on 4.3, it seems to work but never returns. Is that the newly > expected behavior ? > >> Note4: Registering a template issue manually and below for addCluster >> Command, we will look in to it. This i believe is nothing to do with marvin >> though. >> > > your note4 and note3 seem to be talking about the same thing. My concern is > that this was working in 4.2, so if it's broken in 4.2.1 this is brand new > error. > I understand that few people use the simulator, but we should fix it in 4.3 > (and apply patch to 4.2 branch as well ) > > > >> Let me know. >> >> Thanks! >> Santhosh >> ________________________________________ >> From: sebgoa [run...@gmail.com] >> Sent: Tuesday, January 14, 2014 5:22 AM >> To: Santhosh Edukulla >> Cc: dev@cloudstack.apache.org; gir...@clogeny.com; Prasanna Santhanam >> Subject: Re: [ACS 4.3] RC update >> >> On Jan 13, 2014, at 6:45 PM, Santhosh Edukulla >> <santhosh.eduku...@citrix.com> wrote: >> >>> Hi Sebastian, >>> >>> 1. I was able to get the simulator up and running following the below >>> instructions @link: >>> >>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Simulator+integration >>> >>> mvn -Pdeveloper -Dsimulator clean install >>> mvn -Pdeveloper -pl developer -Ddeploydb >>> mvn -Pdeveloper -pl developer -Ddeploydb-simulator >>> mvn -pl client jetty:run -Dsimulator >>> >>> Thereafter deploying a datacenter worked either by "python >>> deployDataCenter.py -i <path_to_config>" or "python deployAndRun.py -c >>> <path_to_config>" >>> >> >> Santhosh, I tried this and it works. >> I am pretty sure that we did not need to use the -Dsimulator before ( I >> documented it without), but we can skip this. >> >> However when accessing the UI and trying to run an instance, there are no >> templates available. >> The systemVMs are running. >> >> Also, I used to be able to use nosetests as well and configure the DC with: >> nosetests --with-marvin --marvin-config=setup/dev/basic.cfg >> >> it gave me this: >> >> $ nosetests --with-marvin --marvin-config=setup/dev/basic.cfg >> >> Exception Occurred Under __deployDC : Execute cmd: addcluster failed, due >> to: errorCode: 431, errorText:Could not find corresponding resource manager >> for simulator >> Traceback (most recent call last): >> File >> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/nosetests", >> line 8, in <module> >> load_entry_point('nose==1.3.0', 'console_scripts', 'nosetests')() >> File >> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/nose/core.py", >> line 118, in __init__ >> **extra_args) >> File >> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/unittest/main.py", >> line 95, in __init__ >> self.runTests() >> File >> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/nose/core.py", >> line 197, in runTests >> result = self.testRunner.run(self.test) >> File >> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/nose/core.py", >> line 61, in run >> test(result) >> File >> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/nose/suite.py", >> line 176, in __call__ >> return self.run(*arg, **kw) >> File >> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/nose/suite.py", >> line 223, in run >> test(orig) >> File >> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/unittest/suite.py", >> line 70, in __call__ >> return self.run(*args, **kwds) >> File >> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/nose/suite.py", >> line 74, in run >> test(result) >> File >> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/nose/suite.py", >> line 176, in __call__ >> return self.run(*arg, **kw) >> File >> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/nose/suite.py", >> line 223, in run >> test(orig) >> File >> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/nose/suite.py", >> line 176, in __call__ >> return self.run(*arg, **kw) >> File >> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/nose/suite.py", >> line 223, in run >> test(orig) >> File >> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/nose/suite.py", >> line 176, in __call__ >> return self.run(*arg, **kw) >> File >> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/nose/suite.py", >> line 223, in run >> test(orig) >> File >> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/nose/suite.py", >> line 176, in __call__ >> return self.run(*arg, **kw) >> File >> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/nose/suite.py", >> line 223, in run >> test(orig) >> File >> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/nose/suite.py", >> line 176, in __call__ >> return self.run(*arg, **kw) >> File >> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/nose/suite.py", >> line 223, in run >> test(orig) >> File >> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/nose/suite.py", >> line 176, in __call__ >> return self.run(*arg, **kw) >> File >> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/nose/suite.py", >> line 223, in run >> test(orig) >> File >> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/nose/suite.py", >> line 176, in __call__ >> return self.run(*arg, **kw) >> File >> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/nose/suite.py", >> line 223, in run >> test(orig) >> File >> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/nose/suite.py", >> line 176, in __call__ >> return self.run(*arg, **kw) >> File >> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/nose/suite.py", >> line 223, in run >> test(orig) >> File >> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/nose/suite.py", >> line 176, in __call__ >> return self.run(*arg, **kw) >> File >> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/nose/suite.py", >> line 223, in run >> test(orig) >> File >> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/nose/case.py", >> line 45, in __call__ >> return self.run(*arg, **kwarg) >> File >> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/nose/case.py", >> line 138, in run >> result.addError(self, err) >> File >> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/nose/proxy.py", >> line 124, in addError >> plugin_handled = plugins.handleError(self.test, err) >> File >> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/nose/plugins/manager.py", >> line 99, in __call__ >> return self.call(*arg, **kw) >> File >> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/nose/plugins/manager.py", >> line 167, in simple >> result = meth(*arg, **kw) >> File >> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/marvin/marvinPlugin.py", >> line 146, in handleError >> self.tcRunLogger.fatal("%s: %s: %s" % >> AttributeError: 'NoneType' object has no attribute 'fatal' >> >> Maybe I am not using nosetests command properly but maybe some changes >> affected the marvinPlugin script, could you look into it ? >> >> thanks >> >> -sebastien >> >> >>> 2. Also, running python executable as part of mvn life cycle, will throw >>> some errors because of different python versions available on client and >>> packages relying to work only on 2.7+. >>> >>> 3. Just a Question: Using the below mentioned way a documented one of >>> running and using simulator? If not as such using above mentioned notes >>> under 1 are still available to work with simulator, >>> can we remove the bug from blocker category?\ >>> >>> mvn -Pdeveloper,marvin.setup -Dmarvin.config=setup/dev/basic.cfg -pl >>> :cloud-marvin integration-test >>> >>> 4. Also, the above mentioned way@3 worked anytime on python2.6? >>> >>> 5. Regarding the cleaning up of pom.xml, i am planning to remove >>> marvin.setup and marvin.test profiles altogether from tools/marvin/pom.xml? >>> let me know your thoughts? As such again fitting them in to mvn cycle has >>> some issues with different python and nose versions compatibility running >>> inside its lifecycle? If not so, i can fix to clean up the removed >>> arguments for deployAndRun.py? >>> <argument>-t</argument> >>> - <argument>/tmp/t.log</argument> >>> - <argument>-r</argument> >>> - <argument>/tmp/r.log</argument> >>> - <argument>-f</argument> >>> - >>> <argument>${resolved.basedir}/marvin/testSetupSuccess.py</argument> >>> >>> >>> Thanks! >>> Santhosh >>> ________________________________________ >>> From: sebgoa [run...@gmail.com] >>> Sent: Monday, January 13, 2014 8:26 AM >>> To: dev@cloudstack.apache.org >>> Cc: gir...@clogeny.com; Prasanna Santhanam; Santhosh Edukulla >>> Subject: Re: [ACS 4.3] RC update >>> >>> On Jan 11, 2014, at 7:08 AM, Animesh Chaturvedi >>> <animesh.chaturv...@citrix.com> wrote: >>> >>>> Folks >>>> >>>> Today is the scheduled RC date for ACS 4.3 We are very close with just a >>>> few lingering issues below. >>>> >>>> >>>> >>>> | Jayapal Reddy | CLOUDSTACK-5848 : [Upgrade3.0.6-4.3]"Unable to >>>> parse VLAN tag" message when network associated with SRX external firewall >>>> device is rebooted. >>>> | >>>> | edison su | CLOUDSTACK-5831 : As regular user , when trying >>>> to take a snapshot , snapshot succeeds but user is presented with "The >>>> given command does not exist or it is not available for user" message. >>>> | >>>> | Unassigned | CLOUDSTACK-5743 : Download ROOT Volume when the >>>> VM is in stopped state is failing with "Forbidden You don't have >>>> permission to access /userdata/e914903a-070b-4ee3-b217-f07dbc8bc72a.vhd/ >>>> on this server" | >>>> | Likitha Shetty | CLOUDSTACK-5707 : Hitting multiple exceptions >>>> when the Vsphere client is upgraded to 5.5 from 5.1 >>>> >>>> | >>>> | Daan Hoogland | CLOUDSTACK-5502 : [Automation] createVlanIpRange >>>> API failing, if you pass VLAN >>>> >>>> | >>>> | Marcus Sorensen | CLOUDSTACK-5432 : [Automation] Libvtd getting >>>> crashed and agent going to alert start >>>> >>>> | >>>> | Sateesh Chodapuneedi | CLOUDSTACK-5408 : [Automation] Failed to deploy >>>> vm in vmware environment with error "due to java.io.IOException: Cannot >>>> run program "mount": java.io.IOException: error=12, Cannot allocate >>>> memory" | >>>> | Wei Zhou | CLOUDSTACK-5144 : [Automation]: Basic Zone >>>> Security Groups - SSH to VM is allowed even when there is no ingress rule >>>> defined for the security group >>>> | >>>> >>>> >>>> If you have not played with 4.3 yet please take it for a spin and call out >>>> any critical issues, I plan to build an RC early next week. >>>> >>> >>> Animesh, I just created a blocker: >>> >>> https://issues.apache.org/jira/browse/CLOUDSTACK-5864 >>> >>> The simulator has been broken with recent changes in marvin >>> >>> >>>> Thanks >>>> Animesh >>>> >>>> -----Original Message----- >>>> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] >>>> Sent: Tuesday, January 07, 2014 10:51 AM >>>> To: dev@cloudstack.apache.org >>>> Subject: [ACS 4.3] RC update >>>> >>>> Folks >>>> >>>> Happy new year everyone. I hope you all had a good recharging time off >>>> during holiday. I want to bring our attention and focus to getting the 4.3 >>>> release out the door. While our scheduled RC date is this Friday 1/10 but >>>> we still have many open blocker and critical. Please review your backlog >>>> of issues and bring them to resolution ASAP and provide a "Due Date" in >>>> the bug. We need to absolutely make sure upgrades are working. If you >>>> encounter upgrade issue please file them as blockers. I will escalate all >>>> current upgrade issues to blocker. >>>> >>>> For the most recent release status please visit the 4.3 Release Dashboard >>>> [1]. I am following up on individual issues directly in JIRA so do watch >>>> JIRA emails >>>> >>>> [1] http://s.apache.org/dFk >>>> >>>> Thanks >>>> Animesh >
