Bug 1387378
Summary: | [rhos-osp-9][Assure updates to rhel7.3] Minor update that includes rhel72 to rhel73 switch fails with running instance (on SSL environment ) . | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Omri Hochman <ohochman> |
Component: | openstack-puppet-modules | Assignee: | Emilien Macchi <emacchi> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Alexander Chuzhoy <sasha> |
Severity: | urgent | Docs Contact: | |
Priority: | high | ||
Version: | 9.0 (Mitaka) | CC: | augol, cpaquin, dbecker, emacchi, jguiditt, jslagle, mburns, mfuruta, morazi, rhel-osp-director-maint, srevivo |
Target Milestone: | --- | Keywords: | TestOnly, Triaged, ZStream |
Target Release: | 9.0 (Mitaka) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openstack-puppet-modules-8.1.8-3.el7ost | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-11-29 15:07:21 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1386373 |
Description
Omri Hochman
2016-10-20 17:47:36 UTC
openstack-puppet-modules-8.1.8-2.el7ost.noarch file neutron/lib/puppet/provider/neutron_config/openstackconfig.rb does not seem to contain https://review.openstack.org/#/c/359475/ puppet-neutron updated Emilien Macchi,
I also get similar error report from customer on the customer portal case when they're using template file they used with osp8 for upgrade testing from Red Hat OpenStack Platform 8 to 9.
They saw the followings:
> [director01-osp9.dev-sirius:stack/788]$openstack software deployment output show 5d070b47-f404-471f-91e3-b7ff62c2e9a2 deploy_stderr
> output_value:
>
> deploy_stderr: |
> ...
> Warning: Scope(Haproxy::Config[haproxy]): haproxy: The $merge_options parameter will default to true in the next major release. Please review the documentation regarding the implications.
> Warning: Not collecting exported resources without storeconfigs
> Warning: Not collecting exported resources without storeconfigs
> Warning: Not collecting exported resources without storeconfigs
> Error: /Stage[main]/Neutron/Resources[neutron_config]: Failed to generate additional resources using 'generate': OpenStackConfig only support collecting instances when a file path is hard coded
> Error: Could not start Service[httpd]: Execution of '/usr/bin/systemctl start httpd' returned 1: Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details.
> Wrapped exception:
> Execution of '/usr/bin/systemctl start httpd' returned 1: Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details.
> Error: /Stage[main]/Apache::Service/Service[httpd]/ensure: change from stopped to running failed: Could not start Service[httpd]: Execution of '/usr/bin/systemctl start httpd' returned 1: Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details.
> Warning: /Stage[main]/Keystone::Deps/Anchor[keystone::service::end]: Skipping because of failed dependencies
(truncated, view all with --long)
Now they'd know if there is any workaround , if it's taken over without SSL ?
Thank you.
(In reply to Masaki Furuta from comment #6) > Emilien Macchi, > > I also get similar error report from customer on the customer portal case > when they're using template file they used with osp8 for upgrade testing > from Red Hat OpenStack Platform 8 to 9. > > They saw the followings: > > > [director01-osp9.dev-sirius:stack/788]$openstack software deployment output show 5d070b47-f404-471f-91e3-b7ff62c2e9a2 deploy_stderr > > output_value: > > > > deploy_stderr: | > > ... > > Warning: Scope(Haproxy::Config[haproxy]): haproxy: The $merge_options parameter will default to true in the next major release. Please review the documentation regarding the implications. > > Warning: Not collecting exported resources without storeconfigs > > Warning: Not collecting exported resources without storeconfigs > > Warning: Not collecting exported resources without storeconfigs > > Error: /Stage[main]/Neutron/Resources[neutron_config]: Failed to generate additional resources using 'generate': OpenStackConfig only support collecting instances when a file path is hard coded > > Error: Could not start Service[httpd]: Execution of '/usr/bin/systemctl start httpd' returned 1: Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details. > > Wrapped exception: > > Execution of '/usr/bin/systemctl start httpd' returned 1: Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details. > > Error: /Stage[main]/Apache::Service/Service[httpd]/ensure: change from stopped to running failed: Could not start Service[httpd]: Execution of '/usr/bin/systemctl start httpd' returned 1: Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details. > > Warning: /Stage[main]/Keystone::Deps/Anchor[keystone::service::end]: Skipping because of failed dependencies > (truncated, view all with --long) > > > Now they'd know if there is any workaround , if it's taken over without SSL ? > > Thank you. there could be many reasons why httpd might fail to start. i'd suggest filing a new bug with all the relevant information (logs, etc) so that we can track it as a new issues, especially since they are using a different openstack version than this bug was reported against. if needed, you can escalate the bugzilla through the rhos-prio escalation procedure. (In reply to James Slagle from comment #7) > > there could be many reasons why httpd might fail to start. i'd suggest > filing a new bug with all the relevant information (logs, etc) so that we > can track it as a new issues, especially since they are using a different > openstack version than this bug was reported against. > > if needed, you can escalate the bugzilla through the rhos-prio escalation > procedure. Sure, Thanks for it, I'll bring out with httpd error on another bz ! Btw ,based on Error regarding to Neutron in the log, I guess customer also hit this bz too. If it's true, can we work neutron related error around with disabling SSL or any suggestion worth trying to do ? (In reply to Masaki Furuta from comment #8) > (In reply to James Slagle from comment #7) > > > > there could be many reasons why httpd might fail to start. i'd suggest > > filing a new bug with all the relevant information (logs, etc) so that we > > can track it as a new issues, especially since they are using a different > > openstack version than this bug was reported against. > > > > if needed, you can escalate the bugzilla through the rhos-prio escalation > > procedure. > > Sure, Thanks for it, I'll bring out with httpd error on another bz ! > > Btw ,based on Error regarding to Neutron in the log, I guess customer also > hit this bz too. > > If it's true, can we work neutron related error around with disabling SSL or > any suggestion worth trying to do ? I wouldn't recommend disabling SSL at this point. There's no indication that SSL might be related to the issue. Verified: Environment: openstack-puppet-modules-8.1.8-3.el7ost Was able to minor update a deployment with ssl. |