Bug 1204481 - [Build 20221019-2] openQA test fails to launch simple rails application
[Build 20221019-2] openQA test fails to launch simple rails application
Status: NEW
Classification: openSUSE
Product: openSUSE Distribution
Classification: openSUSE
Component: Ruby
Leap 15.4
Other Other
: P1 - Urgent : Major (vote)
: ---
Assigned To: Ruby Devel
E-mail List
https://openqa.opensuse.org/tests/281...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2022-10-19 09:23 UTC by Marcus Meissner
Modified: 2022-11-04 11:51 UTC (History)
3 users (show)

See Also:
Found By: openQA
Services Priority:
Business Priority:
Blocker: Yes
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marcus Meissner 2022-10-19 09:23:37 UTC
## Observation

openQA test in scenario opensuse-15.4-DVD-Updates-x86_64-extra_tests_textmode@64bit fails in
[rails](https://openqa.opensuse.org/tests/2814152/modules/rails/steps/12)

## Test suite description
Maintainer: slindomansilla@suse.de.
Mainly post-installation console extra tests.


## Reproducible

Fails since (at least) Build [20220818-1](https://openqa.opensuse.org/tests/2532924)


## Expected result

Last good: (unknown) (or more recent)


## Further details

Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensuse&flavor=DVD-Updates&machine=64bit&test=extra_tests_textmode&version=15.4)
Comment 1 Marcus Meissner 2022-10-19 09:25:20 UTC
testcase is super simple:

zypper -n in --recommends -C "rubygem(rails)"
rails new mycoolapp --skip-bundle --skip-test
cd mycoolapp
(rails server -b 0.0.0.0 &)
for i in {1..100} ; do sleep 0.1; curl -s http://localhost:3000 | grep "<title>Ruby on Rails" && break ; done
pkill -f "rails server" || pumactl -P tmp/pids/server.pid stop


the rails server start up fails with:
(rails server -b 0.0.0.0 &) 
Could not find gem 'puma (~> 3.11)' in any of the gem sources listed in your Gemfile.
Run `bundle install` to install missing gems.


I have however installed ruby2.5-rubygem-puma-4.3.12-150000.3.9.1.x86_64
Comment 2 Josef Reidinger 2022-10-19 14:53:41 UTC
(In reply to Marcus Meissner from comment #1)
> testcase is super simple:
> 
> zypper -n in --recommends -C "rubygem(rails)"
> rails new mycoolapp --skip-bundle --skip-test
> cd mycoolapp
> (rails server -b 0.0.0.0 &)
> for i in {1..100} ; do sleep 0.1; curl -s http://localhost:3000 | grep
> "<title>Ruby on Rails" && break ; done
> pkill -f "rails server" || pumactl -P tmp/pids/server.pid stop
> 
> 
> the rails server start up fails with:
> (rails server -b 0.0.0.0 &) 
> Could not find gem 'puma (~> 3.11)' in any of the gem sources listed in your
> Gemfile.
> Run `bundle install` to install missing gems.
> 
> 
> I have however installed ruby2.5-rubygem-puma-4.3.12-150000.3.9.1.x86_64

and that is issue ~> 3.11 means > 3.11 but < 4.0 so 4.3 is too high to satisfy that dependency - https://thoughtbot.com/blog/rubys-pessimistic-operator
Comment 3 Santiago Zarate 2022-11-04 11:16:56 UTC
(In reply to Josef Reidinger from comment #2)
> (In reply to Marcus Meissner from comment #1)
> > testcase is super simple:
> > 
> > zypper -n in --recommends -C "rubygem(rails)"
> > rails new mycoolapp --skip-bundle --skip-test
> > cd mycoolapp
> > (rails server -b 0.0.0.0 &)
> > for i in {1..100} ; do sleep 0.1; curl -s http://localhost:3000 | grep
> > "<title>Ruby on Rails" && break ; done
> > pkill -f "rails server" || pumactl -P tmp/pids/server.pid stop
> > 
> > 
> > the rails server start up fails with:
> > (rails server -b 0.0.0.0 &) 
> > Could not find gem 'puma (~> 3.11)' in any of the gem sources listed in your
> > Gemfile.
> > Run `bundle install` to install missing gems.
> > 
> > 
> > I have however installed ruby2.5-rubygem-puma-4.3.12-150000.3.9.1.x86_64
> 
> and that is issue ~> 3.11 means > 3.11 but < 4.0 so 4.3 is too high to
> satisfy that dependency -
> https://thoughtbot.com/blog/rubys-pessimistic-operator

So we're distributing two gems that aren´t compatible?
Comment 4 Santiago Zarate 2022-11-04 11:51:40 UTC
(In reply to Santiago Zarate from comment #3)
> (In reply to Josef Reidinger from comment #2)
> > (In reply to Marcus Meissner from comment #1)
> > > testcase is super simple:
> > > 
> > > zypper -n in --recommends -C "rubygem(rails)"
> > > rails new mycoolapp --skip-bundle --skip-test
> > > cd mycoolapp
> > > (rails server -b 0.0.0.0 &)
> > > for i in {1..100} ; do sleep 0.1; curl -s http://localhost:3000 | grep
> > > "<title>Ruby on Rails" && break ; done
> > > pkill -f "rails server" || pumactl -P tmp/pids/server.pid stop
> > > 
> > > 
> > > the rails server start up fails with:
> > > (rails server -b 0.0.0.0 &) 
> > > Could not find gem 'puma (~> 3.11)' in any of the gem sources listed in your
> > > Gemfile.
> > > Run `bundle install` to install missing gems.
> > > 
> > > 
> > > I have however installed ruby2.5-rubygem-puma-4.3.12-150000.3.9.1.x86_64
> > 
> > and that is issue ~> 3.11 means > 3.11 but < 4.0 so 4.3 is too high to
> > satisfy that dependency -
> > https://thoughtbot.com/blog/rubys-pessimistic-operator
> 
> So we're distributing two gems that aren´t compatible?

Even if we move the version of puma further, we'll end up in a similar situation with other gems:

> 247338f6210b:/mycoolapp # rails s
> Could not find gem 'listen (< 3.2, >= 3.0.5)' in any of the gem sources listed in your Gemfile.
> Run `bundle install` to install missing gems.