| Summary: | Aeolus-configure error: /Stage[main]/Aeolus::Conductor::Seed_data/Aeolus::Provider | ||
|---|---|---|---|
| Product: | [Retired] CloudForms Cloud Engine | Reporter: | Shveta <ssachdev> |
| Component: | aeolus-configure | Assignee: | Mo Morsi <mmorsi> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | wes hayutin <whayutin> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 0.3.1 | CC: | dajohnso, ssachdev |
| Target Milestone: | beta | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Shveta
2011-06-27 14:41:03 UTC
rpm -qa|grep aeolus aeolus-conductor-0.3.0-0.fc14.20110624185507gita043b1b.noarch rubygem-aeolus-cli-0.0.1-1.fc14.20110622223500gitb6e219a.noarch aeolus-conductor-doc-0.3.0-0.fc14.20110624185507gita043b1b.noarch aeolus-conductor-daemons-0.3.0-0.fc14.20110624185507gita043b1b.noarch aeolus-all-0.3.0-0.fc14.20110624185507gita043b1b.noarch aeolus-configure-2.0.1-0.fc14.20110624144850git38b0c06.noarch Fedora -14 we seem to be getting random issues when configure tries to seed data..
anting administrator privileges for admin...
notice: /Stage[main]/Aeolus::Conductor::Seed_data/Aeolus::Site_admin[admin]/Exec[grant_site_admin_privs]/returns: executed successfully
notice: /File[/var/log/deltacloud-ec2-us-west-1]/ensure: created
notice: /File[/var/log/deltacloud-mock]/ensure: created
notice: /File[/etc/init.d/deltacloud-ec2-us-west-1]/ensure: defined content as '{md5}d52f8ab18e5fec3d847c2ec754409857'
err: /Stage[main]/Aeolus::Conductor::Seed_data/Aeolus::Conductor::Hwp[hwp1]/Web_request[hwp-hwp1]/post: change from to https://localhost/conductor/hardware_profiles failed: An exception was raised when invoking web request: Invalid HTTP Return Code: 502,
was expecting one of 200
notice: /File[/var/log/deltacloud-ec2-us-east-1]/ensure: created
[root@sgi-xe270-01 ~]# rpm -qa | grep aeolus
aeolus-conductor-0.3.0-0.el6.20110627173747git2a88782.noarch
rubygem-aeolus-cli-0.0.1-1.el6.20110627173747git2a88782.noarch
aeolus-all-0.3.0-0.el6.20110627173747git2a88782.noarch
aeolus-conductor-daemons-0.3.0-0.el6.20110627173747git2a88782.noarch
aeolus-conductor-doc-0.3.0-0.el6.20110627173747git2a88782.noarch
aeolus-configure-2.0.1-0.el6.20110624145042git38b0c06.noarch
[root@sgi-xe270-01 ~]#
err: /Stage[main]/Aeolus::Conductor::Seed_data/Aeolus::Provider[mock]/Aeolus::Conductor::Provider[mock]/Web_request[provider-mock]/post: change from to https://localhost/conductor/providers failed: An exception was raised when invoking web request: Expecting .*Provider added.* in the result rpm -qa|grep aeolus aeolus-all-0.3.0-0.fc14.20110627173747git2a88782.noarch aeolus-conductor-daemons-0.3.0-0.fc14.20110627173747git2a88782.noarch rubygem-aeolus-cli-0.0.1-1.fc14.20110627173747git2a88782.noarch aeolus-conductor-0.3.0-0.fc14.20110627173747git2a88782.noarch aeolus-configure-2.0.1-0.fc14.20110624144850git38b0c06.noarch aeolus-conductor-doc-0.3.0-0.fc14.20110627173747git2a88782.noarch Just hit this, seems related: err: /Stage[main]/Aeolus::Conductor::Seed_data/Aeolus::Conductor::Hwp[hwp1]/Web_request[hwp-hwp1]/post: change from to https://localhost/conductor/hardware_profiles failed: An exception was raised when invoking web request: Invalid HTTP Return Code: 404, was expecting one of 200 [root@dell-pe1950-02 ~]# rpm -qa | grep aeolus aeolus-conductor-0.3.0-0.el6.20110628135944git2a88782.noarch aeolus-conductor-daemons-0.3.0-0.el6.20110628135944git2a88782.noarch rubygem-aeolus-cli-0.0.1-1.el6.20110628165632git0dfe3ff.noarch aeolus-configure-2.0.1-0.el6.20110628141215gitb8aaf85.noarch aeolus-conductor-doc-0.3.0-0.el6.20110628135944git2a88782.noarch aeolus-all-0.3.0-0.el6.20110628135944git2a88782.noarch Could you elaborate on the steps you are taking to reproduce this? How often does this happen? Which seed data steps are failing? Looking at the output in the first comment it looks like the first conductor wui request is failing, perhaps conductor isn't fully up when the init script returns? I just ran aeolus-configure / aeolus-cleanup on my F14 box several times successfully (at least 10), verifying the seed data is created correct. Updated aeolus rpms have also just hit the fedorapeople.org testing repo, which I've been using, could you perhaps try w/ those. for the sake of argument... lets see how many times we can recreate this using beaker boxes... Shveta/Aziza can you try 10 installs and report how many times out of 10 there are any issues w/ seeding the data in conductor. thank you. I have not seen this issue in the last week.. moving to verified.. [root@sgi-xe310-02 ~]# rpm -qa | grep aeolus aeolus-conductor-0.3.0-0.el6.20110708135911gitdb1097c.noarch rubygem-aeolus-cli-0.0.1-1.el6.20110708135911gitdb1097c.noarch aeolus-all-0.3.0-0.el6.20110708135911gitdb1097c.noarch aeolus-configure-2.0.1-0.el6.20110707131907gitfaa220b.noarch aeolus-conductor-doc-0.3.0-0.el6.20110708135911gitdb1097c.noarch aeolus-conductor-daemons-0.3.0-0.el6.20110708135911gitdb1097c.noarch [root@sgi-xe310-02 ~]# rpm -q oz removing from tracker release pending... release pending... release pending.. 2 closing out old bugs perm close |